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

0

u/[deleted] Jul 04 '22

[deleted]

28

u/Dealoite Jul 04 '22

I don't really see the contradiction there tbh, plus I can show you plenty of "infrastructure engineer" jobs that have literally the same role as devops engineer / cloud engineer / blah blah blah and involve plenty of programming / writing of software.

For example:

https://jobs.lever.co/spotify/a83d82a1-47aa-4a76-b6df-7f30b959cdaf

Sounds a lot like DevOps Engineer / cloud engineer / blah blah blah, doesn't it?

The titles are meaningless at the end of the day, the only thing that makes sense is that it's all under the larger umbrella of "software engineer"

14

u/Warkred Jul 04 '22

Infra engineer has nothing to do with devops. But coming from software engineers, it's acceptable to make that mistake.

0

u/[deleted] Jul 04 '22

[deleted]

5

u/Bob_the_gob_knobbler Jul 04 '22

Systems engineers don’t do that either.

6

u/PartemConsilio Jul 04 '22

Not a lot of people do that anymore, period. Thanks to the cloud. But people who write infrastructure-as-code are often titled infrastructure engineer at different shops…and its firmly in a DevOps skillset.

6

u/BothAirline1 Jul 04 '22

Seriously?!

3

u/[deleted] Jul 05 '22

[removed] — view removed comment

3

u/[deleted] Jul 05 '22

Someone else computer duh.

5

u/wtfsoda Prime Minister of Logs Jul 04 '22 edited Jul 04 '22

Not a lot of people do that anymore, period.

Come to the telecom sector. I promise you there’s a lot of people still doing “that”. It’s just grueling and ugly and not always seen in your typically air conditioned, coffee-supplying office building.

Anytime a new Data Center gets built? A new office complex gets erected, a new school, anytime a building goes up I 100% assure you there are loads of people (low voltage technicians, often or at least in my part of the US: unionized) not just running cables, but actually doing some basic networking on a core switch once the structure is in place to construct MDF/IDFs.

4

u/PartemConsilio Jul 04 '22 edited Jul 05 '22

Sorry, but I meant the infrastructure work which is traditionally considered “operations” within the IT framework of, say, a retail business. Most of those places do not have their own in-house data center stuff. They actually rely more on businesses like yours to backbone off of and then they leverage the cloud for everything else.

TBF, I should also call out DoD and financial sectors for also still needing rack and stack techs. I used to work for the DoD doing a lot of that same work. But even now they’re transitioning to a more cloud-based approach in multiple sectors.

1

u/Masterzjg Jul 04 '22 edited Jul 28 '25

cover rain crawl paint waiting plants ancient station bike growth

This post was mass deleted and anonymized with Redact

-11

u/Dealoite Jul 04 '22

No one is saying software engineering == devops.

That's the entire point of this thread, the comparison doesn't make sense because devops is a subset of software engineering in the modern day and age. Also see edit.

Not many are connecting cables and switches in the cloud era. Infrastructure engineer has transformed from it's traditional meaning as well.

Everything is now all about writing software. It just depends what that software does.

22

u/pythbit Jul 04 '22

Not many are connecting cables and switches in the cloud era

Oh, I guess those cloud datacenters run on magic?

10

u/[deleted] Jul 04 '22

This thread is showing me how silly the titles are in tech. Because there's infrastructure engineer which means you're writing code, but then there's also infrastructure engineer which means you are physically connecting cables and switches.

16

u/pythbit Jul 04 '22

Welcome to Information Technology, the field where everything is made up and the titles don't matter!

4

u/[deleted] Jul 04 '22

Ha! So true.

I like the simplicity of just calling everything a subset of software engineering, but I think you are right that it misses nuance in some cases.

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.

→ More replies (1)

-3

u/Dealoite Jul 04 '22

It really doesn't matter.

We are talking about the modern era, and the fact is that people who manually connect cables are getting rarer and rarer.

The industry has already moved on. Go on LinkedIn and search "infrastructure engineer" , they are 95% just software engineering jobs.

2

u/pythbit Jul 04 '22

Yeah, fair enough. I don't work for a tech company, so I think my perspective is a little different.

0

u/[deleted] Jul 04 '22

[deleted]

→ More replies (1)

2

u/my-ka Jul 04 '22

Yeah, it is getting harder do distinct a role because of that description mess

-5

u/[deleted] Jul 04 '22

There's no contradiction.

For example:

https://www.dropbox.com/jobs/listing/2413410

How is that not a subset of software engineering?

Funny enough, they list it as "infrastructure software engineer", but the job description would fall under "data engineer".

Do you now see how silly all of this is?

5

u/my-ka Jul 04 '22

Maybe the company has dev ops budget and now everything is called fckn devops

-3

u/Equivalent_Loan_8794 Jul 04 '22 edited Jul 04 '22

Ah so you interface with something different than software? How’s does one interface with hardware or infra… without software? Unless one is a physical infrastructure engineer.

But if that were the case I’d have to ask why a physical infra engineer, dctech, would be wanting to INSIST dev is in their name and covers what they do.

Y’all need Jesus Jez Humble