Citation: Wing, J. M. (2006). Computational thinking. Communications of the ACM, 49(3), 33–35.
URL: https://www.cs.cmu.edu/~15110-s13/Wing06-ct.pdf
Pulled by: Claude on 2026-04-29
PDF: wing-2006-computational-thinking.pdf in this folder.
What this is
The 3-page Communications of the ACM viewpoint that launched "computational thinking" as a curricular and policy concept. Wing's thesis: computational thinking is a fundamental skill — alongside reading, writing, arithmetic — that everyone, not just computer scientists, should learn.
Wing's definition (quotable)
"Computational thinking involves solving problems, designing systems, and understanding human behavior, by drawing on the concepts fundamental to computer science." (p. 33)
"Computational thinking is a fundamental skill for everyone, not just for computer scientists. To reading, writing, and arithmetic, we should add computational thinking to every child's analytical ability." (p. 33)
The mental tools Wing names
Across pp. 33–34 she enumerates the cognitive operations she counts as CT. The ones directly relevant to digital literacy (not programming) are:
- Abstraction and decomposition — "using abstraction and decomposition when attacking a large complex task or designing a large complex system. It is separation of concerns. It is choosing an appropriate representation for a problem or modeling the relevant aspects of a problem to make it tractable." (p. 33)
- Reformulating problems — "reformulating a seemingly difficult problem into one we know how to solve, perhaps by reduction, embedding, transformation, or simulation." (p. 33)
- Heuristic reasoning under uncertainty — "planning, learning, and scheduling in the presence of uncertainty." (p. 34)
- Trade-off thinking — "making trade-offs between time and space and between processing power and storage capacity." (p. 34) — generalizes to "trade-offs between effort and value" in our domain.
- Prevention / recovery thinking — "thinking in terms of prevention, protection, and recovery from worst-case scenarios through redundancy, damage containment, and error correction." (p. 34) — directly maps to "what to do when something goes wrong online" — a core digital-literacy task.
- Everyday-life examples she gives (p. 34): packing a backpack = prefetching/caching; retracing steps for lost mittens = backtracking; ski-rental decision = online algorithms; supermarket queue choice = performance modeling. These are the kind of examples our curriculum should mine.
What Wing says CT is not (load-bearing for our positioning)
"Conceptualizing, not programming. Computer science is not computer programming. Thinking like a computer scientist means more than being able to program a computer. It requires thinking at multiple levels of abstraction." (p. 35)
"Fundamental, not rote skill. A fundamental skill is something every human being must know to function in modern society. Rote means a mechanical routine." (p. 35)
"A way that humans, not computers, think. Computational thinking is a way humans solve problems; it is not trying to get humans to think like computers." (p. 35)
The fundamental-vs-rote distinction is exactly the position our pitch takes against tutorial-library competitors: we teach schemas, not click routines.
What Wing does not address
- Transfer. She asserts CT is a fundamental skill that transfers ("computational thinking will be a reality when it is so integral to human endeavors it disappears as an explicit philosophy") but provides no empirical evidence and acknowledges no transfer problem. The 20 years of subsequent CT-education research is largely a sustained engagement with that gap — and as Pea & Kurland (1984) had already shown for LOGO, transfer doesn't happen automatically.
- Adult learners. Wing's framing is K–college: "we should expose pre-college students to computational methods and models." Adult / workforce CT is not in scope.
- Mechanism. No theory of how CT is acquired, only a definition of what it is. This is one reason the subsequent literature spent two decades trying (and partly failing) to operationalize and measure transfer.
How we'll use this in the docs
- Pedagogy doc — opening section: cite Wing for the definition and the "fundamental, not rote" framing. Use it to set up the project's position: we agree CT is foundational, but we take seriously that the transfer problem Wing's manifesto did not address is the actual design constraint.
- Pitch — Thesis: the "schemas, not procedures" framing maps to Wing's "fundamental, not rote" — we can borrow her framing word-for-word.
- Spec — Curriculum levels: Wing's everyday examples (backpack/prefetch, mittens/backtrack) are templates for the kind of pattern-naming we want the AI co-pilot to do.
What's missing from this paper that we still need
Pea & Kurland (1984), Salomon & Perkins (1989), Schwartz & Bransford (1998), and the post-2010 CT-transfer evaluation literature (Lye & Koh; Fagerlund et al.; Scherer et al. meta-analyses). Wing without those is half the story.