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

2

u/my-ka Jul 04 '22

Yes. Unless it is broken. So you confirm the idea that it is not about a rock star.

1

u/farinasa Jul 04 '22

I never said anything about a rockstar?

DevOps is simply the automation of ops and the integration of infra into development tasks. Tools are required to accomplish this. Everyone should be familiar with the toolset so anyone can fix it if it breaks. In the meantime, everyone is developing, deploying, and assuring the health of their systems.

If you want a team dedicated to the toolset, fine, but that team is also a product team whose customers are internal engineers. They treat the automation toolset as their product.

1

u/my-ka Jul 04 '22 edited Jul 04 '22

Just a script writer then? Sounds a bit artificial and redundant. Why would a senior engineer need to explain somebody what to write instead of doing himself?

I prefer every team member to leverage DevOps tools and practices instead of a dummy person doing just that.

If it is a copy-paste job i can write a script for that.

Remember years ago one "mega" architect tasked 2 DBAs to produce 100 prosc and 100 triggers. i was one of them. We had a week. In an hour i realized that they are similar and have a pattern. One more hour later i had a script writing both procs and triggers.

Question, what was wrong and what is good in the plan and the implementation?

2

u/farinasa Jul 04 '22

You clearly didn't read anything I wrote.

I said everyone should know the tools and be able to fix the tools if they go down. If you prefer to have a dedicated team there are ways to do that. So what point are you making? That senior devs are too good to understand the tools they utilize?

I've worked with someone like you in every job. You belittle people's work, then go on an hour tangent about how good you are. Often not even understanding the topic.

We all see right through it.

3

u/my-ka Jul 04 '22

Looks like misunderstood. Totally agree that senior should share that

1

u/farinasa Jul 04 '22

I apologize for my judgement. Getting a little frustrated in this thread.