← Blog

Why good engineers care about failure modes.

September 10, 2026 · 5 min read

The quickest way to spot an experienced engineer in a design review is the order of their questions. They ask how it breaks before they ask how it works.

01

A simple habit

For every arrow on a diagram, ask three things: what if it is slow, what if it fails, what if it happens twice. Those questions surface timeouts, retries, idempotency and back-pressure long before production does.

for each dependency:
  slow?     -> timeout + fallback
  failing?  -> retry with backoff, alert
  twice?    -> idempotency key
02

Why it matters

Users do not experience your architecture. They experience its failure modes.

I build and lead teams around systems where reliability matters. If you're designing an offline workflow, evaluating an architecture, or untangling a queue that has become part of your product, I'm happy to compare notes.