1) counting
3) off-by-one errors
4) naming things
5) keeping the documentation up-to-date
4) database synchronization
5) multit
6) database synchreadinghronization
My god what an ancient trope.
Presumably you realize most current Microsoft employees were not even alive when the EEE memo was written.
Must we also talk about some decision Henry Ford made in 1906 every time the automaker is mentioned, or something the Gauls did in 200 BC every time England is mentioned?
The only time we talk about Henry Ford, unless it's about his anti-Semitism, is about decisions he made in 1906. If we go by your arbitrary standard, why would we talk about Henry Ford at all when we could talk about this year's Tesla model?
> See also Netscape v2.0 and 3.0, which were badass browsers back in 1996, but are similarly irrelevant today.
Why are you talking about Netscape? What does that have to do with anything happening right now?
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
Taking care that such incongruent representations can’t happen even in the face of inconsistent backend caches is part of proper UI state management.
How many companies engender taste in bugs, eh??
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.
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.
Microsoft. That's the answer. Microsoft is happening over there.
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.
It ran fine for years, then around November just stopped and never ran again. Tried moving it around for which time it would trigger, and it just never started again. Opened a ticket, and got nowhere
They are owned by Microsoft, what did you expect exactly?
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.
"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.
And knowing how these sorts of large corporations are structured, I wouldn't be surprised if the people who spend a few hours prompting AI to add some new unnecessary feature are being rewarded more than the people breaking their backs trying to stop the site from collapsing under the weight of 100 million vibe coders.
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.