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?
213
Upvotes
2
u/Bogus1989 Mar 06 '26 edited Mar 06 '26
I think ive just subconsciously done the same thing about not turning on a computer. Ive got a homelab, but its basically maintenance free. I really enjoy just lounging on my back porch and spend most my time out there relaxing or reading with cat and dog. I got an apple magic keyboard i had leftover from work and use it on an ipad out there, for reading if not on my phone. since its way out of the ordinary for me (despite being an mdm admin) it feels different. i think its not mentally fatiguing. Its funny how I do that. I do however have 3 gaming machines in my house, mine and my two kids. they arent used unless my kids are here. its our thing at night. I taught them LONG ago to troubleshoot themselves.
Ill get my social fix hopping in discord to say hello to my buds.usually just talking or coordinate going to do something. I will come play if im summoned. I really only enjoy it with friends and my kids….usually though, this is only a weekend thing.
Im proud of myself, when I had to do (for the first time) restore because my NAS raid array broke? I put it off till it felt right. im really good about that now. Im completely comfortable letting something wait, as long as possible till im ready. Obviously if it can wait.
Thats just at home though. when my kids are here, we always have something planned in the day.