dette technique

Kent Beck, creator of test-driven development, framed the mechanism directly in an October 2024 LinkedIn post: AI amplifies the consequences of undisciplined development. Coding faster without tests means accumulating technical debt faster. That framing recurs across the source notes, with different actors reaching it from different directions.

Itamar Friedman, CEO of QodoAI, put figures on the accumulation in November 2025: pull request volume up 97%, review time up 90%, security incidents up 300% by some reports, while 67% of developers voiced concern about the quality and maintainability of generated code. Martin Harrison and Natasha Maniar of McKinsey described the same bottleneck from the delivery side, where large enterprises plateau at 5 to 15% overall improvement despite spectacular individual gains, manual code review being one of the choke points.

Addy Osmani drew the line as a semantic one: «vibe coding» suits prototypes and throwaway weekend projects, while AI-assisted engineering keeps the human engineer accountable for every generated line. Philippe Martin's BMAD method and EveryInc's «plugin Compound Engineering» both attack the problem structurally, the latter by making each unit of work document patterns and codify conventions so the codebase improves rather than degrades.

What none of the sources settle is the ownership question Edgar Kussberg raises: developers accept AI suggestions without deep examination, which breaks code ownership. The debt is measurable. Who holds it is not.