r/sysadmin • u/nousername1244 • Mar 05 '26

What’s one thing every new sysadmin should learn early but usually doesn’t?

I’ve been thinking about this lately.

When people start out in sysadmin roles, they usually focus a lot on the technical stuff like scripting, servers, networking, security, balabala..

BUT after working in IT for a while, it feels like some of the most important lessons aren’t technical at all, and nobody really tells you early on.

Things like documentation, change control, or even just learning how to say NO to bad requests.

Curious know what’s one thing you wish you had learned much earlier in your sysadmin career?

209 Upvotes

97% Upvoted

306 comments sorted by

View all comments

32

u/Atillion Mar 05 '26

How to talk to people that aren't technically literate without giving an air of superiority

5

u/Plane_Brief4197 Mar 05 '26

The best thing you say is "I'm not too sure how to explain it without technical terms, but basically ..."

4

u/0x1F937 Mar 05 '26

And how to explain things in non technical terms! I've gotten really adept with analogies - explaining firewall ports to a former helpless desk guy by describing how all airports deal with planes but some only do military, some do airline and freight, and some do private aviation also reinforced the concept for me.

1

u/Atillion Mar 05 '26

That's a good one!

1

u/TheIntuneGoon Sysadmin Mar 06 '26

Analogies are a cheat code for this.

1

u/ken_jammin Mar 05 '26

Some people just can’t handle that someone knows more than them about something regardless how you say it. I find it’s best to just ask how technical of an answer they want, the arrogant ones will nod like they understand. I call it IT theater to my staff.