CONCEPT
The Law of Leaky Abstractions
Spolsky's 2002 thesis that all non-trivial abstractions, to some degree, are leaky — the structural observation that every layer designed to hide complexity will eventually fail to hide it, forcing the user to understand the very thing the abstraction promised to conceal.
Formulated by Joel Spolsky in a November 2002 blog post, the Law of Leaky Abstractions names a structural feature of abstraction itself: concealment is not elimination, and complexity that is hidden is not complexity that has been resolved. Every layer of technology designed to hide lower-level mechanics from its users will, at unpredictable moments, fail to hide them. When the failure occurs, the user must understand the very layer the abstraction was supposed to make irrelevant. The law is not a complaint about bad abstractions — it applies equally to brilliant ones — because the issue is not quality but architecture. It has held across sixty years of computing history without being falsified, and in the age of AI-generated code it describes the most consequential abstraction failure modes ever faced.
In The You On AI Field Guide
The law emerged from Spolsky's years inside the specific