SPIN Processed
Source Simon Willison's Weblog simonwillison.net Analyst Center
September 6, 2026 developer_practice developer

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.net

Overview

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

What happened?Who is involved?Why does this matter?

Narrative Frame

strategic ambiguity

The Fog

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)

Spin Types

Every story gets a Spin Verdict: a primary spin type (and secondary when the framing blends), a specific tactic name, and a score for how strongly the narrative is steered. Examples beneath each type are tactics, not separate categories.

The Cushion

— Softens negative news

Reframes setbacks, layoffs, delays, losses, or criticism as necessary transitions, efficiency moves, temporary headwinds, or strategic resets — making the downside feel smaller, more acceptable, or less alarming.

Tactics: job-loss softening · restructuring framing · efficiency framing · strategic reset · temporary headwinds

The Shield

— Deflects blame

Shifts responsibility away from the actor — toward regulators, market forces, competitors, bad actors, legacy systems, or abstract risks — while positioning the subject as reactive, responsible, or protective.

Tactics: regulatory blame shift · macroeconomic headwinds · safety framing · bad-actor framing · market-pressure framing

The Hype

— Amplifies future upside

Emphasizes breakthrough potential, massive growth, democratization, transformation, or category disruption while downplaying uncertainty, cost, adoption risk, or timeline friction.

Tactics: innovation framing · democratization · breakthrough framing · category creation · moonshot framing

The Halo

— Associates with virtue

Wraps the story in public-good language — responsibility, safety, inclusion, access, sustainability, national interest, or mission — so the subject appears morally aligned and criticism feels harder to make.

Tactics: altruistic reframing · public good · responsible AI framing · inclusion framing · mission-first framing

The Fog

— Obscures details primary

Uses jargon, passive voice, vague claims, complex phrasing, or missing specifics to make it harder to identify who decided what, what changed, what failed, or what trade-offs were made.

Tactics: strategic ambiguity · jargon saturation · passive voice distancing · accountability blur · undefined metrics

The Stampede

— Creates inevitability

Frames a trend, product, market shift, or decision as already happening, unavoidable, or something everyone must respond to now — creating urgency, FOMO, and pressure to accept the narrative.

Tactics: arms-race framing · inevitability framing · FOMO framing · adoption momentum · future-is-here framing

Spin Score measures how strongly the framing steers the narrative (0–100%). Higher scores mean more deliberate spin tactics — loaded language, selective emphasis, or omitted context. Many stories blend two types (e.g. Halo + Hype).

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.

  1. 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.

  2. Frame

    Key details stay obscured

    Developer-as-observer: a reflective, experienced voice naming an uncomfortable truth rather than advocating a solution or assigning responsibility.

  3. Beneficiary

    Establishes authority on software sustainability through memorable, quotable insight

    Zach Kehs — Establishes authority on software sustainability through memorable, quotable insight.

  4. 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)

  5. 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

01 Primary Technical Claim Present in Source risk:Moderate

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

No direct fact-check match found

0 of 1 claim matched · confidence: low · checked September 6, 2026

01 No direct match

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.

Fact Check Signals

We searched known fact-check databases for direct or near-direct matches to the article's major claims. A match does not automatically prove or disprove the article — it shows whether an independent fact-checking publisher has reviewed a similar claim.

  • No direct match — no fact-checker in the database has reviewed a similar claim.
  • Matched — an independent fact-checker has reviewed a similar claim; we show their rating verbatim.
  • Conflicting coverage — fact-checkers disagree on a similar claim.

This is evidence discovery, not an automated truth score. Ratings and wording come directly from the publishing fact-checker.

Language Heatmap

Loaded terms that carry the frame beyond the facts.

Quoting Zach Kehs

collapse Loaded framing

Carries emotional weight beyond the underlying fact.

no such constraint Loaded framing

Carries emotional weight beyond the underlying fact.

always get worse Loaded framing

Carries emotional weight beyond the underlying fact.

no limit Loaded framing

Carries emotional weight beyond the underlying fact.

Frame Strength

Frame Strength

