John Carmack's AI Position: The Kung-Fu Master Who Won't Retire (1990–2026)

Case study run on 2026-09-21 against templates/research/pre-llm-elite-programmer-ai-adaptation.md, as the third cohort case after the DHH study and the Torvalds study. It rests on a same-day evidence dossier (content/dev-tools/john-carmack-ai-adaptation-dossier-2026-09-21.md); every source below was re-fetched live during this session, with the fetch mechanics disclosed in Sources. The evidence layers are uneven and this matters: baseline facts come from Wikipedia and 80.lv; his X posts are quotable only through fetched secondary sources (Simon Willison’s quote log, The Decoder, D Magazine, PC Gamer, an Ars Technica mirror, braindetox.kr, GeekNews, and HN mirrors) — x.com itself would not fetch and the xcancel mirror returned HTTP 451 “suspended” — while Keen’s own research pages (keenagi.com) are official primary material. The structural finding of this case is negative and is reported as a finding, not hidden: no fetched source documents Carmack’s personal LLM/agent coding workflow. Everything below that lacks evidence is labeled “no public evidence found,” exactly as the template instructs; nothing was manufactured to fill the form.

Why this case (template Section 2 screen)

Carmack passes the template’s inclusion criteria on fame, technical reputation, and post-2023 evidence — with one criterion that must be reported honestly:

• Publicly recognized before 2023 for technical work: he “co-founded the video game company id Software and was the lead programmer of its 1990s games Commander Keen, Wolfenstein 3D, Doom, Quake, and their sequels” (Wikipedia).
• Reputation grounded in programming ability, not CEO or venture status: the same source credits him with pioneering or popularizing adaptive tile refresh, ray casting, binary space partitioning (“which Doom became the first game to use”), surface caching, Carmack’s Reverse, and MegaTexture — an engine-level technique list, not a management biography.
• Post-2023 public evidence is abundant for commentary: dated statements in 2023, 2025, and 2026 (timeline below), plus a published research program.
• He actually encountered AI coding tools in the abstract — GPT-3 writing code is what produced his first recorded reaction, in 2020.
• The honest caveat: template criterion 3 asks for “enough public evidence” of what happened after 2023, and the template’s core question is behavioral. For Carmack that evidence exists in plenty for his positions, and in effective zero for his practice. This case therefore passes the screen on commentary and fails it on practice evidence — and is written anyway, as the template’s Section 12 spectrum is explicitly designed to include low-adoption and minimally-documented members. The exclusion rule (“famous programmer → works on AI” is not adaptation evidence) is honored strictly here: he runs an AGI startup, and that fact alone would not make him a case. What makes him a case is the combination — six years of dated AI statements against a total absence of documented personal-workflow change.

Pre-2023 baseline (template Section 3)

Facts, from Wikipedia, the Lex Fridman episode page, and 80.lv:

