> [!question] Lingering Questions > - What would change this claim if it turned out to be wrong, and where's the strongest counter-evidence? > [!idea] Article Ideas > - Code duplication (5+ consecutive repeated meaningful lines) rose 81% in the AI-coding era, directly eroding DRY. > [!info] Cross Reference > - See MOC links below for the cluster this note belongs to. > [!abstract] Vocabulary > - (no source-specific jargon requiring definition in this piece) --- ## Metadata - **Source:** [[3. Resources/Readwise/Articles/Code maintainability plummets in the AI coding era]] - **Author:** leaddev.com - **URL:** https://leaddev.com/ai/code-maintainability-plummets-in-the-ai-coding-era - **Type:** article - **Citekey:** leaddev-ai-code-maintainability-2026 ## Links - [[3. Resources/MOCs/AI & the Future of Knowledge Work MOC.md]] ## Author's thesis **Q1 (What is the author saying?):** GitClear's analysis of AI-assisted commits, corroborated independently by Google's DORA data, finds that AI coding tools systematically trade away maintainability — raising code duplication, increasing error-masking instead of fixing root causes, and letting legacy code go untended — because the tools optimize for satisfying the immediate prompt rather than for the codebase's long-term health. **Q2 (Why should the reader care?):** It reframes a widely-assumed cause-and-effect relationship with concrete, checkable evidence, which changes what action is worth taking next. ## Key arguments 1. Code duplication (5+ consecutive repeated meaningful lines) rose 81% in the AI-coding era, directly eroding DRY. 2. AI "strongly prefers to write code that won't be labeled as a defect," pushing obfuscation/error-masking up 47% instead of fixing root causes. 3. Legacy refactoring (touching code untouched for 12+ months) fell 74% since 2023, and Google's independent DORA 2024 data corroborates rising instability: every 25% more AI usage tracks with 7.2% more instability. ## Claim atoms ### AI coding raises duplication and lowers reuse > [!quote] ID:rw_leaddev-ai-code-maintainability-2026_1 > duplication was tracked as occurrences of five or more consecutive repeated meaningful lines - Body: quantifies the +81% duplication rise. - Quantifies DRY erosion; the headline maintainability regression to cite. ### AI hides errors instead of fixing their cause > [!quote] ID:rw_leaddev-ai-code-maintainability-2026_2 > AI strongly prefers to write code that won't be labeled as a defect - Harding quote; obfuscation (error masking) up 47% year over base. - Explains shallow apps and confusing user behavior from silent catches. ### Legacy code is being left untended > [!quote] ID:rw_leaddev-ai-code-maintainability-2026_3 > Since 2023, it has fallen 74%. - "Legacy refactoring" = changes to code last touched >12 months ago. - Developers build new instead of maintaining; functional connectivity also −35%. ### More AI usage tracks with more instability > [!quote] ID:rw_leaddev-ai-code-maintainability-2026_4 > every 25% of additional AI usage creates 7.2% more instability - Google DORA 2024 corroboration, independent of GitClear. - Triangulates the maintainability-decline thesis. ## Permanent candidates #### AI Coding Optimizes For Prompts, Not Maintainability AI coding tools optimize for satisfying the immediate prompt, which systematically trades away the reuse, legacy care, and honest error handling that keep a codebase maintainable. ## Processing checklist - [x] Bib capsule complete - [x] Thesis captured (Q1 + Q2) - [x] Key arguments extracted (≤3) - [x] Permanent note candidate(s) spun out - [ ] Cross-links reviewed by next sweep