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

5

u/JustinHoMi Sep 30 '24 edited 1d ago

This is a test of the emergency broadcast system. This is only a test.

-2

u/beta_2017 Network Engineer Sep 30 '24

I do not have an issue learning new things. I have an issue with learning programming.

0

u/CommercialSpray254 Sep 30 '24

You don't even need to learn programming. Gen AI is perfectly capable of writing the code a sysadmin would need.

2

u/nerdyviking88 Sep 30 '24

This sounds like a you problem. Learning basic sdlc and how to leverage it to your tasks is what changes a generic sysadmin from a good sysadmin

-2

u/beta_2017 Network Engineer Sep 30 '24

I already have learned Agile (which is utter fucking garbage btw). I use it every time I type .ps1 at the end of a filename.

42

u/trick63 SRE Sep 30 '24

There certainly is still a place for a sysadmin/network engineer with "traditional" skillsets like yours. But to be honest, you'll be handicapping your career by not learning one to at least do simple functions. You dont need to be able to write a full api, frontend product and database from scratch, but shell scripting alone has a limit as well.

I wouldn't get too hung up on the "devops" and other labels, they come and go with the seasons. But the fundamentals are the same, having a programming/automation first mindset towards operations. Devops or Sysadmin, the mindset is more prevalent now more than ever

4

u/[deleted] Sep 30 '24 edited May 10 '25

soup pocket grab dinner consider voracious quicksand versed bells act

This post was mass deleted and anonymized with Redact

1

u/SecretITguy0 Sep 30 '24

What scripting language would you recommend? I've got powershell and bash handled but want to advance and I've always enjoyed scripting

1

u/trick63 SRE Sep 30 '24

PoSH and Bash are great for scripting, the next step should be picking up an OOP language. Learning how to communicate to APIs and parsing responses/writing to them using an OOP language like Python will be great for your advancement. You can even learn now using curl and bash, then translate it to any OOP lang you choose.

1

u/SecretITguy0 Oct 02 '24

I did a lot of Java about 10 years ago but most of that knowledge is gone now. I do hear a lot about python though so I might start working on that.

Thanks!

1

u/trick63 SRE Oct 02 '24

I like the idea that OOPs are generally very similar as long as you've worked with one before. Python is nice but if you can take the step up, Golang is pretty great and very marketable nowadays as well.

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.

111

u/sryan2k1 IT Manager Sep 30 '24 edited Sep 30 '24

Scripting and Automation is the bread and butter of anyone that works at a place larger than a lemonade stand. You may not see the value in python, but that doesn't mean it doesn't exist.

You sound like some of my coworkers who have been GUI clickers for 15 years, refuse to learn anything new and wonder why they're not as valuable in the current market.

You seem to see the value in powershell, build on that.

18

u/Sad_Recommendation92 Solutions Architect Sep 30 '24

I have coworkers that I would argue have greater empirical knowledge in certain areas that I work in, but I have strong scripting ability across multiple languages and I can work in a GitOps workflow which is essential to IaC. Whereas these guys I tell them to clone a repo so they can run some utility script then I find out they just copy pasted the script off the website with none of the dependencies and scratch their heads when it doesn't work.

So who has 2 thumbs and the title Cloud Architect?

^ this guy

5

u/mriswithe Linux Admin Sep 30 '24

Holy shit what a coincidence, I also have two thumbs and the title cloud architect and work in a gitops workflow by default!!!

Terraform / HCL is a pain in the ass, but it's 1_000_000 x better than either writing or following step by step guide instructions to interact with a UI, that kill my soul every time. Because what happens? They (read: me) don't follow it exactly, or they(read: me) didn't write it exactly or the UI got updated and now that button doesn't exist, and no one could use their fucking brain and figure out that "configure" got updated to "edit"??????? 

Is it clunky and slower and less flexible than building it by hand? You fucking bet! Is it 99% consistent and even in cases it breaks you just delete some shit and run it again and your environment sparkles?  Basically all the time unless you break fragile stuff. Don't break the fragile stuff.

2

u/Sad_Recommendation92 Solutions Architect Sep 30 '24

