Vibe Coding: Generating tech debt at the speed of light

>The leaderboard isn't "PRs opened per week." It's not "lines of code generated." It's "months since the last mass refactor." Time between architectural resets. How long your codebase stays coherent under continuous AI-assisted modification.

This was a good one, however we cannot absolutely rely on this from a metric perspective. Code velocity should also be included as a factor, like PR dwell time and time to first PR (especially for new hires)

The irony of this being completely written by Claude.

When you’ve worked with Claude intimately you instantly recognise it’s writing:

- littered with “It’s not X, it’s Y.”

- Short. Punchy. Triplets.

- Overexaggeration.