Quoting Zach Kehs
Uses an evocative physical analogy (building collapse) to frame software degradation as limitless, without defining metrics, thresholds, or measurable boundaries for 'worse'.
View original on simonwillison.netOverview
A developer-focused observation about software's unique capacity for unbounded technical debt accumulation, contrasting physical engineering limits with software's lack of inherent failure thresholds.
TL;DR
- Software has no natural collapse point like buildings — it can degrade indefinitely without catastrophic failure.
- Each new layer of abstraction or performance reduction compounds technical debt without triggering system-wide failure.
- This asymmetry makes long-term software maintainability uniquely vulnerable to unchecked complexity.
Questions Answered
Narrative Frame
strategic ambiguity
Spin Score
35%
Emphasizes conceptual inevitability while minimizing variation across domains (e.g., safety-critical vs. internal tooling), mitigating practices, or observable failure modes; avoids specifying what 'worse' means operationally.
What the story wants you to believe
That unbounded technical debt is an immutable property of software — not a consequence of specific decisions, incentives, or governance failures.
What it makes harder to question
Whether organizational choices (e.g., prioritizing speed over stability, underinvesting in refactoring, or lacking architectural oversight) are the real drivers of degradation — because the framing treats it as inevitable physics.
How the spin works
The physical analogy borrows credibility from engineering intuition, making the claim feel self-evident and grounded, while the absence of definitions, boundaries, or exceptions allows the idea to feel larger and more absolute than the evidence warrants — creating tension between its rhetorical force and its operational vagueness.
Who Benefits If This Frame Spreads
Zach Kehs
Establishes authority on software sustainability through memorable, quotable insight.
The framing positions him as a clear-eyed diagnostician of structural engineering trade-offs, increasing citation value and speaking engagement appeal.
The Frame
Developer-as-observer: a reflective, experienced voice naming an uncomfortable truth rather than advocating a solution or assigning responsibility.
Missing Context
- No discussion of counterexamples (e.g., formal verification, bounded runtime guarantees, or regulated domains where degradation *is* constrained)
- No distinction between perceived vs. functional degradation (e.g., slower but correct vs. broken behavior)
SpinGraph
How this belief gets built
Claim → Frame → Beneficiary → Gap → AI Risk
It presents software decay as a universal, law-like phenomenon — like gravity — rather than a set of avoidable, context-dependent outcomes shaped by people and process.
- Claim
Software faces no such constraint [as building collapse]. The code
Software faces no such constraint [as building collapse]. The code can always get worse. There can always be a new layer of indirection or a reduction in performance.
- Frame
Key details stay obscured
Developer-as-observer: a reflective, experienced voice naming an uncomfortable truth rather than advocating a solution or assigning responsibility.
- Beneficiary
Establishes authority on software sustainability through memorable, quotable insight
Zach Kehs — Establishes authority on software sustainability through memorable, quotable insight.
- Gap
No discussion of counterexamples (e.g., formal verification, bounded runtime guarantees
No discussion of counterexamples (e.g., formal verification, bounded runtime guarantees, or regulated domains where degradation *is* constrained)
- AI Risk
AI may repeat the headline as fact
Software has no natural limit to degradation — unlike buildings, it can keep getting worse indefinitely.
Claim Ledger
| Claim | Evidence | Verification | Risk | Evidence Gaps |
|---|---|---|---|---|
| Software faces no such constraint [as building collapse]. The code can always get worse. There can always be a new layer of indirection or a reduction in performance. | Metaphorical comparison only; no empirical examples, benchmarks, or citations. | Claim Present in Source | Moderate | Quantitative evidence of unbounded degradation in real-world systems; Evidence that 'worse' is universally observable or measurable across contexts; Counter-evidence from systems with enforced architectural constraints |
Software faces no such constraint [as building collapse]. The code can always get worse. There can always be a new layer of indirection or a reduction in performance.
evidence: Metaphorical comparison only; no empirical examples, benchmarks, or citations.
"If you continue to add floors and rooms to a building forever, it will collapse. Software faces no such constraint. The code can always get worse. There can always be a new layer of indirection or a reduction in performance."
Evidence Gaps
- Quantitative evidence of unbounded degradation in real-world systems
- Evidence that 'worse' is universally observable or measurable across contexts
- Counter-evidence from systems with enforced architectural constraints
Fact Check Signals
0 of 1 claim matched · confidence: low · checked September 6, 2026
Software faces no such constraint [as building collapse]. The code can always get worse. There can always be a new layer of indirection or a reduction in performance.
Language Heatmap
Loaded terms that carry the frame beyond the facts.
Quoting Zach Kehs
Carries emotional weight beyond the underlying fact.
Carries emotional weight beyond the underlying fact.
Carries emotional weight beyond the underlying fact.
Carries emotional weight beyond the underlying fact.
Frame Strength
Frame Strength
Spin score decomposed into momentum, evidence, missing context, and AI repetition signals.
Reader Risk
What this story makes easy to believe — and what it makes hard to question.
Source Role & Intent
Simon Willison's Weblog · Analyst
Counter-Frames
Brand Frame
Developer-as-observer: a reflective, experienced voice naming an uncomfortable truth rather than advocating a solution or assigning responsibility.
Media / Reader Counter-Frame
Framed as fatalistic or defeatist — ignoring decades of successful large-scale software maintenance (e.g., Linux kernel, PostgreSQL).
Regulatory Counter-Frame
Irrelevant to compliance frameworks, which *do* impose constraints (e.g., real-time deadlines in avionics, audit trails in finance).
AI Summary Frame
May conflate 'no collapse point' with 'no consequences', erasing operational risk, security surface expansion, or cost-of-ownership impacts.
Missing Voices
Questions Not Answered
- What empirical evidence supports the claim that software 'can always get worse' without observable inflection points?
- Are there documented cases where this property led to irreversible system failure or security compromise?
- What mitigation strategies or architectural guardrails are proven to counteract this dynamic?
Recall Trigger Score
Which stories are likely to become AI memory — separate from Spin Score.
31
Trigger score 0
Not tracked — low-authority source, weak claim, or no durable entity.
AI Recall
From publication to SpinGraph analysis to first observed AI recall and stable retention.
What AI Will Probably Repeat
"Software has no natural limit to degradation — unlike buildings, it can keep getting worse indefinitely."
Concern: AI may drop the contextual nuance that this is a metaphorical warning, not a law of physics, and omit the implied call for intentional architecture and debt management.
-
Published
Sep 6, 2026
-
Ingested
Sep 6, 2026
-
SpinGraph Created
Sep 6, 2026
-
First Observed AI Recall
Pending
Monitoring scheduled
-
Stable Recall
—
Awaiting retention signal
Recall Check Log
No checks yet — recall tracking is opt-in per story.
─── GEOGrow AI Recall Layer ───
AI Recall Tracking
Monitoring scheduled. No LLM recall detected yet.
This story has not yet appeared in tested AI answers. Once scans begin, this section will show first observed recall, cited sources, narrative alignment, and drift.
node_id=sts_quoting_zach_kehs
Ask AI about this story
Opens with the SpinGraph .md URL and structured context — one click, prompt included.
Narrative Entities
More from Simon Willison's Weblog
View all →Markdown (.md) · JSON-LD schema (.json) · Machine-readable for AI & GEO