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

53

u/TheKingInTheNorth Jul 04 '22

The key is “I write software.” I encounter so many DevOps and SRE teams that would never say that. They would say “I use tools.” And these teams are nothing more than traditional ops teams using consoles and modern tools that enable automation without ever having to code something beyond an occasional config file/template.

And those teams and companies are left with shitty software being thrown into production to be supported by people who are only as capable as out-of-the-box tools like dynatrace enable them to be.

19

u/focus_black_sheep Jul 04 '22

let's be honest every engineer uses tools, no one is writing machine code from scratch to develop a new tool.

6

u/TheKingInTheNorth Jul 04 '22

Absolutely. But using these tools should help create feedback loops into the application software you’re writing, it’s operational quality/instrumentation, and additional software that integrates with and leverages operational tools and the APIs they expose.

You don’t get all those benefits when the DevOps team doesn’t write code inside or outside the application stack they support.

13

u/rebelopsio Jul 04 '22

100%. I’m a DevOps Engineer by title but it’s a modern ops team. We work in our own silo with our own org structure that differs from engineering.

30

u/Spider_pig448 Jul 04 '22

YAML and HCL are code. They're just kidding themselves

14

u/nultero Jul 04 '22

This is a very elaborate bikeshed we've got here

How come you guys can keep a Kubernetes cluster alive through a jillion requests but the McDonald's ice cream machine is always down?

7

u/xokako Jul 04 '22

They forgot dockershim was deprecated

0

u/[deleted] Jul 04 '22

[deleted]

8

u/MindYourBusinessTom Jul 04 '22

Knowing what bad code looks like and how to create a jira story and ping a PO is helpful, too

3

u/[deleted] Jul 04 '22

[removed] — view removed comment

4

u/TheKingInTheNorth Jul 04 '22

“When the application breaks and my DevOps team gets paged, I open dynatrace to see where the errors or latency are coming from. Then I pass the ticket to the application team with that info.”

2

u/[deleted] Jul 04 '22

[removed] — view removed comment

6

u/TheKingInTheNorth Jul 04 '22

This is not me or my team, I’m more of a contract software engineer. But it’s something I commonly see at big fortune 500s on their Ops team.

For the most part your summary is correct. Occasionally the error observed is documented and has a standard ops procedure (bounce a service, flush a cache, etc.). Rarely the DevOps team will fully diagnose an issue and code a potential fix (missing null check or something similar that caused a service to crash instead of reject a request). But 90% of the time, it’s a 30 minute triage in Prod followed by a handoff to a dev team for deeper investigation or resolution.

-7

u/sunrrrise Jul 04 '22

What do you consider as a code? Because writing JSON templates is hardly writing a code. Same for Terraform. Hell, I have a doubt whether code written in Python that clones entire resource group can be considered as a software.

3

u/TheKingInTheNorth Jul 04 '22

Yep, agree with you on all those. Software Engineering, to me, requires a task that’s complex enough that it requires functional or object oriented design, logging, monitoring of its own, is worthy of code review, etc. All the things a typical application’s code would be accountable for.

SRE is what happens when you give Ops problems to software engineers (what I believe good companies are doing when they have DevOps roles that write real code).

DevOps is what happens when the application development teams own all aspects of their own operations.

Companies with DevOps teams and roles that barely write scrips and mostly depend on packaged tools and to do their job is just the next evolution of companies following a legacy and separated dev/ops model with all the same pitfalls.

1

u/Shep_Book Jul 05 '22 edited Jul 05 '22

I was but a young sysadmin when the concepts of DevOps and SRE really started taking hold.

I went to a conference and met Adam Jacob, the original author of Chef, and it’s where I first encountered the concept of “DevOps”. It was a way of working, not a job title. Sysadmins had been writing bash/python/perl scripts for ages, so they were already writing software.

On the SRE front, one of the people I consider foundational to the initial concepts of SRE, Tom Limoncelli, came to our little sysadmin meetup and talked about SRE at google and what it meant there. (Also talked a little bit about ganeti, which was really neat in the days before docker and k8s.)

One of the keys of both DevOps and SRE movements was the sharing of responsibilities and the breaking down of silos.

It was never about trying to draw a bright line to demarcate the separation between those who write software and those who “don’t”. One of my favorite quotes from that era was that sysadmins are polyglots, even if they don’t realize it.

While the negative effects of silos never fully went away, they have largely softened in highly functional teams. In such teams, tossing the code over the wall to the sysadmins to run and monitor, is a thing of the past. A well oiled team has software engineers that are dedicated to writing new features and such, working with and on call with the ops folks who run it in production.

In my current team, we have application teams that are responsible for specific parts of our overall app, who use systems setup and maintained by our CI/CD team. Those systems output the packages and containers my team uses to build into releases, and those releases go to the ops teams that manage the instances for customers.

The key thing in all of this is that if there’s an outage or critical issue, it’s not just the ops folks that are on call and digging into instances. We bring in whoever is needed. Sometimes that’s my team since we built and configured the core systems they use, sometimes it’s the app team that wrote that part of the code, etc. It means that when there’s a problem, we all come together to work on it, then do what we can to prevent it from happening again.