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

4

u/[deleted] Jul 05 '22

All the bickering here makes me glad to be an SRE and not a “DevOps Engineer” (whatever the hell that is…)

DevOps is a culture, not a job. Dev provides code that is ready to ship and Ops provides a means for getting the code where it needs to go with minimal manual intervention. Simple as that. “DevOps Engineers” are just ops people who work on deployment/release processes. If you are doing infrastructure work (k8s, networking, really anything HA related) you are an SRE, network engineer, infra engineer, sysadmin, server admin, etc.

0

u/victorj405 Jul 30 '22

I've been both and both do the same thing. Whether intended or not, SRE is the new DevOps. I'm guessing next will be Chaos Engineer although now that is just a service. Cloud Engineer is probably the best fit. Maybe AWS Person, lol.

1

u/[deleted] Jul 31 '22

I am an SRE and I don’t do “Devops Engineer” work. I do SRE work. We operate a strong devops culture but I don’t touch pipelines, build processes, or really anything that has to do with production code. Just as Google intended.

0

u/victorj405 Jul 31 '22

Well at least there is one person.

0

u/[deleted] Jul 05 '22

[deleted]

3

u/sabat Jul 05 '22

DevOps Engineer may exist but it's a meaningless misfire. They mean SRE, or they mean automation tools person, or something like that. Devops is an idea, not a technology. All they're doing is making themselves look stupid.

2

u/[deleted] Jul 05 '22

The industry does reflect this. They just give people who are doing Ops jobs the “devops” title to attract talent. The title is an HR buzzword but it is, in practice, the same as a sysadmin who works only on supporting apps and infrastructure. We do it the right way at my company: devs own their pipeline, tests and k8s resources.

SRE is also a completely different animal. We stick to the Google SRE manifesto like it’s our religion. We don’t manage dev pipelines and we don’t have any software engineers on our team. Our biggest focuses are on observability and automating fixes. Neither of those are part of the DevOps realm according to the people who coined the phrase.