Let’s get something straight right away.
I’m your sysadmin.
We are not friends.
This is not hostility. It’s just clarity. In most jobs people expect warmth, camaraderie, the occasional lunch conversation about weekend plans. In systems administration, the relationship is a little different. My job is not to be socially available. My job is to make sure the systems keep running and nothing catches fire at three in the morning.
And over time, the job changes how you see people.
The Job Teaches You Suspicion
If you work long enough in infrastructure, you start to realize something uncomfortable.
Most problems in technology do not come from evil hackers sitting in dark rooms.
They come from someone clicking something.
Someone installing something.
Someone bypassing something.
Someone saying, “It should be fine.”
After a while, you develop a habit of questioning everything. Requests. Permissions. Software vendors. Random USB drives. “Quick fixes.” Urgent emails.
People think this makes sysadmins cynical.
It doesn’t.
It makes them experienced.
Loyalty Works Differently Here
Here is another uncomfortable truth about the job.
My loyalty is not to the users.
My loyalty is not to the vendors.
My loyalty is not even to the organization in the sentimental sense people like to talk about during leadership workshops.
My loyalty is to myself.
That sounds harsh until you understand what it means.
If a system fails, the blame lands on the sysadmin.
If data disappears, the sysadmin gets called.
If something breaks at midnight, the sysadmin is the one logging in.
So every decision becomes personal risk management.
Will this configuration break later?
Will this permission create a problem?
Will this shortcut come back and haunt me during an audit or outage?
The sysadmin learns quickly that nobody else carries the operational consequences.
So you protect yourself.
By protecting the systems.
The 2 AM Rule
Every sysadmin has an invisible rule that guides decisions.
Will this wake me up at 2 AM?
If the answer is yes, the answer to the request becomes very slow.
Very cautious.
Very detailed.
People sometimes mistake this for resistance or stubbornness.
It’s not.
It’s self-preservation.
Professional Distance
This is why sysadmins maintain distance.
Not because they dislike people.
Not because they enjoy saying no.
But because the job forces you to think about failure before convenience.
You become the person who asks annoying questions.
The person who refuses shortcuts.
The person who says, “Let’s do this the right way.”
That personality eventually bleeds into everything else in life.
You start double checking things.
You question intentions.
You think about worst-case scenarios automatically.
It becomes part of how you operate in the world.
The Quiet Arrangement
In the end, the relationship between users and sysadmins is simple.
You use the systems.
I keep them alive.
We do not need to be friends for that arrangement to work.
We just need the network to stay up, the servers to stay patched, and the backups to restore when everything inevitably goes sideways.
And if none of those disasters happen today, then the sysadmin did their job.
Quietly.
From a distance.
Exactly the way they prefer it.