Production Is the System's Point of Truth
Production Is the System’s Point of Truth
There’s a moment when engineers understand that Production isn’t “just another stage in the pipeline.”
It’s not a place you reach after developing, testing, and approving. It’s a state where every decision changes a live, breathing reality.
The Illusion: “It Passed Tests, So It’s Safe”
Before production there’s:
- Tests
- Simulations
- Staging environments
- And thorough QA
And all of these matter.
But they don’t simulate the thing itself.
In Production:
- Load isn’t constant
- Users aren’t predictable
- And timing is never perfect
What works in isolation can behave completely differently at scale.
Why Real Incidents Don’t Reproduce
Many of the most severe failures:
- Didn’t happen in a controlled environment
- Didn’t repeat themselves
- And can’t be fully reproduced
Not because we missed a test - but because the conditions that created them were born from a one-time combination of:
- Load
- Timing
- And interactions between components
Production is a dynamic system. Not a repeatable experiment.
The Difference Between “Working” and “Under Control”
A system can:
- Work
- Return answers
- And meet its SLA
and still be dangerous.
The critical difference isn’t: whether the system works - but: whether we understand what’s happening inside it.
In Production: control matters more than Correctness.
Observability Before Elegance
At this stage, questions like:
- “How elegant is this?”
- “How architecturally beautiful is this?”
get replaced by other questions:
- Will we know how to identify an anomaly?
- Will we know how to stop damage?
- Will we know how to explain what happened?
A system that can’t be investigated and understood - can’t be managed.
An Analogy
Think of a flight.
A simulator can be perfect. Ground tests can be rigorous.
But in the air - everything changes.
A pilot doesn’t ask: “is the system correct?” They ask: “do I know what’s happening right now, and what are my options if it changes?”
The Bottom Line
Production isn’t a place where you finish building. It’s the place where you start taking responsibility.
Stable systems don’t assume Production “will be fine.” They’re designed with the understanding: that there, everything is already moving.
Looking Ahead
In the next post we’ll examine why Latency is a product of human and organizational decisions, and why local optimization often makes the overall problem worse.
📚 More in this Series: When the System Is Already Running
- Part 2 Latency as an Organizational Problem, Not a Technical One
- Part 3 When Metrics Lie
- Part 4 Deploy Is a Dangerous Event
- Part 5 Gradual Rollout: Why "Gradually" Isn't Always Safe
- Part 6 Backward Compatibility as a Long-Term Commitment
- Part 7 When a System Reflects Organizational Structure
- Part 8 Incident Response Is Culture, Not Procedure
- Part 9 Good Enough Engineering
- Part 10 Over-Engineering and Under-Engineering: Two Sides of the Same Mistake
- Part 11 Mature Engineers Don't Seek Control