I say unreliable because I cannot rely on it to accurately do what it claims to do. I cannot trust any number. I cannot trust that actions I invoke will actually happen. I cannot trust that taking action will not have mysterious side effects (e.g. re-opening an issue my boss’s boss closed in 2017 without explanation). I think I trust the underlying git infra but at this point I’m not sure why I do.

I say low quality because it is extremely slow at random moments, gets into broken inconsistent UI states, has baffling UX choices that make it harder to navigate than it should be (particularly with new UIs), and overall just doesn’t have the fit and finish we should expect from software in 1996 - or 2026, or literally any time in between.

For example, when I decided to continue my eight-year-old PR https://github.com/ClickHouse/ClickHouse/pull/104948, I couldn't see it - neither in search nor while navigating through pages.

Direct links still work.

1) counting

Software could be so much simpler and more reliable. There's so much bloat that is necessary to solve problems created by bloat. I hope we find our way out of this mess sooner rather than later. I'd hate for entire generations to suffer the current state of software whereas the theoretical understanding necessary to make things better was produced very early in the history of programmable computers.

"api.github.com/repos/{owner}/{repo}/actions/runs?status=in_progress" -> outputs 3 workflow runs

5 seconds later -> outputs 2 workflow runs

5 seconds later -> outputs same 3 workflow runs again

Apparently they make no guarantees of any type of consistency or continuity in output, which has the side effect of also making it completely useless.

The issues/pulls pages used to be showing the data from the primary data source, and then they changed it so everything is search, including the basic props is:pr and state:open.

Microsoft. That's the answer. Microsoft is happening over there.

It used to be that you could have a single GitHub account and join multiple orgs, some of which have enterprise plans with GitHub. They completely fumbled this during the pressure to ship AI features. Some enterprise controls that are supposed to affect only my work at a specific GitHub org affects me account-wide. I’m part of quite a few orgs on GitHub for OSS projects, and I never consented for that one org’s policies to basically take over my account.

I thought of going through the process of creating another account specifically for my work at this company, but GitHub is itself solving the problem in a very unique way: by being a place I don’t want to be in after I clock out.

That said, Microsoft isn't alone. The YouTube Android app has so many basic bugs that I sometimes wonder if the developers have tried asking an AI to "find all the bugs" in their code. It might do a better job! Large blank spaces in downloads, incorrect watch states, forgotten watch states, etc.

so nothing will be %100 correct, and we will always live in the past.

https://github.com/vanyauhalin?tab=packages

Extend: add actions, drive adoption, move your own devs to it

Extinguish: enshittify until all that's left is ads for copilot

They knew GitHub was the, well, hub, for most open source development. Then they captured it, now they use it to push their high margin products