r/devops • • Jul 04 '22

DevOps is a subset of Software Engineering. Stop all this madness of "Software Engineer vs DevOps"

DevOps started as a philosophy, a way to bridge the gap between operations teams and software engineering teams in-order to provide more efficiency and transparency. Why should people who develop the software not care about how it operates? Why should the people who operate the software not care about how it was developed?

Fast forward to today, and the philosophy has actually become a job title.

In the modern day and age, the term "Software Engineer" is actually meaningless. Software Engineering is a gigantic field with many subsets.

Some of these subsets include:

  1. Web Development (this can be farther split up into fullstack, frontend, backend)

  2. Mobile Development (can be split up into fullstack, frontend and backend as well)

  3. Game Development

  4. Embedded Systems Engineer

  5. Data Engineering

  6. Machine Learning Engineering

  7. Virtual Reality Engineering

  8. Desktop Application Developer

  9. "Low Level Developer" (things like Operating Systems, Kernels, Compilers, etc)

  10. Dozens of others I can't remember at the moment

Do you want to know another subset? DevOps!!

Yes, DevOps in the modern era is nothing but a subset of Software Engineering. That's going to trigger a whole lot of people who come from the operations side of things (which is 90% of this sub), but it's true.

Modern DevOps = A software engineer who focuses on infrastructure, automation and internal tooling. These are the folks who write code to make sure that all the other code that was written, works as expected. They also write code to make writing code easier!

Sure, they may use more pre-made tools than web developers. But web developers use plenty of tools and pre-made services too. Modern web development in fact, is all about gluing together pre-made services, and there's plenty of subsets that I listed above that are tool heavy too (like data engineering), but I digress.

Synonyms to the "DevOps Engineer" title include:

  1. Platform Engineer

  2. Cloud Engineer

  3. Infrastructure Engineer

  4. Systems Engineer

  5. Site Reliability Engineer

and probably a few dozen I can't remember right now.

Yes, the titles in the industry are a mess. But I hope this clears things up for you.

That's why it's silly to say "Software engineer vs DevOps". It's like saying "What's better, a vehicle or a truck??"

934 Upvotes

248 comments sorted by

View all comments

Show parent comments

5

u/khobbits Systems Infrastructure Engineer Jul 04 '22 edited Jul 04 '22

Why not both?

I consider myself an Infrastructure Engineer and I've pretty much been doing both for most of my professional career.

Right now my main focus is building out a datacentre with 180 racks.

This month I have been:

  • Working on the floor plan/rack layouts

  • Racking up switches

  • Ordering cross connects

  • Talking with vendors about the SDN solution we're going to roll out

  • Setting up a new HCI VM solution, in staging ready to be installed

  • Tweaking the Terraform used our cloud render farms

  • Hosting a training session on using EKS in AWS (gitops ftw)

  • Helped a colleague out with Kubernetes troubleshooting

  • Discussing plans for an active directory migration

  • Code review

I wouldn't generally suggest what I was doing is part of software engineering, except when I'm taking part of scrum/standups with Dev Teams.

Edit: Just to clarify, I've done software development in Java and PHP, and can bungle my way through a dozen or so languages. Was a lead developer on an popular open source project.

1

u/Shep_Book Jul 05 '22

There’s a big part of me that misses working with hardware. I loved volunteering to drive to Ashburn (when I lived/worked in MD) to rack and setup the servers my team designed and built.

I’m kinda jealous reading about what you’re working on.

I specifically moved out of a pure “dev” role and back to a more ops focused DevOps role because I missed working closer to the systems and their monitoring and automation.