- What vibe coding changes is the prototyping phase. Going from 0->1 doesn’t take a team. You need the team, like you say, to get to the next level of scaling or complexity (at least for now)
- We have to realize the next generation of programmers are 10 years old right now, and the next generation of business owners are also about that age. There will be a gap between technical expertise between the two, as usual, hence leading to business. Just like we saw, our business owners did not give two shits about how things work and why they break, so long as they work, and so long as things are fixed (however the heck). So, if the new generation of coders vibe code their ass off to make things and vibe code their ass off to fix things, that will be the new nature of programming work. The business has never cared for the most part.
- Fixing things requires more finess than adding features. Because it needs to be fixed. Not fixed means you are out of business. Vibe coding is rolling a dice to see if something works. The question is whether these systems can stack that dice to converge to self healing within the time needed.
Maybe they will maybe they won't, or maybe it depends on the problem.
I think you need a expert human in the loop. Maybe fewer of them for a given weight of functionality.
