The Cost of Clever
There’s a particular kind of code that makes its author feel smart and everyone else feel lost. You know it when you see it: a one-liner that does in twelve characters what ten lines would do legibly, a chain of transformations with no variable names to anchor you, a design pattern applied not because it fits but because the author wanted to use it.
Clever code is optimized for the wrong audience. The author imagines a reader who will be impressed. The actual readers — including future-you — need to understand what’s happening under time pressure, possibly at 11pm before a deploy.
This isn’t an argument against sophistication. Some problems are genuinely complex, and their solutions should reflect that. But there’s a version of complexity that exists to signal effort rather than solve a problem, and it has a real cost: every hour spent deciphering unnecessarily tricky code is an hour not spent on something useful.
The discipline is writing for the next person, not the last version of yourself who was proud of a particular trick.