Massive, voluntarily deskilling of a professional class on an economy-wide scale. The folks who do not deskill will be the winners (eventually). Probably not before a bunch of people use the whole thing to make their fortunes selling smoke and mirrors, and probably not before burning down the planet, though. Where's Ford Prefect when you need a lift? 🤔
@ai6yr Rhymes with pulling COBOL programmers out of retirement to fix y2k bug. It will take a lot of money to pull me out of retirement to fix vibecoded systems that have zero human-written documentation 15 years from now.
@scottmiller42 @ai6yr I don't think "fixing" is possible with non-trivial vibecoded software. It's basically the equivalent of embedding a circuit in epoxy. You just have to replace it as soon as it starts acting up.
@scottmiller42 @ai6yr I actually find the unreadability and un-maintainability of code produced by generative AI somewhat surprising and interesting. If you had asked me five or so years ago, I would have expected machine produced software to be better than machine produced written language in 2026. But the opposite is clearly true.
@scottmiller42 @ai6yr It may be simply a matter of the requirements assumed by these systems. Code doesn't have to be comprehensible to "work", but human lanague does.
@mattblaze @scottmiller42 I think it's just a side effect of the training. They're using a generic LLM trained on "everything" in the world, multiple languages, multiple styles, and it mashes them all together. It's not like they trained it on, say, all the source code written to a high spec and documented and peer reviewed at IBM, or whatever company. Instead, it's code Joe Hacker posted on a forum, etc. etc. etc. Reddit, etc. and it all gets mashed into a kind of soup, which is inconsistent....
@mattblaze @scottmiller42 @ai6yr agree
I think it will be an interoperability standard change that will enact the demise of the vibe code
