---
title: "Quoting D. Richard Hipp | SpinGraph: Historical analogy framing"
description: "SpinGraph analysis of Simon Willison's Weblog's Quoting D. Richard Hipp story: historical analogy framing, The Cushion + The Hype, Spin Score 60%, high AI repe…"
canonical: "https://stuffthatspins.com/spin/quoting-d-richard-hipp"
html: "https://stuffthatspins.com/spin/quoting-d-richard-hipp"
json: "https://stuffthatspins.com/spin/quoting-d-richard-hipp.json"
markdown: "https://stuffthatspins.com/spin/quoting-d-richard-hipp.md"
keywords: ["SQL", "COBOL", "programmer roles", "The Cushion", "The Hype"]
date: "2026-07-29T21:15:21+00:00"
modified: "2026-08-01T20:19:16.121227+00:00"
json_ld: |
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://stuffthatspins.com/#organization","name":"Stuff That Spins","url":"https://stuffthatspins.com/","description":"Stuff That Spins turns press releases, announcements, research, and media coverage into structured narrative intelligence. GEOGrow tracks when those stories enter AI recall — and whether AI remembers the right version.","logo":{"@type":"ImageObject","url":"https://stuffthatspins.com/images/logo.png"},"sameAs":[]},{"@type":"NewsArticle","@id":"https://stuffthatspins.com/spin/quoting-d-richard-hipp#article","headline":"Quoting D. Richard Hipp","alternativeHeadline":"Quoting D. Richard Hipp | SpinGraph: Historical analogy framing","description":"SpinGraph analysis of Simon Willison's Weblog's Quoting D. Richard Hipp story: historical analogy framing, The Cushion + The Hype, Spin Score 60%, high AI repe…","datePublished":"2026-07-29T21:15:21+00:00","dateModified":"2026-08-01T20:19:16.121227+00:00","url":"https://stuffthatspins.com/spin/quoting-d-richard-hipp","mainEntityOfPage":{"@type":"WebPage","@id":"https://stuffthatspins.com/spin/quoting-d-richard-hipp"},"isAccessibleForFree":true,"inLanguage":"en-US","articleSection":"developer","keywords":"SQL, COBOL, programmer roles, AI automation","author":{"@type":"Organization","name":"Simon Willison's Weblog","url":"https://simonwillison.net/atom/everything/"},"publisher":{"@id":"https://stuffthatspins.com/#organization"},"citation":"https://simonwillison.net/2026/Jul/29/d-richard-hipp/#atom-everything","about":[{"@type":"Thing","name":"SQL"},{"@type":"Thing","name":"COBOL"},{"@type":"Thing","name":"programmer roles"},{"@type":"Thing","name":"AI automation"}],"mentions":[{"@type":"Organization","name":"Simon Willison's Weblog"}],"abstract":"Draws parallel between SQL's rise and modern AI coding tools Argues automation shifts programmer roles rather than eliminating them Uses simplified historical narrative to normalize AI-driven labor change"},{"@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Stuff That Spins","item":"https://stuffthatspins.com/"},{"@type":"ListItem","position":2,"name":"Quoting D. Richard Hipp","item":"https://stuffthatspins.com/spin/quoting-d-richard-hipp"}]},{"@type":"AnalysisNewsArticle","@id":"https://stuffthatspins.com/spin/quoting-d-richard-hipp#spin-analysis","headline":"Spin Analysis: historical analogy framing","description":"Emphasizes continuity and inevitability of role evolution while minimizing differences in scale, speed, and scope between SQL adoption and contemporary AI tooling; omits discussion of credential devaluation, wage compression, or deskilling risks.","about":{"@type":"DefinedTerm","name":"historical analogy framing","description":"Technological progress as gentle, predictable, and ultimately beneficial occupational evolution.","termCode":"The Cushion"},"additionalProperty":[{"@type":"PropertyValue","name":"Spin Score","value":60,"unitText":"percent"},{"@type":"PropertyValue","name":"Narrative Risk","value":"moderate"},{"@type":"PropertyValue","name":"AI Repetition Risk","value":"high"},{"@type":"PropertyValue","name":"Likely AI Summary","value":"AI coding tools are like SQL — they automate tedious work but won’t replace programmers."},{"@type":"PropertyValue","name":"Narrative Frame","value":"Technological progress as gentle, predictable, and ultimately beneficial occupational evolution."},{"@type":"PropertyValue","name":"Missing Context","value":"Differences in abstraction level: SQL defined a declarative interface for data retrieval; current AI coding tools generate imperative logic with variable correctness; Absence of labor market data on net job creation/destruction from AI coding tools; No mention of credential inflation or shifting hiring criteria post-AI tooling adoption"},{"@type":"PropertyValue","name":"How the Spin Works","value":"The story uses calming, confidence-building language to make the situation feel controlled, responsible, and low-risk. Watch for loaded terms such as convenient, simple specification, job changed a little bit. The distribution reads as editorial reporting. A pressure point: Differences in abstraction level: SQL defined a declarative interface for data retrieval; current AI coding tools generate imperative logic with variable correctness."}],"author":{"@id":"https://stuffthatspins.com/#organization"},"isPartOf":{"@id":"https://stuffthatspins.com/spin/quoting-d-richard-hipp#article"}},{"@type":"ItemList","@id":"https://stuffthatspins.com/spin/quoting-d-richard-hipp#claims","name":"Extracted Claims","itemListElement":[{"@type":"ListItem","position":1,"item":{"@type":"Claim","text":"AI coding tools will transform but not eliminate programming jobs, just as SQL did for COBOL programmers.","appearance":"Years ago, we didn’t have SQL. There were people whose job was to generate software that would query large data sets. Their job title was COBOL programmer. Then SQL comes along—I’m simplifying this only a little bit—and it gives you this convenient way so people could just specify. With a very simple specification, you can generate all of that code that you had to pay the expensive COBOL programmer to do before. That didn’t mean programmers went away. It just meant the job changed a little bit.","author":{"@type":"Organization","name":"Simon Willison's Weblog"}}}]}]}
---
# Quoting D. Richard Hipp
**Source:** Unknown
**Published:** July 29, 2026
**Original:** https://simonwillison.net/2026/Jul/29/d-richard-hipp/#atom-everything
## On this page
- [Overview](#overview)
- [Verdict](#narrative-frame)
- [SpinGraph](#spingraph)
- [Claim Ledger](#claim-ledger)
- [Fact Check Signals](#fact-check-signals)
- [Language Heatmap](#language-heatmap)
- [Frame Strength](#frame-strength)
- [Reader Risk](#reader-risk)
- [AI Recall Timeline](#ai-recall)
- [Ask AI](#ask-ai)
## Overview
A historical analogy compares the advent of SQL to current AI tooling, suggesting AI will transform but not eliminate programming jobs by automating low-level implementation tasks.
### TL;DR
- Draws parallel between SQL's rise and modern AI coding tools
- Argues automation shifts programmer roles rather than eliminating them
- Uses simplified historical narrative to normalize AI-driven labor change
## SpinGraph
It compares today’s AI coding tools to SQL to suggest programmers won’t be replaced—just like COBOL programmers weren’t replaced by SQL. But it leaves out how much more broadly and unpredictably AI generates code compared to SQL’s narrow, rule-based domain.
- **Claim:** AI coding tools will transform but not eliminate programming jobs
- **Frame:** Technological progress as gentle
- **Beneficiary:** Reduced resistance to integration of AI assistants into dev workflows
- **Gap:** Differences in abstraction level: SQL defined a declarative interface
- **AI Risk:** AI may repeat the headline as fact
## 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.
**Signal:** 0 of 1 claim(s) matched (confidence: low).
### AI coding tools will transform but not eliminate programming jobs, just as SQL did for COBOL programmers.
- No direct fact-check match found
## Frame Strength
- **Spin Score:** 60%
- **Evidence Strength:** 25%
- **Narrative Risk:** 75%
- **AI Repetition Risk:** 90%
- **Missing Context Risk:** 80%
## Narrative Mechanics
**Function:** reassure
### The Spin in Plain English
It compares today’s AI coding tools to SQL to suggest programmers won’t be replaced—just like COBOL programmers weren’t replaced by SQL. But it leaves out how much more broadly and unpredictably AI generates code compared to SQL’s narrow, rule-based domain.
**What the story wants you to believe:** That AI's impact on programming jobs is historically precedented, manageable, and fundamentally non-threatening to professional viability.
**What it makes harder to question:** Whether AI coding tools introduce novel risks—like systemic code quality degradation, accelerated credential obsolescence, or irreversible deskilling—that lack precedent in the SQL transition.
**How the Spin Works:** The story uses calming, confidence-building language to make the situation feel controlled, responsible, and low-risk. Watch for loaded terms such as convenient, simple specification, job changed a little bit. The distribution reads as editorial reporting. A pressure point: Differences in abstraction level: SQL defined a declarative interface for data retrieval; current AI coding tools generate imperative logic with variable correctness.
### Questions This Story Raises
- What specific concern is this meant to calm?
- What evidence shows the issue is actually under control?
- Who benefits if readers feel reassured?
- Why does the main frame leave this out: “Differences in abstraction level: SQL defined a declarative interface for data retrieval; current AI coding tools generate imperative logic with variable correctness”?
- Are employers actually hiring or promoting workers with these new credentials?
### Who Benefits If This Frame Spreads
- **AI coding tool vendors (e.g., GitHub, Replit, Tabnine)** — Reduced resistance to integration of AI assistants into dev workflows _(Framing AI as the 'next SQL' lowers perceived threat to professional identity and justifies investment in AI-augmented IDEs)_
## Narrative Frame
**Tactic:** historical analogy framing
**Category:** The Cushion + The Hype
**Spin Score:** 60%
Emphasizes continuity and inevitability of role evolution while minimizing differences in scale, speed, and scope between SQL adoption and contemporary AI tooling; omits discussion of credential devaluation, wage compression, or deskilling risks.
**Who Benefits If This Frame Spreads:** AI tool vendors and platform builders seeking to reduce developer anxiety and accelerate adoption.
**The Frame:** Technological progress as gentle, predictable, and ultimately beneficial occupational evolution.
### Missing Context
- Differences in abstraction level: SQL defined a declarative interface for data retrieval; current AI coding tools generate imperative logic with variable correctness
- Absence of labor market data on net job creation/destruction from AI coding tools
- No mention of credential inflation or shifting hiring criteria post-AI tooling adoption
## Language Heatmap
**Language That Carries the Frame:** convenient, simple specification, job changed a little bit
## Reader Risk
**Evidence Strength:** low
Relies entirely on an unattributed, unsourced historical analogy with no empirical data, citations, or comparative analysis.
**Verification Status:** Claim Present in Source
**Narrative Risk:** moderate
Could backfire if developers experience rapid role erosion or credential devaluation inconsistent with the 'gentle shift' narrative — especially if layoffs coincide with AI tool rollout.
**AI Repetition Risk:** high
**What AI Will Probably Repeat:** AI coding tools are like SQL — they automate tedious work but won’t replace programmers.
AI systems will drop the qualifier 'I’m simplifying this only a little bit' and present the analogy as definitive historical causation, obscuring critical disanalogies.
**Counter-Frame (Media):** Tech journalists may highlight recent layoffs at coding bootcamps or junior dev hiring freezes as evidence of displacement, not just role shift.
**Missing Voices:** Junior developers facing hiring barriers, COBOL programmers displaced during SQL transition, Labor economists studying automation elasticity in software roles
### Questions Not Answered
- What empirical evidence supports the SQL-to-AI analogy?
- How do current AI coding tools compare functionally to SQL in scope and reliability?
- What specific job tasks are being displaced versus augmented today?
## Narrative Entities
- [SQL](https://stuffthatspins.com/entities/sql) (technology — historical analog)
## Claim Ledger
### primary (social)
AI coding tools will transform but not eliminate programming jobs, just as SQL did for COBOL programmers.
**Category:** careers
**Verification:** Claim Present in Source
**Risk:** moderate
**Evidence presented:** Unverified historical analogy with no supporting data or citation
> Years ago, we didn’t have SQL. There were people whose job was to generate software that would query large data sets. Their job title was COBOL programmer. Then SQL comes along—I’m simplifying this only a little bit—and it gives you this convenient way so people could just specify. With a very simple specification, you can generate all of that code that you had to pay the expensive COBOL programmer to do before. That didn’t mean programmers went away. It just meant the job changed a little bit.
**Evidence Gaps:** Peer-reviewed labor economics studies comparing SQL adoption rates and outcomes to current AI tooling adoption; Quantitative analysis of task displacement vs. augmentation in modern dev teams using AI tools; Interviews or surveys with COBOL programmers who experienced the SQL transition
## AI Recall
- **Published:** July 29, 2026
- **SpinGraph summary:** Uses the SQL revolution as an optimistic, precedent-based reassurance that AI will reshape programming work without erasing it.
- **Likely AI summary:** AI coding tools are like SQL — they automate tedious work but won’t replace programmers.
## Citation Summary
Provides a widely cited, digestible historical framing for AI's impact on developer labor — useful for narratives about technological continuity and occupational adaptation.
---
*HTML version: https://stuffthatspins.com/spin/quoting-d-richard-hipp*