Vibe Coding vs Engineering: Where to Draw the Line in Real Projects

Description and use

<p>Last month a client sent me a message that started with "it was working yesterday" and ended with "can you fix it today." In between those two lines was a login system that an AI tool had generated in about four minutes, that nobody had actually read, and that had quietly been letting a password reset link work even after the password was already reset.</p> <p>Nobody caught it because nobody looked. The code ran. The demo worked. The client was happy for exactly nine days.</p> <p>This is the story behind almost every vibe coding horror story you have read this year, and it is also the reaso

Problem

<p>Last month a client sent me a message that started with "it was working yesterday" and ended with "can you fix it today." In between those two lines was a login system that an AI tool had generated in about four minutes, that nobody had actually read, and that had quietly been letting a password reset link work even after the password was already reset.</p> <p>Nobody caught it because nobody looked. The code ran. The demo worked. The client was happy for exactly nine days.</p> <p>This is the story behind almost every vibe coding horror story you have read this year, and it is also the reaso

Outcome

<p>Last month a client sent me a message that started with "it was working yesterday" and ended with "can you fix it today." In between those two lines was a login system that an AI tool had generated in about four minutes, that nobody had actually read, and that had quietly been letting a password reset link work even after the password was already reset.</p> <p>Nobody caught it because nobody looked. The code ran. The demo worked. The client was happy for exactly nine days.</p> <p>This is the story behind almost every vibe coding horror story you have read this year, and it is also the reaso

Evidence

Vibe Coding vs Engineering: Where to Draw the Line in Real Projects

Source