Comment If people are terrible at resource allocation... (Score 1) 16
What strikes me as curious about this hypothesis is that it has been the case for decades. It wasn't "AI"; normally some combination of overgrown Excel sheets and garbage-tier Access by the more technical of whatever the mostly nontechnical user population happened to be to deal with needs that didn't get developer attention. And, for the most part, they still didn't get developer attention.
I suppose that there is a slim possibility that this 'vibe coding' will somehow convince management in ways that Access didn't, by being better at giving the illusion of being a slick solution that just needs a little more fixing; but there's nothing about the past quarter century of no-code/low-code or the last more-or-less-forever of "understand what it is your employees do and what would be useful for doing it" that suggests that people are particularly good at getting software to those in need of it.
If 'AI' tooling makes it radically cheaper to actually get to a final, working, tool then perhaps it will increase the absolute number of programming jobs if 'dude from fivver' replaces 'access' as the de-facto barely adequate unmaintainable solution; but if the idea is that somehow 'AI' will increase the number of actually costly programmers getting thrown at problems because it's easier for amateurs to produce broken non-solutions that seems implausible given the history. If it does happen, it will mostly be an indictment of everyone who could have used technology we had in 1925, the venerable "look at your fucking business processes and ask your more competent people some questions, dumbass" to identify gaps; and I suspect that it mostly won't happen. You'll probably get some projects that are mostly about saving face for whoever vibe-coded their way into the problem and overpromised; but it's not like the bot codebase will be more useful to the programmer than the user who failed to make it work just telling them what they actually need would be; which is something we've been able to do(albeit mostly bad at doing) since forever.
I suppose that there is a slim possibility that this 'vibe coding' will somehow convince management in ways that Access didn't, by being better at giving the illusion of being a slick solution that just needs a little more fixing; but there's nothing about the past quarter century of no-code/low-code or the last more-or-less-forever of "understand what it is your employees do and what would be useful for doing it" that suggests that people are particularly good at getting software to those in need of it.
If 'AI' tooling makes it radically cheaper to actually get to a final, working, tool then perhaps it will increase the absolute number of programming jobs if 'dude from fivver' replaces 'access' as the de-facto barely adequate unmaintainable solution; but if the idea is that somehow 'AI' will increase the number of actually costly programmers getting thrown at problems because it's easier for amateurs to produce broken non-solutions that seems implausible given the history. If it does happen, it will mostly be an indictment of everyone who could have used technology we had in 1925, the venerable "look at your fucking business processes and ask your more competent people some questions, dumbass" to identify gaps; and I suspect that it mostly won't happen. You'll probably get some projects that are mostly about saving face for whoever vibe-coded their way into the problem and overpromised; but it's not like the bot codebase will be more useful to the programmer than the user who failed to make it work just telling them what they actually need would be; which is something we've been able to do(albeit mostly bad at doing) since forever.