Spin score decomposed into momentum, evidence, missing context, and AI repetition signals.

Spin Score 35%
Evidence Strength 25%
Narrative Risk 25%
AI Repetition Risk 75%
Missing Context Risk 70%

Frame Strength Signals

Frame Strength decomposes the overall spin into individual signals. Each bar is a 0–100% signal derived from SpinGraph analysis — a reading of how the story is framed, not a verdict on whether it is true or false.

Reading the ranges

Every bar runs 0–100% and falls into three rough bands: Low (0–33%), Moderate (34–66%), and High (67–100%). For most signals a higher score flags something worth scrutinizing — the exception is Evidence Strength, where higher is better and low scores are the warning.

Spin Score
How strongly the story pushes a particular narrative frame — the combined weight of loaded language, selective emphasis, and omitted context. 0% reads as neutral reporting; higher means more deliberate spin.
  • 0–33% Low — Largely neutral reporting; little detectable framing.
  • 34–66% Moderate — Noticeable slant — the story leans a particular way.
  • 67–100% High — Heavily framed; the angle drives the piece.
Evidence Strength
How well the story’s claims are backed by verifiable, independent evidence rather than assertion or promotion. Higher is stronger. Low scores flag claims that rest on the source’s own word.
  • 0–33% Weak — Claims rest mostly on assertion or a single interested source.
  • 34–66% Mixed — Some verifiable backing, but key claims are thinly sourced.
  • 67–100% Strong — Well supported by independent, checkable evidence.
Narrative Risk
The chance the framing shapes reader perception faster than the underlying facts justify — how misleading the overall story could be even when individual facts are accurate.
  • 0–33% Low — Framing stays close to what the facts support.
  • 34–66% Moderate — Framing outruns the facts in places — read with care.
  • 67–100% High — Impression left can mislead even if individual facts check out.
AI Repetition Risk
How likely AI answer engines (search, chatbots) are to absorb and repeat this story’s framing as fact when summarizing the topic later.
  • 0–33% Low — Framing is unlikely to propagate through AI summaries.
  • 34–66% Moderate — Some risk the slant gets echoed as fact.
  • 67–100% High — Framing is sticky and likely to be repeated as fact.
Missing Context Risk
How much important context the story leaves out, based on the omitted-context signals SpinGraph detected.
  • 0–33% Low — Little material context appears to be omitted.
  • 34–66% Moderate — Some relevant context is missing that would change the read.
  • 67–100% High — Key context is left out, skewing the takeaway.
Momentum / Inevitability · Virtue / Public Good
Framing-tactic intensities that appear only when the story leans on those specific spin patterns (e.g. “the future is already here” or “this is for the public good”).
  • 0–33% Low — The tactic is barely present.
  • 34–66% Moderate — The tactic shapes part of the framing.
  • 67–100% High — The tactic is a dominant part of the pitch.

Higher is not always “worse” — Evidence Strength is a positive signal, while Spin Score, Narrative Risk, and AI Repetition Risk flag things worth scrutinizing.

Reader Risk

What this story makes easy to believe — and what it makes hard to question.

Evidence Strength

Low

The claim is presented as an aphorism, not supported by data, case studies, or citations; relies entirely on rhetorical analogy.

Verification Status

Claim Present in Source

Narrative Risk

Low

As a short, non-assertive observation without policy, product, or financial claims, it lacks concrete hooks for reputational backfire — though overgeneralization could draw expert pushback.

AI Repetition Risk

Moderate

Source Role & Intent

Simon Willison's Weblog · Analyst

Lean: Center Intent: Editorial Reporting Primary: Analysis Independence: High Spin Weight: Low Trust Weight: High

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.

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

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.

  1. Published

    Sep 6, 2026

  2. Ingested

    Sep 6, 2026

  3. SpinGraph Created

    Sep 6, 2026

  4. First Observed AI Recall

    Pending

    Monitoring scheduled

  5. Stable Recall

    Awaiting retention signal

Recall Check Log

No checks yet — recall tracking is opt-in per story.

Sign in to check AI recall

─── 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