1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either !asklemmyafterdark@lemmy.world or !asklemmynsfw@lemmynsfw.com.
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email info@lemmy.world. For other questions check our partnered communities list, or use the search function.
6) No US Politics.
Please don't post about current US Politics. If you need to do this, try !politicaldiscussion@lemmy.world or !askusa@discuss.online
Reminder: The terms of service apply here too.
Logo design credit goes to: tubbadu
Devops will have more job openings, network will have a higher salary, especially as you become more senior.
Devops people who don't know networking and/or general traditional sysadmin work are a crushing pain in the ass for those of us who have to support them though. Networking background will make you better at devops, but not necessarily vice versa.
Becoming a networking expert will also make you an expert in troubleshooting everything else in the IT stack from web servers not turned on to database queries causing high CPU usage. All because when something goes wrong it's the network fault.
I'm far from a networking expert, but I was usually the guy that had to reel the network guys back in when they said "you always blame the network" and stood around waiting to be proven in the wrong. It's amazing what a couple tracert and continuous ping commands will show (and how little interest corporate IT shows in doing even the basics unless monitoring is under their team).
US Sr SRE (devops) checking in: I would personally recommend the networking path. Caveat: A good engineer will know the background of both (curl, telnet, Iam, security groups, cidrs, domains)
Devops was mostly automating the stuff in between the other teams; and most of that is working out of the box these days. Most repos already have their Jenkins and docker files. How much admin are you expecting on serverless? Most people are pivoting to app support (ticket queues) or supporting managed services (on call).
As far as my day to day:
Pros: I do a lot of different things, we get downtime because we need to respond to things immediately, I don't have normal project/sprint planning. I have the keys to the kingdom. Higher pay than most other devs. I hack things together, I don't need to design workflows.
Cons: I am on call, I am the silliest clown (I get hardest problems), I need to understand a lot of moving pieces, sometimes when things break, there is a lot of pressure on you to find something hard. I regular have to Google "bash variable syntax" because I'm coding in 15 languages. Interviewing for jobs is impossible because no 2 positions are the same
What happens when you migrate from Jenkins? I'm currently in a multi year platform build using gitops and it is not mature and nothing fits together out of the box.
Just my experience.
As tools mature they will integrate easier but at the bleeding edge it still takes work. (Just trying to justify my existence I guess)
I personally don't like the idea of migrating off Jenkins, we blew our yearly budget testing our build platform in git. But it's all just platformed ci/CD, which is why I'm recommending the other path. Platform teams lost the goal recently.
Sysadmin and network roles are saturated. You only need a couple for a few hundred employees and colleges are pumping out dozens a semester each.
So unless you're interested in certification hell and rock a stellar GPA. I'd suggest DevOps of the two choices.
Database and legacy code roles are in demand though.
Here (central EU) I see a lot of sysadmin job offers. They tend to be less well paid than developers, so unless you can become some senior "expert", expect a pay cut. But people will always need someone to fix "the computer".