Explore the stack / Systems
Systems administration
Linux, services, and the habits that turn a noisy incident into a clear next step.
Field notes
02 ARTICLES
Systems admin/01
The first 15 minutes of a Linux incident
A calm, repeatable approach to finding the signal: establish impact, inspect the host, and follow the evidence.
Systems admin/02
A 404 is a clue. Test before you restart.
Reproduce a missing-file failure, compare it with a working health route, and recover without restarting the service.
Our current focus is Linux troubleshooting and reliable deployments. All four topic collections remain open as the journal grows.