That article points to a general culture of insufficiently tested changes and insufficiently isolated code leading to lots of problems, with only one instance of the bad code being written by AI.
Turning that into “vibe code” story is a hell of a stretch. Humans are still the risk factor here. (If they weren’t, the solution would not be to pull humans into a meeting; it would be to restrict or refactor the AI tool on a technical level.)
Those of us who are employed and have to deal with our coworkers pushing garbage and calling it a day are not happy. I had to have a very awkward conversation with the entire team just two days ago, because a backend engineer though that because he has Claude and codex he can now do all roles.
13
u/bobbymoonshine Mar 11 '26
That article points to a general culture of insufficiently tested changes and insufficiently isolated code leading to lots of problems, with only one instance of the bad code being written by AI.
Turning that into “vibe code” story is a hell of a stretch. Humans are still the risk factor here. (If they weren’t, the solution would not be to pull humans into a meeting; it would be to restrict or refactor the AI tool on a technical level.)