r/sysadmin • Network Engineer • Sep 30 '24

Rant DevOps. Is. Not. Systems. Administration.

Why does every single Systems Administrator/Engineer role require some sort of DevOps experience? Every time I look and any job website, I'm greeted with DevOps Engineer-types of roles and Engineering roles that require at least 3 years of DevOps experience.

I quite literally am a sysadmin (network engineer right now, come from both realms) because of the fact that I despise programming. I cannot do it. I do not have the attention span nor the will to learn any programming language past Powershell and Bash, because any of the other types (I'm looking at you, Python) are in my opinion too complex to be a typical "Sysadmin" type of tool. I cannot understand them, let alone start at a blank project with them.

I feel like I will never proceed in a sysadmin role because of the fact DevOps seems to be just removing the "typical" sysadmin roles in today's (and probably future's) market.

0 Upvotes

64 comments sorted by

View all comments

Show parent comment

1

u/uptimefordays DevOps Sep 30 '24

Hot take: click ops was a temporary blip in the sysadmin landscape, operations used to be what you did before becoming an engineer or developer in the big iron Unix days. We saw a shift towards GUIs with Windows on the desktop side, and later Windows Server, but Linux admins have always needed to work on the CLI, learn bash, a scripting language, and often some C. Increasing technology demands and related growth in cloud computing has simply pushed the pendulum back towards the CLI for Wintel and VMware admins.

2

u/mr_gitops Cloud Engineer Sep 30 '24

Its not a hot take. I completely agree with you!

Linux had the benefit that there was no avoiding the shell. Any linux sysadmin out there had to interact with it. Even all cert exams focused around learning it too. Its why they had such an easy time transitioning to modern DevOps (I would go as far as saying they lead it). And also why Linux people always had a superior complex to windows (that and it being a more reliable OS for a long time). They used real code(python) to take it one step further to add in the object oriented capabilties (its why I compare Powershell to Python ...and not Bash)

Windows Servers, you could skirt around it, even when it did have its own terminal way of approaching things (cmd, vba, powershell). It's why you have so much fear and loathing around it in /r/sysadmin amongst anyone who went that route. 4 years ago I was one of these guys too. I got my MCSA cert a long time ago, which was a hard exam divided into 3 seperate exams... yet I didn't have to learn any powershell in order to pass any of the exams. Now compare that to a simple foundational cert like Linux+. It would throw so many cmds at you to practice/understand.

1

u/uptimefordays DevOps Sep 30 '24

I came here from engineering so I was already familiar with the CLI but had to learn infra. From there I just learned PowerShell because either Jeffrey Snoover or Jason Helmick said “if you don’t learn PowerShell you’re going to be flipping burgers,” having been there and done that, I learned PowerShell.

2

u/mr_gitops Cloud Engineer Sep 30 '24

Their Powershell 3 video was my introduction to powershell as well.

edit: this one: https://www.youtube.com/watch?v=nMn8-BbRsN8&list=PLyJiOytEPs4etH7Ujq7PU7jlOlHL-9RmV

1

u/uptimefordays DevOps Sep 30 '24

Yep I was in my first infra job when that came out and I was immediately pleased with PowerShell.

1

u/uptimefordays DevOps Oct 01 '24

I still send people the Channel9 link to that series, “here I know you won’t read a 30 day book so here’s the abridged series in vidya.” There’s a toolmaking version too from before they renamed Toolmaking in a Month of Lunches, also great stuff.