Elements of Code

2026-05-14 · page · source summary

John Mark Wilkinson's book offering rules for writing software that future readers will understand. The core thesis: comprehensibility is the practical virtue that matters most, because perfect software is impossible and the real goal is being wrong in correctable ways.


Key Quotes

"Writing comprehensible code is what allows us to be wrong in correctable ways."

Key Themes

#simplicity #cognitive-debt

The title echoes Strunk & White's Elements of Style -- a compact set of rules that, if followed, produce clearer results than any amount of general advice. The framing is pragmatic rather than aspirational: you will be wrong, requirements will change, contexts will evolve. The question is whether the next person can understand your code well enough to fix it.

This philosophy directly supports Simplicity in the Age of AI-Assisted -- if LLMs reproduce complexity faithfully, then comprehensible code is the foundation that makes AI-assisted development work rather than amplifying mess. And it's the antidote to the Nobody Knows How Large Software Projects Work problem: if individual components are comprehensible, the system may still be unknowable in aggregate, but at least each piece can be understood in isolation.

Available free online or as PDF, which removes the usual barrier to adoption.

Critical Analysis

The ambition is right -- software needs its Strunk & White. Whether this book delivers on that promise is hard to judge from the landing page alone. The central aphorism ("wrong in correctable ways") is excellent and worth adopting regardless. The risk with any prescriptive code style guide is that the rules become cargo cult without the understanding. But the framing around correctability rather than correctness is unusually mature.


Sources: Elements of Code Last updated: 2026-05-14