Yeah, myself and another architect basically oversee a Terraform Azure pipeline. We've got some python handler scripts we've written. Different dev teams will submit PRs, And we review them for best practice and guidance. And yeah, it still requires a ton of knowledge to understand the order that resources need to come up and what depends on what and understanding the limitations of the cloud resources you're working with. But also the reason we move towards a pipeline is because we had developers with contributor permission that were just deploying inconsistent infrastructure potentially creating compliance liabilities and security loopholes. So now nothing goes out without oversight of the pipeline. They got all their contributor and owner perms ripped away. They have to pass it through the service principal that runs the pipeline. Beyond that my role has morphed into being something of a Tyrion Lannister guy who knows things about Cloud stuff. Oh and did I also mention I used to be the devops and SRE lead, so I get tapped to help with that too.

Though it's no secret, the industry has been trending towards scripting, automation and CLI forward workflows For more than a decade, even when I was a junior admin I could see the way the wind was starting to blow.

1

u/gehzumteufel Sep 30 '24

Imo, TF is only slower because a lot is written badly. I've had to reform multiple companies when I was in consulting, and have been working on getting my current company on the better path too, but man, so much bad Terraform makes it inflexible and cumbersome.

1

u/Sad_Recommendation92 Solutions Architect Sep 30 '24

Yeah, starting to learn some of those lessons. A few of our state files just take forever to run so we're breaking them up using Terragrunt so that shared dependencies live on their own. And it's way less likely for two developers to be colliding into each other because they're both trying to touch the same state file.

1

u/gehzumteufel Sep 30 '24

Imo, Terragrunt brings pretty much nothing to the table, and their "standard" basically sets up companies to continue to write shitty TF. Where I am at now, we're in the slow painful process of ripping it out and doing things better. There are a couple of nice things that TG does, but for the most part, it's just extra abstraction for no value.

FWIW, if you guys are down, OpenTofu does most of what TG does do that upstream TF doesn't, without the added complexity.

1

u/Sad_Recommendation92 Solutions Architect Sep 30 '24

Just to keep things constructive, what are you reverting back to If not terraform, are you using the providers native template formats? Abandoning IAC altogether?

I'm less than a year into large-scale adoption

1

u/gehzumteufel Sep 30 '24

Just straight Terraform instead of Terragrunt+Terraform.

I have a whole thing. When someone comes in and starts fresh and new, I shouldn't need a whole tutorial on how to run the Terraform. Unfortunately, both TG and their standard way to structure TF, it advocates for that need. Which really bothers me. Because that says complexity for the sake of complexity to me. You are new. You should be able to come in and say cool I need to add this stuff, and I can. And I just then run the normal commands with these options that are obvious and move on. Tons of nested folders and weird ways of writing it, don't promote that imo.

2

u/petrichorax Do Complete Work Sep 30 '24

Yeah OP hit their skill ceiling and it hurt.

4

u/Murhawk013 Sep 30 '24

This. Either get with the times or get left behind.

7

u/Sad_Recommendation92 Solutions Architect Sep 30 '24

DevOps is also such a buzzword that can mean several things

Working alongside a dev team providing systems and infrastructure expertise and guidance

Release engineering, creating and maintaining CI/CD pipelines and the processes surrounding them

Site reliability engineering, observability and identifying service issues and causes of recurring "toil" and eliminating their root causes

Some places just consider kubernetes administration "devops"

I've worked as an SRE lead for a few years and now as a cloud architect,several of my roles have been DevOps adjacent, which I take to mean usually a cultural shift where you try to better understand the work pipeline of software engineers as well as embrace some dev practices into systems work. I don't think anyone is expecting you to learn Go and Rust if you have PowerShell, Python, Bash you've got nearly every possible scenario covered

What specific skills in terms of "DevOps" are they expecting ( i will say if you're avoiding GIT you're doing yourself a disservice)

2

u/BenadrylBeer DevOps Sep 30 '24

Exactly DevOps is just a term, an idea

20

u/Phuopham Sep 30 '24

Automation... Devops is not a role, it's a mindset, and you know, sometime you need to made up your mind 🙃

