The humbling thought should be all the blue collar workers on r/vibecoding demoing their apps and games.
And then realizing they put together something that would have taken you a few days to do.
The supply of software is about to go way up, and that's going to massively impact demand unless every firm on earth is clamoring for more.
We're going to see if Jevons paradox holds true, or if wages get impacted drastically.
Only if you're working on a client consulting model perhaps, and not even then necessarily. There are lots of reports of vibe coded apps not holding up in production so they should be treated as prototypes. It's similar to the outsourcing trend where people reverted back to using in house talent once they realized how terrible most of the produced software was. The only difference is AI models get better but it remains to be seen if they can get to such an end to end stage that they can autonomously deploy to prod and diagnose any issues without human intervention. There have been some paths to that but I haven't seen it end to end yet.
Personal software is the future and a person building software for themselves tends to withstand enshittifcation. That's why I love when people open-source projects they love and are passionate about and I will always choose them over proprietary ones.
People always argue "well, Slack and Notion have distribution and the product isn't everything." Ok and? The person making it for themselves doesn't necessarily need distribution for it to be valuable. In fact, it's even more attractive that way.
Every time I wrote software that I was personally motivated to have and kept at it until it reached a comfortable equilibrium of utility, scope, and quality and then stopped? No one paid me.
Every time someone paid me to write software it was some combination of 1. not that interesting of a problem 2. no real utility i could see or touch, useful in some abstract way of making a number go up 3. involved a constant, painful maintenance burden 4. involved incident management of one kind or another 5. involved a long tail of details with no unifying principle other than a lot of implicit legacy constraints and stakeholders whose involvement waxed and waned with no seeming rhythm..
I'm a big fan of the new capability, it opens up new regimes of performance and correctness and capability for what I can achieve, that in turn grinds me up against math and theory that I had thus far been able to avoid, it's pushing me up the ambition ladder hard and that's a good thing.
But the change is a change in degree not in kind at least in the vibecode regime: it was always relatively fun and relatively easy to do one small program with modest requirements around defect rigor that had a big legible "oh cool!" surface that I didn't have to maintain. Fable doesn't seem any better than Opus at grinding detail work in the bowels of a compiler, but it sure can make an iPhone-scoped platform game with a bunch of bugs in it in a single shot?
If there's a job where you get paid for doing fun, high defect, "oh wow!" factor one-off software that you can immediately disavow any responsibility for? Fuck man, I should have had that job before Fable got that job.
Most of the stuff demoed on r/vibecoding are trivial programs, and they’re often buggy and full of holes. If that’s the type of software you produce then yes, you’ll probably be impacted. Thankfully that isn’t the majority of software.
It’s kind of like saying wedding photographers will be impacted because of the people posting on r/iPhoneography. Seems kind of silly doesn’t it.
The supply of software has already gone up, and most of the new stuff is close to useless