# Cheap Generation Raises the Total Maintenance Bill ## Claim Lowering the cost of producing software does not lower the cost of owning it — it raises the total maintenance burden, because every cheaply-generated artifact still has to be sustained by someone, and generation is exactly the part of the lifecycle that was never the constraint. <!-- atomicity: 1 idea ✓ --> ## Evidence **Source**: Brian Coords (Woo), "Maintaining over Building," reinforced by the MemberPress "vibe-coding hangover" data and the wp2shell core-RCE. > [!quote] > Meanwhile 90% of the stuff I've vibe-coded is sitting on GitHub, gathering dust. Coords is Exhibit A for his own claim: AI made building cheap without making upkeep cheap, so he generates more and sustains almost none of it. A team he cites reverted from a vibecoded internal tool back to Linear because *maintaining* it exceeded its value — the build was free, the upkeep wasn't. The same 90%-abandonment shape appears in MemberPress's vibe-coded-startup figures, reached from the market side rather than personal experience. The distinguishing variable is persistence: disposable artifacts (a landing page, a one-off script) carry no maintenance and are exactly where cheap generation legitimately wins; durable software is where the bill comes due. ## Scope & conditions - Holds wherever generated artifacts persist and require upkeep — code, content, infrastructure, documentation. The cheaper generation gets, the more artifacts exist, and maintenance is the constraint that does not scale down with generation cost. - On a large install base the bill is also a security bill: "caution scales with the install base" because a mistake's blast radius does (wp2shell — one core bug, millions of sites), so maintenance capacity *is* vulnerability-surface capacity. - Breaks for genuinely disposable artifacts where no maintenance is ever required — the boundary is not complexity per se but whether the thing must last. ## Links - [[3. Resources/Permanent Notes/Maintenance Is Most of the Work but Gets No Prestige]] — extends: that note explains why maintenance is undervalued *labor*; this one adds the AI-era inversion that cheap generation actively *grows* the maintenance pile it doesn't fund - [[3. Resources/Permanent Notes/Zero Build Cost Shifts Advantage From Depth to Breadth]] — applies-in: when generation is free the advantage moves to breadth, but breadth is precisely what multiplies the artifacts someone must later sustain - [[3. Resources/Permanent Notes/Perm · Vibecoding bypasses CMS entirely, draining relative share to 'None']] — evidence-for: the market split — vibe-coding takes the disposable low end (where no maintenance is owed) while durable publishing/commerce stays on maintained platforms - [[3. Resources/Permanent Notes/WordPress's Compatibility-First Culture Is Now Its Binding Security Constraint]] — applies-in: a huge install base makes caution mandatory, which is the maintenance-is-security-capacity corollary of this claim - [[AI & the Future of Knowledge Work MOC]] — applies-in: reframes the AI-productivity story — if generation is cheap and upkeep isn't, net maintenance debt may accumulate faster than it is serviced - [[3. Resources/Permanent Notes/A Nightly Agent Rebase Makes a Personal Fork Cheap Enough to Keep]] — contrasts: maintenance, not writing, kills personal software; a nightly rebase removes that cost for small patch sets (Crawshaw). - [[3. Resources/MOCs/WordPress Hosting Security Stack MOC]] — applies-in: the MOC lists it as the security corollary of its cluster, since maintenance capacity sets vulnerability surface on a large install base. ## Why This Matters The dominant AI-productivity narrative measures time-to-first-version, which AI compresses dramatically — and ignores lifecycle cost, which it does not. For anyone using AI to build: the afternoon it took to make the thing is the smallest cost it will ever have. For platform strategy, it argues for treating "maintenance mode" as a stated, funded, announceable discipline (Woo's Core Foundations quarter) rather than a lull — and for treating a maintenance quarter as a hardening quarter. ## Source - [[3. Resources/Readwise/Articles/Maintaining Over Building]] — the maintainer's-chair argument; 90%-abandoned; revert-to-Linear; the MacSparky "one big thing + a thousand small fixes" cadence - [WordPress Lost Market Share and Got Stronger. Here's Why.](3.%20Resources/Readwise/Articles/WordPress%20Lost%20Market%20Share%20and%20Got%20Stronger.%20Here's%20Why..md) — the vibe-coding-hangover data (Veracode/Escape.tech) from the market-share side - [[3. Resources/Readwise/Articles/Wp2shell (CVE-2026-63030 & CVE-2026-60137) — Full Pre-Auth WordPress RCE Chain]] — the security extreme of "caution scales with install base": one core bug, millions of sites