Production Debugging

Working from symptom to cause under time pressure, starting from the highest-signal question there is: what changed?

A method for narrowing from symptom to cause under time pressure, using six questions in a fixed order rather than intuition.

Q · Production is broken, you have partial information and people are waiting — what do you actually do first?

Deployment-Centric Debugging

The highest-signal habit in the domain: when an incident begins, ask what recently changed before asking what is wrong.

Q · Why is "what did we ship?" a better first question than "what is broken?"

The Debugging Timeline

Deployments, config changes, alerts, error rate and latency drawn on one shared axis, so causal order is read rather than argued about.

Q · How do you see whether the change came before the symptom, instead of asking three people what they remember?

Change Correlation

Four categories of change — deploy, config, infrastructure, dependency — plus traffic, and the discipline of checking all of them rather than only code.

Q · When you ask "what changed?", what is the complete list of things that could have?

Production Anti-Patterns

The practices that reliably produce incidents — each with why it is tempting, because a list that only says "do not" teaches nothing.

Q · Which habits produce most production incidents, and why do sensible teams adopt them anyway?

CI/CD Anti-Patterns

Seven pipeline habits that quietly convert a feedback system into a bottleneck you cannot trust, and the pressure that produces each.

Q · What turns a delivery pipeline from a safety mechanism into a ritual people route around?