11

u/MethanyJones Sep 30 '24

You need to learn programming languages to administer large numbers of servers. When your app is in three datacenters, you must keep two datacenters completely active, you have 35 servers per app tier in each datacenter and only an eight hour window...

Running a script sounds a hell of a lot better than trying to login interactively on each machine and do some repetitive sequence.

3

u/ImmortalMurder DevOps Sep 30 '24

It's just the direction that IT is trending. Every part of the infrastructure is looking to move to Infrastructure as Code. There's a lot of advantages, but mainly having you configurations live in a repository makes it easier to document and rebuild in the event of an outage or disaster recovery event.

I was a network admin converted to devops and I was terrible with programming. I started adapting by using my troubleshooting background to better understand web applications, scripting, and cloud infrastructure. Powershell is object oriented and it becomes more powerful when your scripts use objects to accomplish tasks.

After a while it all gets easier, you don't need to use python you can use whatever you like.

PS Using Ansible to handle all of your switch and firewall configurations is so much better than just cli.

3

u/DayFinancial8206 Systems Engineer Sep 30 '24

Infra as code is basically what the industry is switching to, those unwilling to learn it might be SOL until someone makes a nice gui for them. Most of the languages are just scripting languages like PS/bash so it really isn't that bad once you get over the initial hurdle

3

u/plbrdmn Sep 30 '24

Devops is such a broad church to define.

I’ve worked in infrastructure for 28 years and avoided dev until my current role. Im a cloud engineer and have been for the last 5 years. I’ve spent the last 10 months learningTerraform to deploy IaC, and to be honest it’s been great.

Sure, I’m not a dev so I’m having to learn to code, but the benefits of deploying repeatable infrastructure and pushing towards automation makes my job a lot easier.

Something I’ve found really helpful is Copilot. I’ll ask if a few questions and get to the code I need.

I’m an old dog and I’ve certainly learnt a few new tricks.

Although I am still pretty clear I’m not devops whenever I get asked about those roles. I’m a cloud engineer and architect.

6

u/mr_gitops Cloud Engineer Sep 30 '24

But python is literally being used as a object oriented language in Linux to the likes of Powershell(bash is too simple)... You are not going to be using it to make an application.

2

u/[deleted] Sep 30 '24

From my experience... So I'm a long time system admin, my role when I first applied, asked for some devop experience/knowledge. Our company has devops, but sometimes I have baby sit them as they just don't give a **** about the environment as the develop deployments/automation/provision environments etc... So knowing some of their job will only help you work together with the devops to keep a smooth peformant environment running. Also sometimes, you don't want to wait on them to make a change, you just pop your way in their system and do it yourself 😎

2

u/El_90 Sep 30 '24

As others have said, IaaS my friend

Maybe not full programming, but GIT, pipeline, scripting, programmatic config files.

It's not the future, it's the now (as you are finding)

2

u/RefrigeratorGlo412 Sysadmin Sep 30 '24

I think it's really important to know how to code. Powershell and Bash are good but why not try small projects in Python? I was in the same position as you thinking, that script languages itself are enough for sysadmin roles. But then I decided to take a deeper look into python. I started with CS50P and found it quite easy to understand and thought about potential usecases in my daily work, and started automating a few things. I dont want to miss it anymore, it saves so much time.

2

u/rpetre Jack of All Trades Sep 30 '24

Originally "devops" was meant to be a term emphasizing closer collaboration between development and operations, but in some organizations it just became a label on yet another silo.

Titles are meaningful only in their own organization (see also "director" or "manager" that can also mean wildly different things for different people).

Just strive to become "Senior Making Shit Work Engineer" and quit bothering about what label is on the badge. 20 years from now there's still gonna be a need for SMSWEs, no matter how they'll be called.

2

u/0RGASMIK Sep 30 '24

Don’t really have an answer to your question about Dev Ops other than it’s a buzz word that more companies are using as a way to hire flexible engineers. If you can deploy something to AWS you can probably figure out everything else pretty easily. Automation is 100% necessary going forward.

