(Following thread was prompted by people pointing out that the Bluesky dev team seems heavily into vibe-coding now and originally posted on said vibe-coded Bluesky platform that is now constantly failing.)

Over the past year, every single time one of the apps or services I use suddenly became less reliable and more buggy, I never have to look far for the "Claude is amazing and now writes most of my code" post for the devs involved.

Best part? It's always somebody with years of experience. Exactly the demographic that is supposedly able to use this shit safely, but my impression is they're just as bad as the novices

This is happening IMO because of one of the fundamental issues with software dev (and this predates "AI" and was one of the themes of my first book):

Most software projects fail and most of what gets shipped doesn't work. The way the industry is set up means there is little downside to shipping broken software

Few devs have a reference point for genuinely working software. Usability labs were disbanded over 20 years ago. Very few companies do actual user research, so their designs are based on fiction. Bugs are the norm

Alienation is also the norm for devs, both socially and organisationally. Whether it works for the end user doesn't cross their mind. Whether the design fulfils business needs is not their problem. Bugs are a future problem. Ship insecure software and patch it as user data gets stolen

@baldur This reads like an open Work–Feedback Loop: work ships, but real user effects don’t reliably change decisions or next work. Maybe that is a good starting point to discuss this issue in the organization. Thats at least what my thinking model is for :)
@nobsagile @baldur And when development stops because the rot permeated the tools used for development the leadership says "Oh, something broke. Let us think about it". That is unless they consider declaring bankruptcy the easier option ​
@bunny @baldur Yep. “Let’s think about it” is the sound of years of postponed fixes finally cashing out.