After the incident: change what the next retry does
A report can be finished even when its caller sees a timeout. Follow one lost reply from duplicate work to a repair another engineer can test.
Articles
Guides, news and explanations about AI and reliable systems.
Not sure where to begin? Choose a short reading path, or browse at your own pace.
What to tell customers while the answer is changing
At 14:15, one region has delayed reports. Eight minutes later, you know about another. Keep people informed without promising a fix you cannot yet see.
Hand over the incident, not another mystery
The incoming lead needs the next decision, the controls still active and the changes that never ran. Follow one fictional handoff from Maya to Rowan.
Investigate the incident without undoing each other’s work
One responder needs the worker’s connections. Another wants to restart it. Give their investigations a common question and make the next change visible.
The new approval route is written. Can someone use it?
Replay the moment the approver went missing, then watch what the revised procedure lets a responder do and where it still leaves them waiting.
Review the incident without giving responders tomorrow’s knowledge
A deployment looked suspicious until older-version jobs told a different story. Explain decisions using the clues and authority available when people made them.
The incident looks different from each screen
A missing report, a falling chart and a recent release seem to tell one story. Put their times and sources together before deciding which story it is.
One report arrived. Is the incident over?
New exports can succeed while older customers are still waiting. Check the download path, the backlog and returning demand before deciding what recovery means.
Repair the Linux lab when the server answers with the wrong thing
A running server can return HTTP 200 without returning your page. Introduce one reversible fault, follow the response and repair the request that failed.
Linux files: change a page and keep a way back
Make a small page, add a line and restore the original. Then follow a symbolic link to see why a path and a backup are different things.
Linux networking: find how far the request got
A missing page can begin with a name, a listener or the HTTP request itself. Separate those steps inside your private Linux lab.
Installed is not running: serve your first Linux page
Install the tools, start a server and request one practice page. Then move its port to discover which settings the running program really uses.