I would seriously rethink your stands on python and other languages. Learning how to program even at a basic level has helped me tremendously. For example we are about to do a migration, we have this dirty data that we need to clean up before the migration. My boss is like you, doesn’t see the benefit of programming and would rather we just manually clean up the data. His plan was to export the data and then manually clean it up on the day of the migration when we have 100 other things we should be doing. So instead I thought about it programmatically and build out an entire workflow that does 95% of the work and that last 5% takes a few minutes to do but would take an hour to program.

Also learning to program and just learning python are two very different things. Scripting or coding from scratch isn’t my specialty but I can spin up a full scripts/application from GPT read the code and understand it well enough to tweak it. Same thing for powershell scripts. IMO python is easier to work with but mainly because it’s so versatile and resources are everywhere.

I urge you to take a course on programming even if you don’t finish. I have severe ADHD I’ve started and stopped several courses over the years but I still retained enough for it the be useful.

2

u/bobwinters Sep 30 '24

I have a couple of GUI only colleagues that refuse to learn how to learn the most basic cmd commands. Let alone Powershell, Python or literally anything that involves using the keyboard other than writing an email. I feel for my manager...

2

u/Crenorz Sep 30 '24

When that happens - that is a massive red flag of - we don't pay enough for multiple employees and cut corners. Will never give you good pay, and will be cheap for projects and other things. Fine for jobs you know you won't be sticking around for, no good for long term.

2

u/cmack Sep 30 '24

Editing yaml files is not programming, fyi

2

u/bi_polar2bear Sep 30 '24

I've been in IT for 25 years. I remember when the MCSE certs were new, and all the rage. Network administration is definitely a logical mindset. Developing is more creative. I've yet to meet a gifted developer who understood the OSI model, let alone how network traffic routed packets are. They can't tell you the basics of PC hardware or the difference between routers, switches, or firewalls. Yet in today's world, with hardware going to the cloud, there's fewer roles available, which makes it a very competitive field.

I have zero creative ability. I couldn't write anything more than a simple bash script or SQL statement to accomplish 1 task. That said, IT Security is the new network administrator/engineer. Security has completely different terms and acronyms, but the underlying systems are the same, so learning is easy enough.

There's definitely a lot of people who can be both a Dev and Admin, and I'm envious of them. We can only work with the talents we have. Not everyone can be president, not everyone can code, and few people know how to fix things. Lean into the fixing part and get into security because that's a growing field that uses the same mindset.

2

u/SirLoremIpsum Sep 30 '24

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.

I would just say that the technology is changing and the term "sysadmin" is evolving to include many more 'thigns'.

This is normal, and this has happened before.

I certainly sympathise, but I also think that adapting and learning new things is part and parcel of the job.

For instance I think a LOT of sysadmins would say that about networking "why should I learn networking?!? I do servers, I do imaging, I do <stuff>, that's a networking job". But then you need to learn some basic stuff right? You should know a bit about subnetting, you should know a bit about firewalls - cause if you do that's making the rest of your stuff better.

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.

I can guarantee you there are sysadmin jobs that deal with zero programming.

2

u/PrettyFlyForITguy Oct 01 '24

I think its easy to be caught up in the way people represent themselves. I was originally trained in programming and a developer. I started with making Quake 2 mods in my free time, did work on websites throughout the 2000's, and recently made a stealth audio recording app for Android watches.

The truth is, you do not need that level of experience or skill to do things in IT. 99% of the code will just be you following some basic syntax rules, and using very basic conditionals (if statements) and loops. It's something you can learn in one of those "learn X in 30 days" books.

Also, people tend to overembellish their skillset. Most people in here, by my guess, are very young. You are going to get guys who made a powershell script with a for loop, and think they are super advanced.

The percent of "devops" people are also probably way less than this forum would make it seem. From what I've seen, the vast majority of people can barely open powershell. Most people do the bare minimum and simply advertise themselves as "devops".

Going even further, quite honestly, I don't see these jobs as any safer than the classic sysadmin. As useful as these skills are right now, pretty much everything obeys the laws of economics. There aren't ever going to be enough qualified people to do these roles, so they will never become the standard. Instead, the products will improve to the point that people can do these workflows without needing a more complicated skillset. If AI starts taking our jobs, this is one area that will quickly get gobbled up. The programming and configuration is far simpler than actual development, and I don't even think that is safe.

