I've been a software engineer for over 30 years and I have to say using AI and vibe coding has made me a 10x programmer. It's all about prompting and debugging, knowing how to fix issues is still a necessary skill and how to build/architect things from a prompt perspective. I've released 8 npm modules in the past 2 weeks alone just for some silly stuff I was using.
Coding since 1986, and what I see is the dream of CASE tooling finally coming true, eventually as AI matures, assuming we aren't getting through yet another AI cycle that will stabilize until the next wave, I see ourselves writing requirements documents in a UML kind of way (in spirit, doesn't need to be boxes and arrows) for AI minions to actually do the work with one third of current team sizes.
The other two thirds can search for something else, just like the factory workers when robots took over most factory roles.
The remaining one third, are the folks doing the jobs robots can't yet do, or doing their maintenance.
Software factories are no different from physical ones, in this regard, a few iluminaries will be able to profit from AI, everyone else needs to re-train themselves.
They said 'maybe'. I'm gonna say they are right, because there is no need for 99%+ of npm modules (and indeed, by far most are not used by anyone except the org author). Especially with AI, most npms are trivially generated faster than you can find and install them and usually less influenced/opinionated by the usually terrible star vying programmer that uploaded it in the first place. If AI trivially generates your npm (so you can make 4 per week next to whatever you were doing), why would I need it instead of having AI trivially generating a specific (without the features I don't need) version for what I am doing at the moment?
Ok
I've been a software engineer for over 30 years and I have to say using AI and vibe coding has made me a 10x programmer. It's all about prompting and debugging, knowing how to fix issues is still a necessary skill and how to build/architect things from a prompt perspective. I've released 8 npm modules in the past 2 weeks alone just for some silly stuff I was using.
Coding since 1986, and what I see is the dream of CASE tooling finally coming true, eventually as AI matures, assuming we aren't getting through yet another AI cycle that will stabilize until the next wave, I see ourselves writing requirements documents in a UML kind of way (in spirit, doesn't need to be boxes and arrows) for AI minions to actually do the work with one third of current team sizes.
The other two thirds can search for something else, just like the factory workers when robots took over most factory roles.
The remaining one third, are the folks doing the jobs robots can't yet do, or doing their maintenance.
Software factories are no different from physical ones, in this regard, a few iluminaries will be able to profit from AI, everyone else needs to re-train themselves.
Maybe there was no need for 8 more npm modules ... is_odd ...
Finally the treadmill of endlessly reinventing JavaScript frameworks and libraries is available for us Joe Schmoes too.
How do you know? I'd have to see those modules first to have an opinion.
They said 'maybe'. I'm gonna say they are right, because there is no need for 99%+ of npm modules (and indeed, by far most are not used by anyone except the org author). Especially with AI, most npms are trivially generated faster than you can find and install them and usually less influenced/opinionated by the usually terrible star vying programmer that uploaded it in the first place. If AI trivially generates your npm (so you can make 4 per week next to whatever you were doing), why would I need it instead of having AI trivially generating a specific (without the features I don't need) version for what I am doing at the moment?