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

3

u/farinasa Jul 04 '22

The definition of DevOps changed? When?

0

u/[deleted] Jul 04 '22

[deleted]

4

u/farinasa Jul 04 '22

It has always been an actual role. Every engineer should be doing both dev and ops. Temporary DevOps roles are permissible to set up the initial tooling needed to achieve a DevOps environment. Until you get to that point organizationally, you aren't implementing DevOps. You are using the old model of dev and ops being separate, but you call your operations people "DevOps engineers". The company posting a position doesn't define what DevOps is.

0

u/[deleted] Jul 04 '22

[deleted]

-1

u/farinasa Jul 04 '22

And you will be able to find companies that continue to ascribe to the old ways as you prefer. But, you're 100% wrong otherwise. You're saying that I can change the definition of a word just because I say so.

Of course it can be UNDERSTOOD to mean something different. But the definition remains the same. You just can't get your head out of the old model because you are unwilling or unable to learn the tools that enable the new model.