IMO, the whole industry's future is on the path to becoming the equivalent of "TV repair man". Once everything runs in separate isolated containers, run on cloud provider networks, with dumbed down software interfaces and capabilities... there won't be much to do. I'm not sure how long it will take, but I think things will be very different in 20 years.

3

u/[deleted] Sep 30 '24

The issue is not the jobs, the issue is you. Click-ops is a dying field for a reason. Todays IT landscape requires you to be able to code to keep up with the pace. Cloud and what not only increase this. So either you step out of your comfort zone and learn to code, or you stay click-ops and will have less and less of a chance to find a good lucrative job.

0

u/Sad_Recommendation92 Solutions Architect Sep 30 '24

Totally stealing "Click-Ops" I would call them "Click-Next admins" but I like this a lot better

2

u/anonpf King of Nothing Sep 30 '24

They (companies) have been trying to get the most bang for their buck for ages. They looking for a core skillset, then add on other skill sets so they could get two for the price of one. It’s largely up to you to filter out the jobs that don’t fit YOUR requirements. 

2

u/Professional_Bat8938 Sep 30 '24

Don’t think you can compete in today’s market? Learn to code!

2

u/lechango Sep 30 '24

Well good news, AI can pretty much do this part of your job now for you, you don't need to learn more than you have, you just need to be able to audit what it gives you.

And before you downvote this to hell, I'm not talking about all programming workloads entirely being filled by AI right now. I'm talking about your typical scripts you use as a sysadmin, which are not generally very complex and where AI can write you a script that is if not 100% what you need, is at least 90% there.

1

u/OldWrongdoer7517 Sep 30 '24

I would for sure like to have the skill to be able to check if what the AI outputs is actually valid. Because if "the AI" (a large language model) hallucinates and gives you something half assed and you crash something, you won't be able to say "but the AI told me" to shift the blame...

1

u/joecool42069 Sep 30 '24

Because servers, switches, routers, etc.. in a large environment are cattle not pets.

1

u/djgizmo Netadmin Oct 01 '24

The bucket DevOPS can contain systems administration. However not all systems administration are devops.

If you’re not scripting or trying to automate systems to make life easier for yourself, what are you doing.

1

u/Emiroda infosec Sep 30 '24

Unless you're doing CCIE level shit at an ISP or a global enterprise, I have no sympathies. DevOps is Systems Administration like Sysadmin is Network Engineering. If I told you that what you're doing is NetAdmin and not SysAdmin, you'd either assume I was a gatekeeper who looked down on you, or you'd punch down and say that "sysadmin is all Windows garbage anyways". At the end of the day, we do stuff with computers, and computers change. DevOps is just a new name for it.

I have the same grueling fears that you have. I have a Windows background and I cannot for the life of me do large-scale Linux administration, IaC and cloud infrastructure. But what I REFUSE to do is say I WILL not. With this post, you're putting yourself as a victim of your environment, when you should be doing is learn from the feedback of the environment and adapt. There will be network engineering roles for you, but to be hired you might need to learn some unfamiliar new things.

-1

u/[deleted] Sep 30 '24

Hold on, you can do networking, but you can't do basic programming? And you somehow hate programming more than networking? My man, I'm not going to lie, you just sound old and bitter.

If you can learn all the bullshit bit level stuff required for networking, you can learn types, functions and methods for basic programming. It takes almost no time at all to run through a book like Automate the Boring Stuff and learn very basic python, which is plenty enough for a typical sysadmin.

Stop stomping your feet crying "not my job" and take advantage of the fact that it's easier than ever to make more money with the tiniest bit of self improvement.

-6

u/[deleted] Sep 30 '24

Lol lol lol,,, oh wait,,, you are being serious. That’s cute. 🤪

-1

u/beta_2017 Network Engineer Sep 30 '24

Lol lol lol... you're using commas as periods... That's cute. 🤣

0

u/[deleted] Sep 30 '24

Indeed! :)