The 3 Pillars of a Better System Administrator
Being a better sysadmin isn’t mainly about learning more tools — it’s about building habits that make you consistent under pressure.
[ OK ] Mounted /var/log/conscience — write access enabled
[ WARN ] work-life-balance.service failed to start — unit not found
[ OK ] Loaded existential-dread.conf — 14 clients, 1 soul, infinite tickets
# Diary of a SysAdmin— "the examined network is worth living"
# Diary of a SysAdmin — dispatches on infrastructure, entropy, clients, and the long silence between reboots.
role: "Senior Sysadmin @ undisclosed MSP"
experience: 12+ years // most of it on-call
clients: 14 // each a universe of suffering
open_tickets: ∞
philosophy: "all systems tend toward chaos. tend back."
Being a better sysadmin isn’t mainly about learning more tools — it’s about building habits that make you consistent under pressure.
A day in the life of an MSP tech is way more than reading tickets and closing them out. The ticket is often a symptom — not the diagnosis.
Hardware planning now requires more flexibility than it used to. Sometimes it’s the simple stuff — like RAM and hard drives — that ends up changing the whole game.
Sometimes the win isn’t a successful install. Sometimes the win is saving a client from spending money on a solution that sounds good on paper — but doesn’t hold up in the real world.
A walkthrough of configuring a Conditional Access Policy in Microsoft Entra to require compliant devices when accessing sensitive data via Authentication Context.
New entries when the queue permits. No tracking. No noise. Just dispatches from the machine room.