Dive Into HTML5
Source: https://diveintohtml5.info/ ↗
A free technical book on HTML5 written by Mark Pilgrim, a programmer whose reputation rests as much on the quality of his prose as on his code.
Each chapter opens with historical context — the origins of the doctype, the politics of codec wars, the archaeology of character encoding — before explaining the technical specification, making it simultaneously a reference manual and a history of the web platform.
Pilgrim's earlier Dive Into Python followed the same method and became one of the most widely read programming books of the 2000s.
The HTML5 edition is notable for the author's subsequent disappearance from the internet in 2011, when he deleted all his online presence without explanation, turning the book into something of a time capsule of a particular moment in web culture.
Free online.
Central argument
Pilgrim argues that understanding the web platform requires understanding its archaeology — that HTML5 is not a clean specification handed down from a standards body but the outcome of historical accidents, political fights, and compromises accumulated over decades. Each technical decision he explains is grounded in its origin: why the doctype is a vestigial string with no real meaning, why video codec support fragmented along corporate interest lines, why character encoding remains a source of silent data corruption. The implicit thesis is that a specification only becomes legible when you know the pressures that shaped it.
Critique
The historical method that makes the book exceptional also dates it structurally: written at a moment when HTML5 was still contested and browser inconsistencies were the central engineering problem, much of the practical guidance targets a landscape that no longer exists. More fundamentally, Pilgrim writes as a programmer explaining a platform to other programmers, which means the political and economic dimensions he touches — codec wars, the WHATWG–W3C split — are treated as context rather than as the main story, leaving the deeper critique of how web standards are governed underdeveloped.
Why it matters for product
For a CPO, the book's core lesson is organisational rather than technical: platform constraints that feel arbitrary to a product team usually carry a historical reason, and engineering resistance to certain decisions is often the surface expression of that buried history. Understanding why a technical foundation is shaped the way it is — rather than accepting it as given — changes how a product leader frames trade-offs with engineering and how they evaluate the real cost of technical debt. Pilgrim also models something useful in leadership communication: he proves that rigorous technical material becomes persuasive when its human and institutional context is made visible.