• Co-founded id Software; lead programmer of Commander Keen, Wolfenstein 3D, Doom, Quake and their sequels; the technique list above spans the 1990s (Wikipedia).
• Joined Oculus VR as CTO on August 7, 2013, resigned from id Software the same November; in 2019 he “reduced his role to Consulting CTO so he could allocate more time toward artificial general intelligence (AGI)”; in 2022 he “left Oculus to work on his AGI startup, Keen Technologies” (Wikipedia).
• The 2019 AGI declaration, in his own words as quoted by Simon Willison (2019-11-14): “I’m going to work on artificial general intelligence (AGI). I think it is possible, enormously valuable, and that I have a non-negligible chance of making a difference there, so by a Pascal’s Mugging sort of logic, I should be working on it.”
• Keen Technologies: $20M announced August 2022, led by former GitHub CEO Nat Friedman and Cue co-founder Daniel Gross, with Patrick Collison, Tobi Lütke, Sequoia Capital and Capital Factory participating; he was reported saying AGI is “likely less than a decade from entering the market,” and that he would keep roughly 20% of his time for Meta consulting (80.lv, 2022-08-31 — reported speech, labeled as such). His own framing of taking investors' money: “This is explicitly a focusing effort for me… knowing that other people’s money is on the line engenders a greater sense of discipline and determination” (as quoted by the same 80.lv article).
• His self-description on the Lex Fridman podcast (#309, posted August 4, 2022): “legendary programmer, co-founder of id Software, and lead programmer of many revolutionary video games including Wolfenstein 3D, Doom, Quake, and the Commander Keen series.” The episode outline dedicates segments to “Modern programming” (40:53) and “Day in the life” (50:55) — the transcript was not fetched this session, so the outline is the only verified detail from it.

Classification per the template taxonomy: game programmer / graphics programmer / systems programmer (derivation from the Wikipedia technique list). Comparative advantage carried forward: engine-level performance craft — first-principles rendering systems, optimization, shipping entire 3D engines personally (interpretation from the sourced facts above). One self-deprecating workflow data point from before the LLM era, quoted by Willison: “Anyone that has me on too high of a pedestal should see me fumbling around with git” (2017 tweet, Willison, 2017-11-12).

The adoption timeline (template Section 4)

Phase 0 — 2022 and earlier (no modern LLM coding)

No fetched source documents his daily tools, unit of work, or review habits in this period; the Lex #309 outline’s “Modern programming” and “Day in the life” segments show the topics existed, not their contents. Two dated pre-2023 AI signals exist:

• July 2020 — on GPT-3’s code demos: “I used to say that AI research seemed to have an odd blind spot towards automation of programming work, and I suspected a subconscious self-preservation bias. The recent, almost accidental, discovery that GPT-3 can sort of write code does generate a slight shiver” [secondhand: tweet quoted verbatim by Lambda Labs, 2020-07-20].
• June 2021 — on architecture (YAGNI), quoted by Willison in 2026: “It is hard for less experienced developers to appreciate how rarely architecting for future requirements / applications turns out net-positive” (Willison’s quote log).

Phase 1 — 2023 (ChatGPT / GPT-4 era)

His first post-ChatGPT statement found in fetched sources is advice to someone else. On 2023-03-18 he published a direct message he had received from a young programmer worried AI would make their career obsolete, with his reply (The Decoder, 2023-03-19):

“Software is just a tool to help accomplish something for people — many programmers never understood that,”

with product skills — not tool skills — named as what will matter. The programmer “will probably be fine,” he said, “perhaps with handwritten code today and AI guidance later” (as reported by The Decoder). And: “You can still get work as a straight C programmer today, but it is different from 1990.”

Note the shape of this document: it is normative (what a young programmer should optimize for), dated, and says nothing about his own tools. The template’s key distinction — AI as assistant vs AI as programmer — is left entirely at the industry level. 2023-04 → 2025-02: no dated public statements found in fetched sources.

Phase 2 — 2024 (Copilot / Cursor / Claude / early agents)

No public evidence found in fetched sources. No 2024-dated statement, tool name, or usage report was located this session (the dossier’s search and this session’s fetches both drew blanks for this window).

Phase 3 — 2025 (agentic era; he comments on the field)

• 2025-03-18 — an X post on software development stepping on “land mines” unless artifacts are “a simple collection of human (and LLM!) readable text files”: surfaced in search-result snippets only; not found in fetched sources — carried here as a non-finding, not as a quote.

• 2025-04-07 — the WHAMM “power tools” defense. Microsoft had just shipped a playable demo of WHAMM (World and Human Action MaskGIT Model), “that generates each simulated frame of Quake II in real time using an AI world model instead of traditional game engine techniques” (Ars Technica, 2025-04-08, read via the ruberli.com mirror after Ars itself returned HTTP 405; the project page is at Microsoft Research). An X user had called the demo “disgusting,” claiming it “spits on the work of every developer everywhere” (as quoted by the same article). Carmack called the demo “impressive research work” and then posted the argument that became his most-quoted AI statement [secondhand, tweet 1909311174845329874, quoted by Simon Willison, 2025-04-07]:

  “My first games involved hand assembling machine code and turning graph paper characters into hex digits. Software progress has made that work as irrelevant as chariot wheel maintenance. […] AI tools will allow the best to reach even greater heights, while enabling smaller teams to accomplish more, and bring in some completely new creator demographics. […] Regardless, ‘don’t use power tools because they take people’s jobs’ is not a winning strategy.”

  An HN thread on the post reached 71 points/106 comments (HN Algolia, fetched 2026-09-21).

• 2025-05-21/22, Upper Bound 2025 (Edmonton) — the first large documented behavioral-adjacent move, and it is research, not tooling: Keen’s official page lists his talk with video, slides and notes PDFs, “an alternative path toward artificial general intelligence centered on reinforcement learning, online adaptation, and learning from streams of experience rather than static datasets. Topics include Physical Atari, continual learning, catastrophic forgetting, transfer learning, latency, embodiment, exploration, function approximation…” (keenagi.com/research). Attendee notes describe the session: the agent “has the same inputs and actionnable items as a human” — a camera watching the screen, a robot physically moving the joystick, with a live demo on-site — and his argument that simulated-Atari results “are hardly applicable to a real-world scenario,” plus catastrophic forgetting across games [secondhand attendee notes, Levesque]. The HN thread reached 557 points/360 comments (HN Algolia, fetched 2026-09-21; the companion dossier recorded a lower count at an earlier snapshot). A June 2025 “Research Directions” video exists — URL verified via HN story 44390959 (YouTube, 2025-06-26).

Phase 4 — 2025-11 → 2026 (the actual research target)

• 2025-11-19, D CEO interview (Venture Dallas 2025) — his most detailed recent self-description, and it is about research, not tooling: Keen “launched in 2022,” $20M raised, “no commercial roadmap, no consumer device, no monetization strategy”; “We’re trying to learn fundamental things about architecture and learning that nobody knows right now”; on the Physical Atari rig: “you point a camera at a TV screen, hook a little robot up to a joystick, and learn how to play the games”; and, on why: “I want to try to do science before I’m too old and I age out of it and lose the plasticity in my brain. I’ve always been this hotshot systems engineer, and that’s a super valuable skill set” [self-report via D Magazine, fetched through a reader proxy — see Sources]. The same interview records his AI-impact position: “AI is going to change the world in some pretty significant ways, although not as much or as quickly as people believe… Ten years from now, people will still be talking on Facebook.”
• 2026-07-09 — id Software layoffs [secondhand, quoted by PC Gamer, 2026-07-09, fetched via reader proxy]: “My ‘Microsoft will probably be a good steward of the brand’ statement isn’t aging well… and this is certainly going to dampen the mood of the founder reunion at QuakeCon next month,” and “To continue being produced long term, games need to succeed, not just be beloved.”
• 2026-09-11 — the “Kung Fu master” post [secondhand: tweet 2098443262214230095, quoted by braindetox.kr, 2026-09-14 and corroborated in summary form by GeekNews; HN thread 266 points/424 comments]. After reading Musashi’s Book of Five Rings, on martial arts sliding from battlefield craft (-jitsu) into discipline and hobby (-do): “The poignant undercurrent for me is that I can see many programming skills following that path”; “There are probably dozens of people reading this that remember hand assembling opcodes to hex and still have some magic numbers burned into their memory”; “even the small group of people still programming in assembly today (hey, @FFmpeg !) don’t work at that primitive level now”; “carefully writing code completely by hand is moving from a -jitsu to a -do. Code-do? Codo?”; “The retro computing scene is delightful, full of people building and exercising old skills for the love of it. But don’t be the out of touch Kung Fu master, heir to lifetimes of tradition, that gets mauled by an amateur MMA fighter”; “Musashi would probably have been pretty enthusiastic about assault rifles.” All of the above is his position on the field. None of it is a report of what he personally does with coding agents.

Where the progression lands: the template asks where the person sits on single-agent → long-running agent → parallel agents → agent orchestration → agent-generated software → agent-generated agents. For Carmack, no rung of that ladder can be placed from fetched sources. The crucial template observation — where they stop delegating — cannot be answered with evidence; what is documented is where he says the field should stop romanticizing (below).

The AI stack (template Section 6) — filled with non-findings, as required

This table is the case’s central negative result, and it is template-compliant to state it this way: the form says to write “no public evidence found” where evidence is missing. One adjacent documented stack exists, but it is not a coding-agent stack: Keen’s Physical Atari rig consists of “the Robotroller, which actuates the Atari CX40+ controller; the Atari Devbox, which runs the Arcade Learning Environment asynchronously; a camera; and a reinforcement learning agent” (keenagi.com/research). That rig is the closest thing to a publicly documented technical system he builds — and it deliberately does not contain an LLM. A June 2026 tweet on LLM-adapted “coding style” is known only from a search snippet: unverified, carried as a non-finding.

Unit of work (template Section 7)

The template’s cross-case question — what is the largest unit of work the programmer comfortably delegates? — has no public evidence found as its answer here. No fetched source describes him handing a function, a module, a feature, or a whole problem to an agent. There is no evidence of delegation change in either direction: no statement that he delegates, and no statement that he refuses to. The template’s pre-LLM ladder (function → class → module → feature → project → whole problem) cannot be advanced even one step from the fetched record. In a cohort where DHH documents whole-problem delegation and Torvalds documents a deliberate toy-layer-only boundary, Carmack’s cell is the empty one — and that emptiness is itself the data point this case contributes.

Bottleneck migration (template Section 8)

Unknown / not documented. The template’s before/after constraint table cannot be filled from evidence: no fetched source states what constrained his output before AI, or what constrains it now. What is documented is his commentary on other people’s bottlenecks — that “product skills” and understanding what software is for matter more than tool skills (2023 DM, via The Decoder), and that labor-saving tooling changes which jobs exist at which scale (the April 2025 farming-vs-social-media analogy, via Willison). Both are claims about the field, made by someone whose own constraint profile is not on the record. No bottleneck migration is asserted for him personally.

What he stopped doing / started doing (template Sections 9–10)

Stopped: no behavioral evidence found. No fetched source documents him giving up any concrete practice — not boilerplate, not debugging, not line review, not tool maintenance.

Started: no behavioral evidence found in the personal-workflow categories (prompting, specification, agent supervision, harness engineering, agent orchestration, evaluation, context engineering). What is documented instead is a research program and a discourse practice:

• Building an AGI research program on continual reinforcement learning — Physical Atari, streaming RL, plasticity (keenagi.com, 2025 talk, 2025 video, 2024–2025 publication lineage listed on the same page).
• Near-daily public discourse on AI and programming with unusually large reach (three verified HN threads in 18 months at 71, 557, and 266 points).
• “I am stepping a small toe back into aerospace systems” — Keen Systems tinkering, per the D Magazine interview.

The honest categorization: his documented new activities are Type E-adjacent research and public writing, not the template’s agent-era categories A–G. Whether he privately does any of A–G is exactly what the record does not say.

Identity after AI (template Section 11)

His own label, November 2025: “I’ve always been this hotshot systems engineer, and that’s a super valuable skill set” (D Magazine) — said while describing the aspiration to “try to be a scientist and to learn and formalize some aspect of learning and understanding that nobody knows about right now.” Mapped to the template’s types, the documented trajectory is Type E — researcher (“moved toward deeper technical problems”), with the important dating caveat that this move began in 2019, four years before LLM coding existed: the AGI turn predates the tools this template studies. Interpretation, labeled as such: his identity shift is real but is not AI-coding-induced; the AI-coding era left his declared identity unchanged while his subject matter had already moved to learning systems. Whether he is also a Type A (“AI makes me a much more productive programmer”) in private is no public evidence found.

Spectrum position (template Section 12) — the low-adoption branch

The template demands the whole spectrum: heavy adoption → moderate adoption → low adoption. This case is written as the low-adoption / low-evidence branch, and its precise shape matters:

• He validates AI as a strategy for others, in dated public statements: “AI tools will allow the best to reach even greater heights, while enabling smaller teams to accomplish more” (April 2025, via Willison); “‘don’t use power tools because they take people’s jobs’ is not a winning strategy” (same); product skills over tool skills for the next generation (March 2023, via The Decoder).
• His own research program deliberately builds outside the LLM paradigm: Keen’s stated direction is “learning from streams of experience rather than static datasets” (keenagi.com/research) — a formulation that positions realtime reinforcement learning against the static-dataset paradigm that produced the LLMs. That is a documented behavioral choice about AI, and it points away from the agent-coding world this template usually studies.
• The combination is the case’s punchline: the most famous programmer alive on the subject of AI tooling is also the cohort member with zero documented personal tooling. The template’s question — did their output change despite different AI adoption? — cannot be answered at the output level (no measured code output exists to compare), only at the discourse level: his output is arguments, and the arguments did not wait for a workflow.

Output leverage (template Section 13)

Since 2023, the evidenced output is research and discourse, not shipped software:

Any measured coding output since 2023: not found in fetched sources. The leverage question the template asks — did AI increase this person’s output frontier? — is unanswerable for him from public data, which is itself the finding.

AI leverage × pre-existing strength (2×2, template Section 14)

Carmack lands in the strong-programmer row, low documented adoption column: the “traditional master” cell — the same cell Torvalds occupies, reached by an opposite route. Torvalds documents a personal refusal at his layer of work while his institution adopts; Carmack documents neither personal use nor personal refusal, while producing a body of work adjacent to AI (an AGI research lab) that bypasses the paradigm entirely. The template’s working hypothesis — AI amplifies judgment more than raw coding ability — cannot be tested here: there is no output delta to attribute. The cell assignment is “documented” adoption; his actual behavior may be anything from heavy private use to none, and the public record does not distinguish.

“Taste-to-code ratio” (template Section 15) — not fillable, labeled

This qualitative construct requires personal data this case does not have: units of judgment and units of implementation, before and after. No personal data exists; the field is not applicable rather than zero — labeled as such rather than estimated. What can be noted, clearly separated from the construct: his September 2026 post supplies, as commentary about the field, exactly the concept the template gestures at — the abstraction ladder (hex → assembly → C → AI) and the “-jitsu to -do” migration of hand-coding from practical necessity to discipline. But that is his description of everyone else’s economics, not a measurement of his own ratio, and it is labeled self-report/commentary throughout this note.

The unchanged core (template Section 16)

What the record shows him refusing to change, with evidence:

1. The engine-craft identity. The self-label “hotshot systems engineer” (D Magazine, 2025) is continuous with the 1990s technique list (Wikipedia); the September 2026 post mourns hand-craft’s market decline while keeping the craft itself as “discipline and pleasure” — “The retro computing scene is delightful” (secondhand, braindetox.kr).
2. The researcher bet over the product bet. “I want to try to do science before I’m too old and I age out of it and lose the plasticity in my brain” (D Magazine) — the core move is toward understanding, and it was made in 2019, pre-LLM.
3. First principles over paradigms. Keen’s research direction — streams of experience rather than static datasets, Physical Atari, continual learning (keenagi.com) — is a stated position that the dominant paradigm (large static-dataset models, i.e. LLMs) is not the path he is betting on.
4. Product judgment stays human. “Software is just a tool to help accomplish something for people — many programmers never understood that” (2023 DM, via The Decoder).

Whether any private practice also survived unchanged is not observable; the core above is documented through statements and research choices, not through workflow.

Hypotheses H1–H4 against this case (template Section 19)

• H1 (great programmers become super-programmers) — Directional only, via his own claim. Evidence for: he asserts the amplification thesis himself — “AI tools will allow the best to reach even greater heights” (April 2025, via Willison). Against: zero output measurement; no personal code output is documented at all, so the prediction (“elite programmers increase output”) cannot be evaluated even directionally for him. Untestable in this case; carried as his endorsement, not as a result.
• H2 (programming moves upward) — Partial, as commentary. His abstraction-ladder framing (hex → assembly → C → AI; “-jitsu → -do”) matches the thesis that implementation drops in value while higher layers rise. Against: it is self-described as being about the field — “I can see many programming skills following that path” — not about his own working level. Matches the thesis rhetorically; no self-description to confirm.
• H3 (more specialized, not less) — Strongest fit in this case. He moved into a harder domain than product management would ever have been: continual reinforcement learning, realtime adaptation, embodied agents (Physical Atari), explicitly attacking problems the sim-only benchmark world ignored (keenagi.com/research; Levesque notes; D Magazine). The counter-evidence is timing: the move predates LLM coding, so AI may have validated the specialization rather than caused it — the case cannot separate the two.
• H4 (taste + orchestration is the scarce skill) — Weak. He never describes orchestrating agents; the September 2026 post’s wordplay (“don’t be the out of touch Kung Fu master”) is a warning against exactly the orchestration-era complacency of legacy skill, but he never claims the director-of-computation role for himself. His scarcity claim, where he makes one, is about product judgment, not orchestration. Not supported in this case; the case is the cohort’s counterweight to H4 enthusiasm.

Gaps and what would change this picture

• The X-archive problem is structural. His medium is X; x.com does not fetch; the xcancel mirror returned HTTP 451 “XCancel service is suspended” (fetched 2026-09-21, which attributes the suspension to “a new development in the ongoing legal proceedings”). Every Carmack X quote in this note rides on fetched secondary sources (Willison’s quote log, The Decoder, D Magazine, PC Gamer, an Ars mirror, braindetox.kr, GeekNews, HN mirrors) and is labeled secondhand. A permanent archive of his posts would upgrade every quote here.
• The UB25 slides and notes PDFs are published but were not parsed this session (PDF text not fetchable in this environment); they may contain the only first-person technical detail about how he builds systems today.
• No long-form 2024–2026 transcript about his own coding was found in fetched sources. The Lex #309 episode (2022) has “Modern programming” and “Day in the life” segments, but the transcript was not fetched; nothing post-2023 found addresses his personal tools.
• Non-findings carried verbatim from the dossier: no first-person account of his own LLM/agent coding workflow; no dated public statements found for 2023-04→2025-02; the 2025-03-18 “text files” tweet exists only in search-result snippets (not found in fetched sources); the June 2026 “coding style” tweet is snippet-only and unverified; the source video behind the widely shared April 2025 “future of dev work” clip (r/theprimeagen, 2025-04-07) was not found in fetched sources.
• Whether any Physical Atari/Keen code is public could not be confirmed; no public repo activity was located.
• This is one case; the template’s cross-case matrix becomes meaningful only with more cohort members.

Four cases, one spectrum (contrast coda, interpretation)

Run against the published siblings and the two same-week evidence dossiers, Carmack is the cohort’s spectrum endpoint:

(The antirez and Hejlsberg columns reflect their published case studies in this series: /dev-tools/antirez-ai-adaptation-2026-09-21/ and /dev-tools/anders-hejlsberg-ai-adaptation-2026-09-21/.)

DHH, Torvalds, antirez, and Hejlsberg all have the property the template is built to detect: dated, specific, first-person descriptions of a changed (or deliberately unchanged) workflow. Carmack — the most quoted programmer on AI in this cohort — is the endpoint where the record falls silent precisely where the template’s question lands. He is a famous skeptic-turned-pragmatist whose personal practice remains undocumented: the person who most loudly tells the field to pick up the power tools is the one member of the cohort whose own bench we cannot inspect.

Interpretation

This case suggests that — and this paragraph is our interpretation, not a sourced fact — the template’s spectrum has a fourth, uncomfortable region beyond “rejecter” and “adopter”: the undocumented. The Section 12 low branch was designed for people who visibly do less with AI; Carmack instead demonstrates that fame, frequency of AI commentary, and even founding an AI company produce no evidence at all about personal workflow. His documented behavioral choice in the AI era is real but points sideways: he did not change his coding practice in public view, and he built his research program — continual RL, streams of experience, a robot hand on an Atari joystick — in deliberate opposition to the static-dataset paradigm that produced the tools everyone else was adopting. Read together with his commentary arc (a “slight shiver” in 2020, power-tool advocacy by 2025, the Kung-Fu-master warning in 2026), the coherent picture is a man who treats AI as an industry force to be reasoned about publicly while keeping his own bench out of the record — either because it is unformed, private, or because he considers his personal workflow none of the public’s business. The honest conclusion is smaller than any of the exciting versions: six years of dated statements, zero dated workflow facts. For this template, that absence is the result — the guard against reading a famous person’s AI commentary as evidence of AI adaptation.

Sources

Fetched and read during the run on 2026-09-21 (re-fetching every URL the companion dossier used, plus two new sources verified this session):

Baseline / direct layers

• John Carmack (Wikipedia) — id cofounder, lead programmer of Commander Keen/Wolfenstein 3D/Doom/Quake, technique list, Oculus CTO 2013-08-07 → Consulting CTO 2019 → Keen 2022. Tertiary source, labeled as such.
• Lex Fridman Podcast #309 — episode page, posted 2022-08-04 — his self-description; “Modern programming” (40:53) and “Day in the life” (50:55) outline segments. Transcript not fetched this session.
• 80.lv — “John Carmack’s AGI Startup Keen Technologies Raises $20 Milllion,” 2022-08-31 — Keen funding, investors, the <10-year AGI estimate (reported speech), ~20% Meta consulting, the “focusing effort” quote.
• keenagi.com/research/ — Keen’s official research page: Physical Atari components (Robotroller, Atari Devbox, camera, RL agent), the Upper Bound 2025 talk with video/slides/notes links, and the “streams of experience rather than static datasets” research direction.

X posts — every quote rides on a fetched secondary source (x.com unfetchable; xcancel mirror returned HTTP 451 “XCancel service is suspended”, fetched 2026-09-21 to record the suspension):

• Lambda Labs — “GPT-3 A Hitchhiker’s Guide,” 2020-07-20 — verbatim July 2020 “slight shiver” tweet.
• The Decoder — “John Carmack offers advice to developers worried about losing jobs to AI,” 2023-03-19 — the 2023-03-18 DM (“product skills,” “handwritten code today and AI guidance later,” “straight C programmer… different from 1990”).
• Simon Willison — quote log, john-carmack tag — 2019 AGI Facebook post, 2017 git tweet, June 2021 YAGNI tweet.
• Simon Willison — “A quote from John Carmack,” 2025-04-07 — full April 7, 2025 power-tools quote block, tweet 1909311174845329874.
• Ars Technica — “Carmack defends AI tools after Quake fan calls Microsoft AI demo ‘disgusting’,” 2025-04-08 — live page returned HTTP 405 this session; read via the ruberli.com mirror (2025-04-08), which reproduces the article’s core paragraphs and links the original. Source of the WHAMM demo context and the “impressive research work” tweet. Disclosed as secondhand-through-mirror.
• Microsoft Research — “WHAMM! Real-time world modelling of interactive environments” — the WHAMM project page (fetched; title and URL verified this session — new source, added beyond the dossier).
• braindetox.kr — “John Carmack: ‘Don’t Be the Out of Touch Kung Fu Master’,” 2026-09-14 — verbatim quotes from the Sept 11, 2026 post (tweet 2098443262214230095).
• GeekNews — “현실과 동떨어진 쿵푸 고수가 되지 말라” summary — corroborating summary of the same post.

Interviews (proxy-disclosed):

• D Magazine — “Exclusive: John Carmack Predicts AI Won’t Change the World as Much as People Think,” 2025-11-19 — fetched through the r.jina.ai reader proxy because the direct page was not accessible this session; all quotes above are from that fetched copy. Interview edited for brevity and clarity, per the page’s note.
• PC Gamer — “John Carmack reacts to massive layoffs at id Software,” 2026-07-09 — fetched through the r.jina.ai reader proxy (direct fetch not attempted after the D Magazine proxy route was needed); the July 2026 X quotes are secondhand via this article.

HN Algolia (external measurement layer):

• HN story 43614546 — “John Carmack on AI in game programming,” 71 points/106 comments (Apr 2025); thread comments read via item 43614546.
• HN story 44070042 — “John Carmack talk at Upper Bound 2025,” 557 points/360 comments as fetched 2026-09-21 (the companion dossier recorded 143 at an earlier snapshot; the live count is used here).
• HN item 44390959 — verifies the June 2025 “Research Directions” YouTube URL (2025-06-26).
• HN story 49677577 — “Don’t be the out of touch Kung Fu master,” 266 points/424 comments (Sept 2026); thread read via item 49677577.

Companion documents in this repo:

• content/dev-tools/john-carmack-ai-adaptation-dossier-2026-09-21.md — the evidence dossier this case study is built on (not modified by this run).
• content/dev-tools/dhh-ai-adaptation-2026-09-21.md and content/dev-tools/linus-torvalds-ai-adaptation-2026-09-21.md — published sibling cases compared in the contrast coda.
• content/dev-tools/antirez-ai-adaptation-dossier-2026-09-21.md and content/dev-tools/anders-hejlsberg-ai-adaptation-dossier-2026-09-21.md — same-week evidence dossiers summarized (labeled) in the contrast coda.

Deliberately excluded from evidence: the 2025-03-18 “text files” tweet and the June 2026 “coding style” tweet (search snippets only — not found in fetched sources); the April 2025 viral-clip source video (not found in fetched sources); DuckDuckGo Lite result pages (discovery only, never cited for claims); anything quoted on a page not actually fetched.

Template: templates/research/pre-llm-elite-programmer-ai-adaptation.md in this repo. Every claim above is either a sourced fact with the link shown, a labeled secondhand/self-report item, or labeled derivation/interpretation. The negative results — the empty AI-stack table, the unfilled unit-of-work and bottleneck fields — are findings of this run, reported rather than papered over. Nothing in this note was recalled from model memory without a fetched source.