Jef Raskin’s essay “Holes in the Histories” is most often read for its narrowest claim: that the standard account of the Macintosh’s creation understates his role and overstates others’. That reading is accurate as far as it goes, and the archived essay itself makes the case in Raskin’s own words. But to read the piece only as a credit dispute is to miss the more durable argument inside it — an argument not about who deserves the byline on the Macintosh, but about how computing as a field remembers its own past, and why it remembers it so badly.

This editorial framing takes up that larger argument. The interesting question is not whether Raskin was wronged. It is what his essay says about the mechanism by which technical history goes wrong, and whether that mechanism is still operating.

The Pattern, Not the Grievance

Raskin’s essay identifies a recurring pattern in how the history of a technology gets written. The person who originates an idea and the person who makes it commercially successful are usually different people, and the second person is almost always the one history remembers. The conceptual work — the years of thinking, the problem definition, the framework that makes a project possible — happens before there is anything visible to point at. The commercial triumph happens in public, at a moment, with a face attached. Memory attaches to the moment and the face.

This is the heart of the essay, and it generalizes far beyond the Macintosh. Raskin was describing a property of how human institutions record technical achievement: they compress the long, diffuse, unglamorous work of conceptual development into a single dramatic event, and they assign that event to whoever was most visible when it occurred. The framing wrote out not only Raskin but a whole category of contributor — the person whose work is foundational precisely because it precedes the thing everyone later points to.

Why the Distinction Matters

It would be easy to treat this as an academic point, or as a sophisticated way of relitigating a grievance. Raskin’s essay argues, persuasively, that it is neither — that inaccurate history has practical consequences for the field.

If the remembered story of innovation is “a visionary individual has an idea and drives it to completion,” then that is the model aspiring designers and engineers internalize, and it is wrong in a way that distorts how they understand their own work. The accurate story — a researcher identifies a problem, spends years building a conceptual framework, a project is built on that framework and then transformed by commercial forces and other hands — contains different and more useful lessons. It teaches that conceptual work matters even when it is invisible, that the foundational contributor and the commercial finisher are both real and distinct, and that the absence of a dramatic moment does not mean the absence of essential work.

History that erases the conceptual phase teaches the opposite. It teaches that the work that counts is the work that is visible at the moment of triumph, which is exactly the work that gets done last.

How Computing Forgets

The essay’s title is apt: histories have holes, and the holes are not random. They are located predictably, in the period before a technology became famous and in the contributions that cannot be reduced to a single visible act.

By 2018 there are good resources working against this kind of forgetting. Andy Hertzfeld’s folklore.org, assembled by a member of the original Macintosh team, preserves a granular, firsthand record of how the machine was actually built, including the parts that the popular story compresses away. The Computer History Museum has gathered oral histories from many of the people whose work the standard narratives flatten. These archives exist precisely because the default tendency is to forget, and someone has to do the deliberate work of remembering.

Raskin’s essay is itself an instance of that deliberate work. He is not, in the piece, primarily asking for personal credit — though the frustration is plainly there. He is doing what he elsewhere called historical housekeeping: restoring detail to a record that has been smoothed into legend. The distinction between restoration and revisionism is one he was careful to maintain. Revisionism replaces one story with another to serve a present interest. Restoration puts back what was documented and then removed. The essay claims to be doing the second, and on the evidence it largely is.

The Argument’s Afterlife

Whether the specific Macintosh record has been corrected in the years since is a mixed picture. More careful histories now acknowledge Raskin’s role in originating the project, and the firsthand archives make the conceptual phase recoverable for anyone who looks. But the popular story — the one that circulates without footnotes — still compresses and still misattributes, because the forces Raskin identified have not gone away. The drama of the visible moment still attracts memory more reliably than the substance of the invisible work.

That is the essay’s most uncomfortable implication. The mechanism it describes is not a one-time error in the Macintosh record that has now been fixed. It is a standing tendency in how technical history is written, and it is operating right now, on the technologies being built today. The conceptual work being done at this moment, by people not yet visible, will be compressed and reassigned by the same mechanism unless someone does the deliberate work of recording it accurately.

Read as a credit dispute, “Holes in the Histories” is a single man’s account of a single project. Read as it asks to be read, it is a warning about a habit of forgetting that the field has not broken. Raskin wanted accurate history not for his own sake but because he believed inaccurate history is a kind of intellectual pollution — it makes the past harder to learn from. On that point the essay has aged into something closer to a general principle than a personal complaint.

Documented Sources

• Jef Raskin, “Holes in the Histories” — the archived essay this piece discusses
• Andy Hertzfeld’s firsthand Macintosh recollections at folklore.org
• Computer History Museum oral histories — primary-source recordings of Mac-era contributors
• Jef Raskin, Wikipedia

Part of the Jef Raskin Reference, providing editorial commentary on the published works of the creator of the Macintosh project at Apple.