I do a lot of “disconnected coding,” think scripts that do a long and complicated calculation, triggered manually by a few users, and aren’t online services. In these cases vibe coding is pretty great: if something doesn’t work the first time, I can iterate easily till it does. Very few consequences in getting it wrong other than time. My hand is also very firmly on the wheel and I have a lot of time to think about changes to fix issues or make things better.
Now for an online service with very specific requirements on how it handles inputs and produces outputs, at scale, with security issues, and millions of people using it…yeah I’d be pulling my hair out too if I had to vibe code all that.
I do a lot of “disconnected coding,” think scripts that do a long and complicated calculation, triggered manually by a few users, and aren’t online services. In these cases vibe coding is pretty great: if something doesn’t work the first time, I can iterate easily till it does. Very few consequences in getting it wrong other than time. My hand is also very firmly on the wheel and I have a lot of time to think about changes to fix issues or make things better.
Now for an online service with very specific requirements on how it handles inputs and produces outputs, at scale, with security issues, and millions of people using it…yeah I’d be pulling my hair out too if I had to vibe code all that.
Spoiler alert: the teams have been pulling their hair out doing all that for decades without vibe coding it.
Cha-ching!