> with vibe coding you can't cast aside the AI after you've taken the initial step
Sure you can, why wouldn't you? Good models these days spit out architecture and code fairly indistinguishable from your average developer.
It's always hard to jump into an existing project and understand it all, but it's doable and in 2026 it's no harder to jump into a vibed project than it is to jump into any other project (with exceptions in both directions, of course).
You still have the code and can switch back to "fully human" (or any other point on the spectrum of human-ai) any time you want by just opening the same editor you would use if you cloned any other project.
You can do this if you hold its hand a lot. Claude by default will do insane levels of abstraction for small things. Also make Python docstrings 3x longer than the actual code.
dimbletimbers · · focus · HN ↗
impendia · · focus · HN ↗
And I think that's one important difference: with vibe coding you can't cast aside the AI after you've taken the initial step.
drusepth · · focus · HN ↗
Sure you can, why wouldn't you? Good models these days spit out architecture and code fairly indistinguishable from your average developer.
It's always hard to jump into an existing project and understand it all, but it's doable and in 2026 it's no harder to jump into a vibed project than it is to jump into any other project (with exceptions in both directions, of course).
You still have the code and can switch back to "fully human" (or any other point on the spectrum of human-ai) any time you want by just opening the same editor you would use if you cloned any other project.
jdkoeck · · focus · HN ↗
Emphatically, no. It’s way too complex, every time. Ceinture et bretelles, as we say in French.
jldl805 · · focus · HN ↗
mahboi · · focus · HN ↗
NewJazz · · focus · HN ↗
graemep · · focus · HN ↗
jdkoeck · · focus · HN ↗