

I think part of the issue is that historical software quality was an artefact of its time… if you can’t easily patch your released products, you need to work harder to ensure they’re functional. If the only way for people to learn about how your product works in the documentation you ship with it, the docs need to be useful and comprehensive.
The combination of software needing no guarantee of merchantability or fitness for any particular purpose and the internet rendered those pressures obsolete. Ship shit, fix later. Mass-scale a/b testing over past decade or two shows that most people seemingly don’t care if their software runs like absolute garbage, and is covered in adverts, and harvests all their personal data and the leaks all of it that wasn’t sold.
An incident-to-pr ratio that’s up by 250% is unfortunate, but it is not yet so bad that the end-users actually care enough to do anything about it, even assuming they can do anything.

Some folks, who may be familiar to some or more of you, accidentally discovered that if your git repo symlinks
CLAUDE.MDto, say,/dev/urandom, it breaks Claude code.https://neuromatch.social/@jonny/116779793188712173
The thread is actually about trying to attract and manipulate autonomous coding agents, but they’ve only had limited success so far, which may have been slowed down by the above symlink trick.