Your Brain is Lazy — By Design
The human brain consumes roughly 20% of your body's energy while representing only 2% of its mass. To manage this expense, the brain relies on mental shortcuts called heuristics — fast, automatic rules of thumb that let you make decisions without analyzing every detail from scratch.
Most of the time, heuristics serve you well. "That shadow looks like a tiger — run!" kept your ancestors alive. "This code pattern looks like the one that caused an outage last month — investigate!" keeps your systems alive. The problem arises when these shortcuts fire in contexts where they don't apply. When a heuristic produces a systematic, predictable error in judgment, we call it a cognitive bias.
In engineering, cognitive biases don't just cause bad code. They cause bad architecture decisions, toxic incident reviews, zombie projects that refuse to die, and cargo-cult adoption of tools that don't fit your context. The insidious part: you cannot feel a bias happening. It doesn't announce itself. It feels like clear, rational thinking — which is exactly what makes it dangerous.
You cannot "patch" the human brain. But you can patch your processes — your code reviews, your post-mortems, your architecture decision records, your alerting policies — to create checkpoints where biases get caught before they cause damage. This lesson covers the biases most dangerous to engineering teams, with concrete strategies for defending against each one.
Key Point: Cognitive biases are not character flaws or signs of incompetence. They are features of human cognition that misfire in complex environments. The goal is never to eliminate them (you can't) but to build systems and team habits that compensate for them — the same way you build redundancy into infrastructure because you know individual components will fail.