> Overall, LLMs aren’t yet at the point where they can replace all engineers. But I don’t doubt they will be soon enough, and in the meantime, they just can’t be ignored
Someone has to maintain that code and there is not a single mention of that caveat after the software is built in the article and 99.9999% of the most widely used software is maintained by humans - even if parts of it was vibe-coded, a human has to maintain it so that it functions correctly, especially a must if it is mission critical software.
It is like we are celebrating mediocrity under the guise of AI and rebranding 'prototyping' as 'vibe-coding' but worse - software with fast accumulating technical debt, slapping on third-party risks and close to no tests at all.
Eventually, someone has to maintain that software and surely 9 times out of 10, a typical senior software engineer will look at that vibe-coded slop and will either throw it all away or reduce these third party services with existing robust open source versions.
Vibe-coding gets you faster to maintain the same negatives from traditional software engineering without you understanding what you are doing.
Someone has to maintain that code and there is not a single mention of that caveat after the software is built in the article and 99.9999% of the most widely used software is maintained by humans - even if parts of it was vibe-coded, a human has to maintain it so that it functions correctly, especially a must if it is mission critical software.
It is like we are celebrating mediocrity under the guise of AI and rebranding 'prototyping' as 'vibe-coding' but worse - software with fast accumulating technical debt, slapping on third-party risks and close to no tests at all.
Eventually, someone has to maintain that software and surely 9 times out of 10, a typical senior software engineer will look at that vibe-coded slop and will either throw it all away or reduce these third party services with existing robust open source versions.
Vibe-coding gets you faster to maintain the same negatives from traditional software engineering without you understanding what you are doing.