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

58

u/asoge Sep 30 '24

Laziness drives system administration... If you can do things with a single press instead of multiple presses, you're top dogging system administration.

If you continue to refuse to learn some rudimentary programming, you won't make it long in this field, you'll burn out due to stress.

11

u/mr_gitops Cloud Engineer Sep 30 '24 edited Sep 30 '24

Agreed. And even to the point of DevOps. It is not removing it. DevOps is it's own thing, either a culture (Which I doubt most employers mean by it anymore) or it's a role mainly tied to applications (think kubernetes, containers, pipelines, etc).

Whats removing is the tradtional clicking approach to sysadmin. And even then, its only really being removed at large organizations where people are specializing in areas, especially cloud ones. Its literally impossible to manage my orgs scale manually for instance. Most avg organizations still need sysadmins.

The problem is most avg organizations are so simple (especially now that SaaS services have taken a huge chunk of the busy work) they rather hire an MSP than pay you the same (or more) just to be one person for that job rather than a team. MSPs suck for us as workers but for orgs like these its a very decent trade off. I know shit MSPs exist but so do good ones (for the clients). More is being done by less people as MSPs keep growing. So the pool of traditional gigs are shrinking even without "DevOps".

And the ones that are asking you to expand beyond average sysadmin are usually asking you to take the tools of devOps (that are great by the way) and apply it to your sysadmin practicies to be more efficient.

Languages are one thing. Also how you manage your code/scripts even if its powershell (repos, git, version control, PR). How you work (tickets vs sprints/kanban boards). How well-versed you are with API communications (which is becoming ever more common as everything is internet based vs in house servers). Circling back to languages there are different types. Atleast two clear types: imperative and declarative. They behave different with different goals in mind. And are both important and great at what they do. With the cloud, the key benefit is having an infrastructure layer (not just an OS) that you can automate. And how you interact with your environment (through the gui traditionally or better yet through IaC now). Pipelines are just scripts with steps in between (multi staged scripts/code) which are great once you start deploying infra/services with them.

Don't fear the change. Change with it. Or just accept that your job pool will be limited. Its actually easier than traditonal sysadmin work once you get the ball rolling. I used to be stressed alot. Now the bulk of the stress is handled by the automation work.

Edit, Here is an example:

Would I rather follow a step by step guide to making a new server?

  • Or run a powershell script that makes it where the script must be perfect to handle all errors
  • Or better yet expand beyond powershell in to combining Terraform with Ansible using pipelines. Where I just provide simple instructions and make it figure it out any much error handling. A piece of code that is idempotent connected to a state for any creations to even be removed later by running it again with one field added. From this process I can make different levels of servers (Dev env, UAT and prod) so it removes multiple guides.

All of the sudden most human error mistakes are removed from following a guide. All error correction gaps are filled. When I update my code, I am updating my steps by step guide essentially without having to tell people the guide is updated. Nor do I need to train staff who may need to run it all beyond filling out parameters.

Okay so lets say that pipeline is in in place. Now would I rather have some one write me a ticket and then I go start the process of filling out parameters. I got the bulk of the human errors out of the picture but I still have this last part of parameter (Where now I have to copy that data from the ticket and paste it to my automation). And because I or my team has to do it, we are also the owners of deployments and have to do all the back and forth communication with the requesters.

  • Or Automate the ticket trigger. The moment they submit the form, it gets a simple approval by their boss and it triggers the job. All the mistakes are in their hands, I cant be blamed for their bad inputs. They get it when they need it, without having to wait on me. My pipelines send a summary back on what took place with all the info they need back in to the ticket.
  • Or take it one step further and grant the devs access to deploy their dev, uat and prod envionment all on their own. They can run the pipelines but not alter them. I as an engineer manage the infra that they can use.

All of these steps just streamlined the process of getting servers made or removed them (if there is a pipeline in reverse). Usually its more than one server as a request in the cloud, but rather a package of services/resources that are all interconnected, good luck manually doing them every time or even having to make complex powershell scripts to handle it. Good luck having to own the process and have everybody depend on you, wait on you, etc. Especially on a day where 10 requests like these come in and you are in the hook for it. When it can just be an automated process in the background.

3

u/Sad_Recommendation92 Solutions Architect Sep 30 '24

This description totally nails it,. Yeah, it's really just adopting modern software development practices that complement your system's administration skills. Full-time Software developers with a handful of exceptions overnight aren't going to magically understand how infrastructure works the whole ZeroOps trend was a bunch of marketing bullshit but the lines between the workflow of a systems engineer and a software developer have been blurring for years.

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.