NOTE

Hanlon's razor

#software-engineering (40)#culture (4)

Incidents and brittle threads reward a specific failure mode. You invent an antagonist.

Never attribute to malice that which is adequately explained by stupidity.

That line travels under the name Hanlon’s razor. I treat it as a way to order explanations before I lock in a story about intent, not as proof that nobody meant harm.

The genealogy is messier than a single epigram suggests. People have said versions of this for centuries (misread signals, tired operators, confused policy). The tight modern wording is what got a name. Quote Investigator’s “Not Malice” thread walks the paper trail, pushes back on bogus Napoleonic attribution, and points to Murphy’s Law Book Two (1980), edited by Arthur Bloch, as an early printed instance credited to Robert J. Hanlon. Britannica’s Hanlon’s razor entry tells the same core story in encyclopedia voice. I did not pull the primary source myself, so treat that 1980 line as the best documented origin I know about, not scripture.

A blameless review is not a ban on naming mistakes. It is a refusal to substitute moral theater for mechanics. Hanlon’s razor nudges you toward the boring causes first (fatigue, unclear runbooks, missing guardrails, a deploy train nobody owns, a bad default). That is where fixes live. If you skip that pass and jump straight to “who wanted this broken,” you optimize for courtroom energy and underlearn the system.

Most friction I have seen came from overload, ambiguity, or mismatched assumptions, not from a secret campaign against my roadmap. Defaulting to a generous read of intent keeps me faster and less miserable. The razor still has edges. Malice exists. So does a pattern of carelessness that stops being excusable after the third outage. A heuristic is not a cover for harassment, discrimination, or someone who will not do their job. Use it to slow your reflex to personalize pain, then follow the evidence where it goes.

If you only take one habit from the aphorism, pause before you write the sharp Slack message and ask whether the scene still makes sense if the villain is replaced by confusion, a bad handoff, or a metric that rewarded the wrong behavior. Often it does. When it does not, be direct and act.