The most dangerous thing about vibe coding

The most dangerous thing about vibe coding (especially from non-domain engineers) is not AI writing bad code, it’s people building things that should never have been built in the first place. Tactical solutions where the problem space is misunderstood or not well shaped. Solving automation issues which shouldn’t exist if the workflow could be re-imagined or redesigned properly. Cool & shiny new tools and services to solve non-problems but serve as novelty. Re-inventing wheels at a scale never before seen. And it’s not (only) about the cost of maintenance - it’s the whole human structure around the code and tools, that will now bend to people not thinking deeply enough about what they built. The fact it now can easily be done, doesn’t mean it 𝘴𝘩𝘰𝘶𝘭𝘥.

Originally posted on LinkedIn (opens in a new tab), July 2026.