workflow· 1 min read
The rise of vibe coding
Writing code at the speed of thought, and what that does to the parts of a codebase nobody wants to own.
Jane Doe · Engineering
The interesting thing about generating code quickly is not the speed. It is what happens to the boring parts of a codebase when they stop being expensive.
The boring parts were load-bearing
Authentication, tenancy and billing were slow to write, so teams wrote them once and treated them as settled. When they become cheap to produce, they also become cheap to produce badly — and a role check that looks right is much harder to spot than one that is missing.
Review moves, it doesn't disappear
The unit of review shifts from the line to the boundary. Who can call this? What happens on the second delivery? What does this leak when it fails?