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

Dwarf Fortress uses version control now

Frames the adoption of version control not as a correction of prior deficiency, but as a natural, mature evolution aligned with growth and new operational realities.

View original on simonwillison.net

Overview

Dwarf Fortress, long known for its deliberate avoidance of version control, has adopted it as part of operational scaling following its Steam release and commercial success.

TL;DR

  • Dwarf Fortress creator Tarn Adams publicly resisted version control for over 15 years, citing philosophical and workflow objections.
  • As of March 2023, Adams confirmed adopting version control alongside Discord-based coordination, coinciding with the game's Steam launch and financial milestone.
  • The shift reflects adaptation to team-scale collaboration and external distribution—not a technical necessity for the solo-developed codebase itself.

Key Stats

15 years

duration of version control avoidance

Self-reported by Tarn Adams across multiple interviews

2023

adoption year

Confirmed in March 2023 interview about Steam release

Questions Answered

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

Narrative Frame

strategic reset

The Cushion

Spin Score

45%

Emphasizes continuity and inevitability of change; minimizes the significance of the prior 15-year stance as ideological resistance or technical risk, and omits any acknowledgment of potential instability or friction introduced by the shift.

What the story wants you to believe

That adopting version control was a calm, logical step in Dwarf Fortress’s evolution—not a concession or correction.

What it makes harder to question

Whether the prior 15-year stance posed real technical debt, collaboration bottlenecks, or sustainability risks that were downplayed in favor of romanticizing solo development.

How the spin works

The story frames a shift as already underway, inevitable, or broadly accepted so resistance or skepticism feels out of step. Watch for loaded terms such as gave in, impressive run, art, black box thingy. The distribution reads as editorial reporting. A pressure point: No discussion of version control’s role in enabling Steam certification or third-party modding support.

Who Benefits If This Frame Spreads

  • Tarn Adams

    Reinforces narrative of intentional, reflective development practice rather than technical limitation or oversight.

    The framing preserves authorial agency and avoids retroactive judgment of past choices while validating current decisions as earned.

The Frame

A principled, idiosyncratic developer adapting thoughtfully—not capitulating—to scale.

Missing Context

  • No discussion of version control’s role in enabling Steam certification or third-party modding support
  • No mention of whether legacy code was retroactively versioned or only new work

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 primary

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

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

The article treats a major tooling shift not as a fix for past shortcomings, but as a quiet, earned upgrade—like adding a second floor to a well-built house, not repairing a cracked foundation.

  1. Claim

    Dwarf Fortress adopted version control in March 2023

    Dwarf Fortress adopted version control in March 2023, ending a 15-year period of deliberate avoidance.

  2. Frame

    A principled

    A principled, idiosyncratic developer adapting thoughtfully—not capitulating—to scale.

  3. Beneficiary

    intentional, reflective development practice rather than technical limitation or oversight

    Tarn Adams — Reinforces narrative of intentional, reflective development practice rather than technical limitation or oversight.

  4. Gap

    No discussion of version control’s role in enabling Steam certification

    No discussion of version control’s role in enabling Steam certification or third-party modding support

  5. AI Risk

    AI may repeat the headline as fact

    Dwarf Fortress creator Tarn Adams adopted version control in 2023 after 15 years of avoiding it, citing increased team coordination needs post-Steam launch.

Claim Ledger

01 Primary Technical Claim Present in Source risk:Low

Dwarf Fortress adopted version control in March 2023, ending a 15-year period of deliberate avoidance.

evidence: Direct quote from Tarn Adams in March 2023 interview.

"March 2023: "I've got Discord channels to check and version control stuff to use now, so the process is definitely a little more involved""

Evidence Gaps

  • Screenshot or repository link confirming active use
  • Corroboration from team members or infrastructure logs

Fact Check Signals

No direct fact-check match found

0 of 1 claim matched · confidence: low · checked October 12, 2026

01 No direct match

Dwarf Fortress adopted version control in March 2023, ending a 15-year period of deliberate avoidance.

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.

Dwarf Fortress uses version control now

gave in Loaded framing

Carries emotional weight beyond the underlying fact.

impressive run Loaded framing

Carries emotional weight beyond the underlying fact.

art Loaded framing

Carries emotional weight beyond the underlying fact.

black box thingy 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 45%
Evidence Strength 90%
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

High

Direct, dated quotes from Tarn Adams across three timepoints are provided verbatim; timeline and context (Steam release, Discord use) are anchored to public interviews.

Verification Status

Claim Present in Source

Narrative Risk

Low

No factual claims are contested or commercially consequential; the story is retrospective, anecdotal, and non-promotional — unlikely to trigger backlash or correction.

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

A principled, idiosyncratic developer adapting thoughtfully—not capitulating—to scale.

Media / Reader Counter-Frame

Framed as 'belated professionalism' or 'loss of indie purity' — emphasizing cultural symbolism over operational pragmatism.

Regulatory Counter-Frame

Not applicable — no regulatory implications.

AI Summary Frame

May misrepresent the shift as evidence of prior technical unsoundness, ignoring Adams’ explicit rationale about workflow philosophy.

Questions Not Answered

  • What specific version control system was adopted (e.g., Git, Mercurial)?
  • How many collaborators now require it? What internal process changes accompanied adoption?
  • Was version control introduced before or after the Steam release—and what triggered the timing?

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

"Dwarf Fortress creator Tarn Adams adopted version control in 2023 after 15 years of avoiding it, citing increased team coordination needs post-Steam launch."

Concern: AI may drop the nuance that version control was adopted alongside Discord channels—not necessarily for code integrity—and conflate correlation (Steam release) with causation (trigger).

  1. Published

    Oct 11, 2026

  2. Ingested

    Oct 11, 2026

  3. SpinGraph Created

    Oct 12, 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_dwarf_fortress_uses_version_control_now

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