Skill Infrastructure (Ding)
Jeff Ding's concept — the education, training, and standardization systems that widen the pool of people able to work with a general-purpose technology; his claim that GPT diffusion (and the national/corporate power that follows) is won by building this broad base of "ordinary engineers," not by dominating invention via "heroic inventors" in the technology's leading sector.
Also known as: skill infrastructure, GPT skill infrastructure, ordinary engineers not heroic inventors, ordinary engineers, heroic inventors, diffusion theory (Ding), leading sector theory, LS theory
Part of: Technology Diffusion & Transformation Curves
How authors use it
Oldest first (extraction date when no publication date is known).
| Author | Their term | Their meaning |
|---|---|---|
| This Week in AI: Chips, Checks, and Changing Jobs Michelle Smith · 2026-07-03 | Skill infrastructure | Attributed to Tim O'Reilly: the organizational systems and incentives that let teams actually share what they learn about using a new technology, as distinct from simply having AI-skilled individuals — invoked here as the real determinant of whether either SAP's external-hiring or IKEA's internal-retraining strategy succeeds. |
| Ordinary Engineers, Not Heroic Inventors Tim O'Reilly · 2026-07-07 | Leading Sector (LS) theory | Ding's name for the conventional account of technological revolutions: new technologies create fast-growing industries (steel, railroads, automobiles, semiconductors), and whichever country/company dominates invention in that industry captures the monopoly profits and economic linkages — 'if you win the leading sector, you win the era.' |
| Ordinary Engineers, Not Heroic Inventors Tim O'Reilly · 2026-07-07 | Skill infrastructure | Ding's term for the education and training systems that widen the pool of people who can actually work with a GPT — the institutions that build engineering skill at scale, standardize good practice, and tie research to industry. O'Reilly extends it to a firm-level analogue: the internal apparatus for spreading skill and compounding what employees learn. |
Documents (4)
- How Organizations Use AI: Evidence From ChatGPT Aaron Chatterji, David Holtz, Neel Rakholia, Prasanna Tambe, Gawesha Weeratunga · 2026-08-11 Reader 🖥️
Enterprise ChatGPT adoption and use, measured through OpenAI's own product telemetry across 1,500+ organizations and 17M+ messages, is a broad but highly uneven organizational phenomenon — concentrated among larger, more valuable, more intangible-capital-intensive firms, and diffusing unevenly across job functions, seniority levels and tasks within adopting firms — showing that organizations are still in an early, open-ended process of learning where generative AI belongs in their workflows rather than having already converted access into uniform deployment. - Ordinary Engineers, Not Heroic Inventors Tim O'Reilly · 2026-07-07 source ↗ Reader 🖥️
Technological and economic leadership — for nations and companies alike — is won not by inventing or dominating the 'leading sector' of a new technology but by diffusing a general-purpose technology like AI more broadly and patiently than rivals across ordinary, unglamorous work, a slow organizational (not technical) process that depends on skill infrastructure and on incentives that reward the 'ordinary engineers' who actually do the diffusing. - This Week in AI: Chips, Checks, and Changing Jobs Michelle Smith · 2026-07-03 Reader 🖥️
This week's AI news shows the same shift across three unrelated domains at once — hardware, government policy, and job design — from ad hoc/experimental arrangements to permanent structural conditions that organizations and individuals now have to build around rather than wait to resolve: physical infrastructure (not model algorithms) becomes the next competitive lever, government access to frontier models becomes a standing, revocable condition rather than a settled right, and job titles give way to function-based archetypes that no longer map onto 'engineer' or 'designer.' - The End of Programming as We Know It Tim O'Reilly · 2025-02-04 source ↗ Reader 🖥️
AI will not end programming or cause mass programmer unemployment; it is the latest in a long series of abstraction shifts that each redefined what 'programming' means and historically increased, not decreased, the number of programmers and the scope of what gets built — provided organizations and individuals invest in the 'learning by doing' needed to convert raw AI capability into deployed productivity.
Propositions touching this concept (5)
By publication month, oldest first (extraction month when no publication date is known).
2026-07
- explicitToday's AI industry and the national strategy forming around it operate on the (implicit) assumption of Leading Sector theory: whoever has the biggest and best model wins, and everyone else is an also-ran.
- explicitestablishedGPT diffusion depends on 'skill infrastructure' — education and training systems that widen the pool of people who can work with the technology.
- explicit"It is ordinary engineers, not heroic inventors, who matter" when the priority is widespread GPT adoption rather than invention.
- explicitThe rapid pace of frontier-model improvement makes organizational skill infrastructure more valuable, not less, because it is the only asset that survives each model generation.
- explicitCompanies pursuing an AI-native transition are choosing opposite paths at the same moment — SAP is cutting costs (hiring, travel) to fund external AI-talent hiring, while IKEA is retraining its existing workforce for AI-enabled roles — and the piece, via Tim O'Reilly, frames success as depending not on which path is chosen but on whether the organization deliberately builds a 'skill infrastructure' that rewards knowledge sharing as teams work out what the technology is good for in their specific context.
Open gaps (2)
- incompleteThe article's central analogy (AI's labor effects will resemble the Industrial Revolution's multi-decade diffusion lag) never addresses whether today's much faster information diffusion, platform distribution, and AI self-improvement could compress that lag dramatically — which would matter enormously for near-term organizational and team planning even if the long-run 'more programmers, not fewer' conclusion holds. For a team/org planning horizon of 2-5 years, 'eventually it works out' is compatible with a very disruptive intervening period that the article doesn't characterize.The End of Programming as We Know It — read next: Matt Beane's warnings (quoted elsewhere in this corpus) about the rate of change over the 'next year and a half' exceeding the prior two years would be a useful counterweight on timing, even if not on the long-run outcome.
- incompleteThe piece doesn't explain why SAP and IKEA chose opposite AI-transition strategies (external hiring vs. internal retraining) — no org-size, workforce-composition, financial-health, or existing-skill-base variable is offered, so the two examples read as anecdotes rather than a typology with predictive value for other organizations.This Week in AI: Chips, Checks, and Changing Jobs — read next: Look for comparative organizational-change research on build-vs-buy AI talent strategies that controls for firm size, financial pressure, and existing workforce skill distribution.