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

22

u/Sparcrypt Jul 05 '22

I have never in my life seen people argue over titles as much as I have in this sub.

None of you all have the same jobs and your title does not matter.

1

u/its_all_one_electron Sep 18 '23

(Sorry for super late reply) It matters to me because I'm trying to figure out what the frick title to put on my resume.

2

u/Intelligent-Fix3394 Dec 01 '23

The one in your contract. The title doesn’t matter, list your responsibilities and achievements

1

u/Spyro119 Mar 08 '24

You can always adapt your title to the one in the job description you are sending your resume to. It also increase your chances to pass through filters if they are using any

2

u/its_all_one_electron Mar 08 '24

I ended up putting a combination. Devops engineer/Linux sysadmin. Got me a job now so I'm happy

7

u/Venthe DevOps (Software Developer) Jul 04 '22 edited Jul 04 '22

Sorry, half disagree. Precisely of the reasons that you have stated, DevOps is not a SUBSET; as not all developers are devops and not all operators are devops.

DevOps references - in set terminology, why not - is a [competence] intersection, nothing more nothing less.

3

u/balonmanokarl Jul 04 '22

I agree with you.

If OP says 90% of this sub come from an operations background then tries to distance DevOps with that, the flaws are evident.

It's certainly a large aspect, but DevOps roles are so variable per organisation that such declaritive statements are polarising.

-5

u/[deleted] Jul 04 '22

I think you may need to review what subset means my friend. If DevOps is a subset of Software Engineering, then it implies not all Software Engineers are DevOps.

39

u/Equivalent_Loan_8794 Jul 04 '22

Agreed, to be honest this sub has become quite unenjoyable lately as it’s an unending semantics game in which the OP almost exclusively insists on their semantics while literally asking for clarification of their semantics…

35

u/eggn00dles Jul 04 '22

this is the only technical sub that has a daily identity crisis thread.

17

u/jacurtis Jul 04 '22

Totally agree. I came here to learn from other people solving problems, sharing tools, offering solutions. Instead every post seems to be about the definition of DevOps. And anyone who genuinely asks a question but uses the word DevOps in their post just gets comments filled with how they miss-used the term DevOps.

5

u/stefera Jul 04 '22

I noticed you're mis using the term DevOps.

5

u/[deleted] Jul 04 '22

I noticed you're mis using the term DevOps.

3

u/stefera Jul 05 '22

I noticed you're mis using the term DevOps.

68

u/HonorMyBeetus Jul 04 '22

Not all devops people would qualify as software developers. That guy who writes out the complex deploy script and build runners and helm charts, software developer as well. The guy who knows the AWS UI well and couldn’t write a lambda function to save his life, not a software developer.

21

u/wesborland1234 Jul 04 '22

I think that most people who are proficient with AWS get into CloudFormation and Terraform pretty early on. I doubt there's any true cloud experts that do everything in the UI

3

u/focus_black_sheep Jul 04 '22

Yep and even then cloudformation gets ugly fast so you have to use AWS CDK in typescript. Basically full code at this point for dynamic deployment across accounts and envs

2

u/HonorMyBeetus Jul 04 '22

I’d argue cloud experts are software engineers.

5

u/[deleted] Jul 04 '22

Not if you met some of the schmucks I work with

1

u/papawish Oct 30 '24

I've terraform experts at my job, that don't even know how computers work and couldn't understand a python program if their life depended on it. All they know is AWS services and docs, terraform, ansible, and computer networks. 

15

u/jacurtis Jul 04 '22

That’s true. There are plenty of terrible software engineers too who only know how to do very specific things in one framework that they are hired in and can’t ever stray from that box or small set of tasks they have learned to repeat. When I was a software engineer we had those same people. I see it now in DevOps. We interview DevOps engineers all the time that can execute well-documented runbooks, but don’t really understand what they are doing and couldn’t do it from scratch if they had too. There are good and bad people at all jobs.

-1

u/HonorMyBeetus Jul 04 '22

I would call that a developer, not a software engineer.

3

u/[deleted] Jul 04 '22

I think that's a cloud engineer buddy, I wouldn't class that as DevOps at all.

4

u/focus_black_sheep Jul 04 '22

Really? I think there's a ton of crossover. For example AWS CI/CD is very common. Hell their prof cert is called DevOps for a reason

0

u/[deleted] Jul 04 '22

[deleted]

15

u/[deleted] Jul 04 '22

"I develop in HTML and CSS".

24

u/WorldsWorstSysadmin Jul 04 '22

Any decent ops side person knows how to code too. Does that mean that all the ops teams at AWS supporting the infrastructure and networking behind your "DevOps" tooling are just software engineers too?

I had to walk a mid-level dev through a basic "how to code" moment because their error handling was absolute shit the other day, and rather than adding return data from an API call, they were just trying to blame the ops team so they wouldn't have to do any deep troubleshooting on their shit code. So I took them and their PM through our codebase, pointed out the code in question, then showed them how to add the proper error handling to see the failing return code from the API.

I write a lot of .erb code, bash scripts, python, regex, and a ton of fun awk stuff. I automate a lot of things in a lot of languages.

Ultimately though, I don't develop our product--I maintain our infrastructure across AWS, GCE, and our datacenter deployments.

But based on your definition, I write code quite often. I majored in physics and computer science in college, and am a formally trained software engineer/physicist. Does this mean that my job role is "software engineer" instead of my ops title?

Edit: Embarrassing spelling mistake.

10

u/tamale Jul 05 '22

Yes, you're a type of software engineer.

7

u/[deleted] Jul 05 '22

IMO if you aren't facilitating a "devops" mentality across teams from a leadership role, or aren't automating all the things by writing code, you probably aren't actually doing devops work.

6

u/676f626c7565 Jul 04 '22

really starting to enjoy these semi-daily internecine fights over what DevOps is or isn't. This is absolutely the pedantic content I came here for.

4

u/digisensor Jul 04 '22

This is like the discussion to draw a hard line between Machine Learning and Data Science. Good luck with it.

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.

→ More replies (1)
→ More replies (3)

10

u/unitegondwanaland Manager, Platform Engineering Jul 04 '22

I could be wrong but it feels like you're drawing some hard conclusions on job descriptions alone. Regardless, I think this is somewhat misguided.

I've actually worked as a "Platform Engineer" and if the company has a CTO who knows what they are doing, this job is 100% NOT synonymous with a traditional "DevOps" role. The entire three years I spent in this role was 1) Creating tooling using Python that aided development teams in their day to day. 2) Created/Supported resources in AWS that make up the framework for a given architecture (SSO, AWS ORG, LANDING ZONE, SCP, VPN, TGW, etc). None of my time was spent building out infrastructure for dev teams. That was up to the DevOps Engineers.

The same is said for SRE, if the role was defined correctly, it also is NOT synonymous with DevOps. But again, companies define these roles and they are widely different with similar names and most of them "are doing it wrong" IMHO. As others have said, you are contradictory in your assumptions and incorrect in others so you should put some more thought into this. Also, DevOps is a subset of Engineering, not Software Engineering for obvious reasons.

Good post effort but it was kind of a whiff for me.

0

u/[deleted] Jul 04 '22

[deleted]

5

u/unitegondwanaland Manager, Platform Engineering Jul 04 '22

You clearly didn't read what I just posted. tbh

→ More replies (2)

33

u/crowquilled Jul 04 '22 edited Jul 04 '22

Disagree. This topic comes up often. We like to think we are special, but we have to face that we are not. More often than not our role is to glue tools together to make things work and fix problems that arise along the way. And that is not Software Engineering. Yes, there are exceptions, but it is not the rule. I don’t think it should be that way, but unfortunately it is. I have been in DevOps for quite a few years and I don’t need to convince others that I’m a Software Engineer to feel better. All the gatekeeping and attempts to inflate it our roles in an engineering organization are getting old. Don’t stress about these vain debates about DevOps; keep learning, stay low profile, ride the wave, and enjoy the paycheck.

12

u/IconWorld Jul 04 '22

I generally think that trying to make all software people become systems people as well, and all systems people become software engineers as well makes everyone worse at what they do. These are both huge domains, and the skill sets don't necessarily overlap. Yes, it's good to have a grasp of what the other canp is doing, but few people are going to be good at both.

9

u/Cephalon_Zeash Jul 04 '22

It's much better to promote better teamwork in modern environments.

3

u/rmullig2 Jul 04 '22

All software people don't have to be systems people. This is just a matter of having the systems people use the same tools as the software people. A natural progression staring from manual changing systems to shell scripting to automation tools using DSLs and now finally using full blown programming languages.

2

u/IconWorld Jul 04 '22

Agreed, however there are some managers who hear devops and think that makes us all interchangeable. That doesn't even work well for various types of software engineering yet alone devops.

3

u/focus_black_sheep Jul 04 '22

glue tools together to make things work and fix problems that arise along the way.

This is what modern SWE is. Lol engineers are not writing machine code, they are using pre-built libraries, API's and other libraries that have abstracted all that complexity.

7

u/Rorasaurus_Prime Jul 04 '22 edited Nov 14 '25

bow outgoing wild vanish chief pocket cobweb cow wrench public

This post was mass deleted and anonymized with Redact

0

u/[deleted] Jul 04 '22

[deleted]

5

u/jacurtis Jul 04 '22

Yep I was a software engineer for almost a decade before getting into DevOps and I do the same stuff now that I did then. I use different languages and tools, but it’s the same stuff.

I’m fixing bugs, troubleshooting problems, identifying optimizations, and architecting new systems. These are the same things I did as a software engineer. I actually don’t feel like my job is that much different than before.

I started in backend development and eventually specialized in postGIS data (location data). Now I specialize in infrastructure and pipelines and system automation. So it feels like I’m still a software engineer and just changed specialities.

3

u/focus_black_sheep Jul 04 '22

If you're working with pipelines you can even argue you're also a data engineer. In /r/dataengineering we have this same discussion quite a lot, whether a DE is also considered a SWE. Interesting to see this topic in DevOps

3

u/my-ka Jul 04 '22

You are a web dev within a team practicing devops

→ More replies (1)

6

u/Makelikeatree_01 Jul 04 '22

So are we saying coding == programming?

0

u/[deleted] Jul 04 '22

[deleted]

5

u/khobbits Systems Infrastructure Engineer Jul 04 '22

Hmm, I have previously said that it's easy to learn how to code, it's much harder to do software engineering.

I'd normally suggest that learning how to script is a good first step, but there is a whole load of theory and methodology required to elevate that to software engineering.

1

u/focus_black_sheep Jul 04 '22

It's easy to learn primitive code, however Data Structures, Algorithms, Optimizations, Multi-threading, Databases, Development paradigms like TDD, CI/CD take much longer to learn -- and you need this to be a well-rounded software engineer.
EDIT: replied to the wrong person, ah oh well leaving it up

3

u/lfionxkshine Jul 04 '22

You can call me the ice cream man for all I care. Long as I have the specific skills you want and you're willing to pay me a shit ton of money to leverage them

3

u/Short_Anywhere_9569 Jul 04 '22

But isn’t devops just set of best practices ?

4

u/Fatality Jul 04 '22

It's Agile 2.0

1

u/victorj405 Jul 30 '22

Your probably wrong and right at the same time.

3

u/sabat Jul 05 '22

Sorry, but "devops" is still not a real job title. Sure, they try to use it as one, but it's meaningless. Usually what they mean is "automation engineer" or SRE or something along those lines. But calling that "devops" means nothing.

1

u/victorj405 Jul 30 '22

My HR team would disagree.

33

u/serverhorror I'm the bit flip you didn't expect! Jul 04 '22

Actually DevOps is a superset of Software Development

29

u/drewsiferr Jul 04 '22

That would imply that writing video game physics engines and vpu firmware code are DevOps tasks, which doesn't track with the DevOps-as-a-role being discussed. You could make the argument that they are overlapping sets, as ops isn't traditionally the domain of software engineers.

The practice of having developers deploy and run things has happened forever in startup environments, though I grant that people in startups have to wear many hats, and that doesn't necessarily make those tasks software engineering ones.

10

u/jacurtis Jul 04 '22

Most software engineers don’t know video game physics or vpu firmware codes either. I would call those specialities within software engineering.

By that logic you could classify DevOps (and it’s various synonyms) as a specialty within software engineering. Just like how integrated systems engineers or video game engineers are also specialities within software engineering.

Just to carry out the point. Not all doctors know how to perform spinal surgery. Spinal Surgeons don’t know how to perform open heart surgery. But they are all doctors. Just different specialties.

17

u/drewsiferr Jul 04 '22

Yes, this is exactly OPs point.

6

u/farinasa Jul 04 '22

All software development has associated ops tasks. All code needs to be executed at the very minimum. Ops and development both fall under DevOps.

→ More replies (11)

1

u/farinasa Jul 04 '22

necessarily make those tasks software engineering ones.

You're right, it makes them DevOps tasks. All development tasks and operations tasks fall under DevOps. It's in the name.

9

u/my-ka Jul 04 '22

Nope An overlapping set between dev and ops

3

u/farinasa Jul 04 '22

A superset containing both dev and ops.

2

u/my-ka Jul 04 '22

One person cannot do both 100% 50 to 50 in each means juniour to middle level After that said, what a company needs and how much does it pay

3

u/farinasa Jul 04 '22

I mean... We do at our company soooo...

Once the tools are set up, it really isn't that difficult.

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.

→ More replies (5)

4

u/assofohdz DevOps Jul 04 '22

This is more true than the original post

0

u/[deleted] Jul 04 '22

[deleted]

3

u/farinasa Jul 04 '22

The definition of DevOps changed? When?

→ More replies (4)

2

u/strcrssd Jul 04 '22

Yes to all of those. Devops is the merging of operations of software systems and authoring of software systems. As such, all of those things, which are authoring software systems, are part of devops.

An integrated view of how software is written and how its operated is all that is required.

2

u/focus_black_sheep Jul 04 '22

I would disagree that SWE is under devops. Other way around, just like how Web dev, data engineering is all under SWE

→ More replies (3)

5

u/1544756405 SRE Jul 04 '22

"What's better, a vehicle or a truck??"

Truck.

12

u/0x7374657665 Jul 04 '22 edited Jul 04 '22

I was an application developer for several years and now I'm a DevOps engineer. DevOps is only software engineering if you think yaml is a programming language.

11

u/jacurtis Jul 04 '22 edited Jul 04 '22

That’s probably unique to your job if you never leave yaml.

I write Go, Python, and bash nearly every day. I ship fresh code multiple times a week and contribute to multiple software projects a day.

It really depends on the job. I interviewed for a job once where I could tell that’s all the job was going to be and I decided not to take it. So there are different jobs and companies that have different responsibilities. If you’re happy just writing yaml and doing configuration all day then that’s no problem. There are DevOps jobs that offer that (mostly lower to mid level roles at very large companies).

By contrast if you want to write code, there are plenty of DevOps roles that allow you to write code daily and spend 80% of your time in an IDE. It just depends on the company and how they define the role. These are good questions to ask during an interview to see if the job is what you’re looking for. Because I’ll admit there is a huge gamut of responsibilities across DevOps jobs. Some are configuration focused (what it sounds like you are) and others are heavily scripting and code focused (where I am now). If you want to write more code, you can find it out there.

18

u/ra_men Jul 04 '22

If your only using yaml then something is wrong with your DevOps culture lol.

12

u/ServerMonky Jul 04 '22

Eh, I'm devops, and I write and maintain python, go, bash and PowerShell apps on a daily basis. I've also written a custom docker registry for a special case we needed, as well as maintain complex ci deployment processes for a variety of erm systems we test our products against.

Although I do write yaml too, but it is usually automated at this point.

5

u/Rorasaurus_Prime Jul 04 '22 edited Nov 14 '25

existence historical workable mountainous nose vegetable history scale full reminiscent

This post was mass deleted and anonymized with Redact

0

u/0x7374657665 Jul 04 '22

The difference is that big custom python scripts are an antipattern to be avoided. The devops ethos (which I am admittedly new to) seems to be to keep everything as vanilla and out-of-the-box as possible because every line of custom code has to be maintained and documented and moves your cattle closer to becoming pets.

3

u/Obsidian743 Jul 04 '22

LOL, exactly. Even the best dev ops engineers may know a little Python, but everything else is largely scripting and plumbing.

4

u/silkhammer Jul 04 '22

Only disagreement is that management missed the boat. (Gasp!!! 😀😂). Management had no idea what either devops or sw engineers are. They just have been telling their hr hire one damn quick. Which generates “demand”. Which starts a trend. Etc. someone writes an article that c-levels fall in love with (or coincidentally have a thriving success after “implementing”) and suddenly its The Thing. After 3 decades in IT I call it The Thing Of the Moment. And go back to optimizing improving and create a new magnet with the buzzwords of today place it in front of my name and carry on providing the IT environment I’m in the best I’ve got. Just my $9.02 😀 happy 4th all in the US.

4

u/mrlazyboy Jul 04 '22

I beg to disagree.

When you say “X is a subset of Y”, you are implying an “IS-A” relationship (e.g., inheritance). This means that a DevOps Engineer inherits all base Software Engineering skills, and then extends them via specialization. Colloquially, it means a DevOps Engineer must be a SWE. You also state this explicitly in your post - a DevOps Engineers is a Software Engineer that focuses on automation, infrastructure, and internal tooling.

(Note that subset means something subtly different for set theory)

What this also implies is that Software Engineering is a prerequisite for DevOps.

Next, since we have all at least taken one or two CS classes (and probably more), I’m hoping we’ve all done proofs. There are many proof techniques, for example NP reductions were the bane of my existence for a long time. Another technique is “proof by counter example.” If anyone here has taken a ton of math classes, you’ll probably say “proof by counter example” isn’t actually a proof technique.

You are correct, but in CS we use it as a technique :)

Anyway

Theorem: DevOps is a subset of SWE

Statement: subset implies an “IS-A” relationship, so DevOps Engineers must be SWEs

Proof: I’ve hired many DevOps Engineers who have never been Software Engineers

QED

Less technically, DevOps Engineers and Software Engineers do completely different things. The main similarity is they both use keyboards. Also realize DevOps is quickly becoming DevSecOps.

Source: built a DevOps consulting company that has completed 300+ projects for 200+ clients domestically and abroad, across pretty much every business sector.

0

u/[deleted] Jul 04 '22

[deleted]

3

u/mrlazyboy Jul 04 '22

Why don’t you tell me about SLSA, ZT, and SBOM?

0

u/[deleted] Jul 04 '22

[deleted]

3

u/mrlazyboy Jul 04 '22

Correct in general; however, in this specific instance, OP is using SWE as a catch all.

If you were to enumerate the actual skills encapsulated in “SWE” as defined by OP, it would be “ability to use a keyboard to solve problems.” With a single defined skill, a subset makes them effectively equivalent and an “IS-A” relationship is warranted.

Regardless, my point still stands. There are plenty of DevOps Engineers who are simply not SWEs. They don’t have formal/informal SWE training/education. They don’t know a single programming language. They’ve never written an algorithm or used a data structure. They’ve never heard of asymptotic runtime. The only “code” they’ve written is YAML or JSON. They don’t know what loops, switch case statements, or conditionals are.

SWEs often make great DevOps engineers because they can solve challenging problems. In some cases, DevOps Engineers 100% do SWE work (especially when it comes to tool integration, or creating new capabilities). But in many cases, they don’t do anything even remotely related to SWE other than using a keyboard.

10

u/Rorasaurus_Prime Jul 04 '22 edited Nov 14 '25

fall existence paint screw knee lock stupendous nail jeans workable

This post was mass deleted and anonymized with Redact

4

u/jacurtis Jul 04 '22

You nailed it on the head. People are focusing on what DevOps was supposed to be or what it maybe used to be. But what it has become is simply a specialization within software engineering.

I go to work and write code to fix problems, correct bugs, and design new systems. My job hasn’t really changed from when I was a software engineer. I’m just using different languages and tools than before. But that’s true across many different veins of software engineering.

0

u/my-ka Jul 04 '22

So much true.

Lets advocate that. He answer to all these topics how do i become devops (and get more money)

Should be

Chose a speciality. Start practicing devops

0

u/[deleted] Jul 04 '22

[deleted]

8

u/PartemConsilio Jul 04 '22

I think the sticky part is what KIND of coding people say is essential. I can write stuff for Pulumi in Python. I script largely in bash and python. I also write a lot of yamls. Am I not coding? If not, I’m doing just fine. Sure, I am intent on learning more coding but it’s not my passion.

1

u/ThroawayPartyer Jul 06 '22

Python is 100% a programming language. With Bash it's perhaps arguable whether it's "just" a scripting language.

6

u/Rorasaurus_Prime Jul 04 '22 edited Nov 14 '25

touch cable water school rob ad hoc cows pen caption abounding

This post was mass deleted and anonymized with Redact

10

u/--Thunder DevOps Jul 04 '22 edited Jul 04 '22

The only thing that triggers me - Developers think they can literally plug themselves up to any profile.

They want to create an environment where Ops are meaningless & they can eat their jobs just like they did with QA. That’s the whole gameplan they are trying to push down our throats 🤏🐈‍⬛

FYI -

6

u/dontcomeback82 Jul 04 '22

developers being able to do more things on their own is the goal, not the enemy.

3

u/--Thunder DevOps Jul 04 '22

Totally, But please be gentle to respect every other engineers goals, Not just a developers.

0

u/modern_medicine_isnt Jul 04 '22

In my experience you have the wrong source. All the devs I would rather have qa people and such. It's management that wants one person who does all (but doesn't want to pay for it).

2

u/--Thunder DevOps Jul 04 '22

I don’t see any management here.

0

u/[deleted] Jul 04 '22

[deleted]

8

u/--Thunder DevOps Jul 04 '22 edited Jul 04 '22

I don’t have a problem being a dev, devops, sre or it can be any name, The problem comes up when certain individuals and then the whole community acts as if they can do our job very easily.

I like education to challenge US, So that we can learn new stuff, Not people claiming us that in order to be a DevOps, You should learn to code.

0

u/[deleted] Jul 04 '22

[deleted]

5

u/guterz Jul 04 '22

I don’t particularly believe this. There are DevOps Engineers who can write Terraform, Helm charts, Ansible, Bash scripts, etc but can’t write a line of Python who are highly successful in DevOps.

0

u/[deleted] Jul 04 '22

[deleted]

0

u/[deleted] Jul 04 '22

[deleted]

2

u/--Thunder DevOps Jul 04 '22

🙏🏼

2

u/EiKall Jul 04 '22

The topic of job role naming reminds me a lot of the general issue of naming stuff

The choice of naming conventions can be an enormously controversial issue, with partisans of each holding theirs to be the best and others to be inferior.

From: https://en.m.wikipedia.org/wiki/Naming_convention_(programming)

2

u/komarEX CTO Jul 04 '22

I've been to certain conference lately where BMW folks showed their idea of how DevOps should be and named it "Full Stack DevOps"... I was literally mind blown. I won't describe it here because I don't really want to put more oil onto fire. DevOps definitions are already totally messed up and big companies like BWM are making it even more idiotic.

2

u/No_Impression_2077 Jul 04 '22

DevOps is dead.

2

u/[deleted] Jul 04 '22

Dev in DevOps is short for Developer and Developer is a non formal name of Software Engineer

2

u/snarkhunter Lead DevOps Engineer Jul 04 '22

I get the feeling like when people are making that distinction they mean "software engineers" are people on product teams that are building stuff to be sold to external customers, and "devops" means people on teams that are building tools for those product teams. And that's a fine and valid way to structure things in lots of situations. And given that each team is using different bits of technology to do what they're doing, I get it. But they're both engineering software.

2

u/Obsidian743 Jul 04 '22

Idk, most dev ops engineers I know couldn't write functional code. Yes it's adjacent but the degree to which a functional SWE can do dev ops work compared to the other way around is completely different.

2

u/KikaCodes Jul 04 '22

Yes, DevOps in general has become a buzzword and companies/people have started using it without really understanding it. But it occurs to me that you're doing the exact same thing with Site Reliability Engineer. SRE is a completely different role to DevOps, and by putting it in this list implies that you don't really understand it at all.

2

u/ioah86 Jul 04 '22

Way to start a heated discussion ;-)

I actually do think DevOps is just something so misused at times that it actually has an identity crisis.

IMO it comes from the fact that, for the longest time, IT and Engineering were two different departments, and two different skill sets were needed. Then cloud came around, and Engineers were doing also IT related tasks, with some security-wise disastrous outcomes. Since modern software development is more and more tied to infrastructure, and we can define the latter as code, I feel like the two areas are merging, and the movement behind it is called DevOps. I would hence agree with subsetting it, but also say: They are the same. You can't call yourself a modern developer nowadays anymore without having some infrastructure knowledge.

2

u/westontechfoundation Jul 04 '22

Well said! It’s not the same landscape as it was 3 years ago. Things can shift in months now not years which opens up so much more opportunity.

2

u/Fatality Jul 04 '22

Not even close, unless you think "Agile Engineer" is a job title.

2

u/hamlet_d Jul 05 '22

The only issue is that many folks who have come from operations were already doing many of these things and aren't software engineers by training. Sure on a pure definition basis maybe it is software engineering, but someone said said you'll be someone who:

focuses on infrastructure, automation and internal tooling.

...many operations folks will say "Yeah, that's what I do." That's why it's called devops. It's often along the lines of leveraging software engineering practices in operations. The core of what is being done has always been an operations task.

In other words, it's not just "it's this not that" it's more "it's this AND that"

1

u/sabat Jul 05 '22

All fine and good, but that's not all devops means. The idea is: no more silos. No more "I'm a sysadmin, not a developer, so don't talk to me about stack traces" or "I'm a DBA, don't ask me about code".

2

u/mini_market Jul 05 '22

You and I do not decide the definition. Hiring organizations and managers decide. Each corporate culture has defined DevOps their way with some overlap between organizations. Read the job title and description to understand what the organization means in their context.

2

u/[deleted] Jul 05 '22

Bingo !

2

u/elitesense Jul 05 '22

Get over it. Collect paycheck and call up an old friend for a beer. Stop worrying about shit like this. If the role wants you to integrate with dev team, great. If the role wants you separated, great. That's it. Don't stress over labels.... Just get the job done and get paid. End it there

2

u/tshrex Jul 05 '22

Haha no. Developers can't be trusted with production.

2

u/temotodochi Cloud Engineer Jul 05 '22 edited Jul 05 '22

I disagree a bit, but i've seen this quite often in the past 10 years that the OPS part is completely forgotten.

You think that software defined infrastructure is the operations part and that's where you fail. You'll likely end up in those news articles which describe how many tens of thousands of exposed kubernetes clusters there are on the net.

Devops =! software development, it's handling the whole process of software and service production with people from multiple diciplines working in tandem.

I do devops for a living, i design and run environments and systems which serve millions of people. still i'm not a programmer and never will be.

Bit of a problem for me personally, because most recruiters contact for a programming job and have no clue when i tell them that i'd rather build that cloud platform you use than program something running on it.

3

u/Srr013 Jul 04 '22

My team recently hired an SD who would primarily focus on cloud infrastructure. We don’t have a need for 40h/week of cloud work yet, so the SD will also work on the application code.

Is it a DevOps role? Yes. Is it a SD role? Yes. In this case the individual we hired was more interested in the SD career path so we gave them an SD title.

3

u/lazyant Jul 04 '22

“DevOps” doesn’t have a one definition accepted by everybody; different people use it differently. If we go by job posts descriptions and what people with devops titles do, it’s mostly automating builds and infrastructure. If you go to a devops conference, most of the people come from ops and sysadmin. So even if in theory devops is software engineering, in practice it’s mostly a modern way of doing sysadmin.

3

u/farinasa Jul 04 '22

The theory of DevOps is that dev and ops are not separate. DevOps is a superset of both dev and ops. This is the entire idea of DevOps. There is no difference between task type, all dev and ops tasks fall under DevOps.

3

u/[deleted] Jul 04 '22

You can add operations engineer to that list as well! I think the job titles in this space can vary so much from company to company because everyone is figuring this stuff out as they go along

I generally look at job specs for DevOps engineers with concern, if a company is hiring a DevOps engineer, they're probably not doing DevOps because it shouldn't be a role in itself, it's a practice that everyone in the company should follow, otherwise you're still throwing things over the fence and expecting another team to look after it

3

u/lightwhite Jul 04 '22

There is no subset in Engineering. It is defined and scoped. The modern HR and recruitment jargon bs is leaking into our practices. And that worries me in a certain way. You have a school and you are an engineer of it.

DevOps is a mindset. It’s a martial art with a unique discipline. The term is abused/misused so often that it has become even worse to explain people what a DevOps dude does for living

DevOps Engineering is in fact its own field, like MMA or Jeet Kune Do is in Martial arts in reference of IT. Not everyone can be a DevOps Engineer (Master) but everyone can practice the art and science (practitioner). Job listings ask for people to build pipelines and manage infra and fix monitoring. Because this is a basis practice in DevOps, everyone thinks that they need a DevOps engineer. However that’s not true.

In my book, you are not a DevOps engineer if you don’t know how the stuff works devs your devs are creating. How can you automate workflow if you don’t know how the team is comprised and how the product functions? You build it, you run it, you support it.

A true senior DevOps engineer is someone:

  • who slaps common sense into the heads of Software/Enterprise Architects, can (re-)educate everyone in their team,

  • is a good teacher/mentor,

  • will take pager duty so that the poor sysadmin can sleep at least this night in peace and make sure he doesn’t have to wake up for that issue ever again by solving the root cause,

  • will not allow anyone to push to production before they know what they are doing,

  • is someone who can jump right in and pick up any task from the board and do it alone or in collaboration,

  • is the guy whom will ditch the team to farm chicken when he feels like it, just because he can.

Context is important. You can be a developer without an engineering degree. But you cannot be an engineer without the proper degree, but yet also be a developer. “Engineer” is a title, just like Doctor. It is the proof of one’s capability of practicing the art and science of a given field of expertise. Those who call themselves DevOps/SR/Software engineers without a degree of engineering are technically no engineers. Here is the definition of engineering:

noun noun: engineering

  1. the branch of science and technology concerned with the design, building, and use of engines, machines, and structures. a field of study or activity concerned with modification or development in a particular area. i.e. "software engineering"

  2. the action of working artfully to bring something about. "if not for his shrewd engineering, the election would have been lost"

Software Engineer is absolutely not meaningless at all. If you think it is, I would suggest you reflect upon what you think about it and not talk about things that you have no idea or inform yourself better before representing it as a fact. Your opinion is your, and all power to you, but you are wrong. There is nothing we can do to change that fact.

Recruiters turned the jargon into such a travesty that people started to call themselves the engineer of X that pays the most.

Only 1% of denizens here know what “Engineer” means. People don’t understand the limitations of Software/Hardware Developers in comparison to Engineers.

I feel like its time to exit this industry because it is getting toxic and a lot of people are trying to come for the gold rush.

2

u/googlemehard Jul 04 '22

I think software engineering can just be split into two groups. Do you write code or do you not write code.

0

u/[deleted] Jul 04 '22

[deleted]

1

u/googlemehard Jul 04 '22

My point exactly, if you program you are a software engineer, everything else is meaningless fragmentation.

2

u/TheWaraba Jul 04 '22

I disagree, but I’ve never had a DevOps job or title, nor worked as a Software Engineer.

2

u/0qxtXwugj2m8 Jul 04 '22

Tell that to sys admins that are afraid to code

13

u/SuperQue Jul 04 '22

Sysadmins afraid to code don't make for very good DevOps.

6

u/justinsst Jul 04 '22

They don’t make for very good sysadmins either. I’m a junior sys admin in a small company (like 100 users) and I use Python and Powershell often. If you can’t write a well written Python or Powershell script as a sys admin in 2022 you’re in trouble lol.

3

u/jacurtis Jul 04 '22

It’s true. But that doesn’t stop them for applying for the DevOps roles anyway. I see those resumes daily come across my desk. Well over half the resumes I see are sysadmjns with zero coding or scripting experience. We tried to hire one of those once because we thought it could balance out our team and it was a disaster. The person was great but they just got way too overwhelmed with all the code being pushed around the team and they ended up resigning After two months to go after a job that didn’t require coding.

Now I immediately disqualify any applicant without coding experience.

1

u/Rorasaurus_Prime Jul 04 '22 edited Nov 14 '25

school merciful juggle roll towering chop racial alleged relieved treatment

This post was mass deleted and anonymized with Redact

2

u/admiralspark Jul 04 '22

I think it's funny that IT people evolved to the point where DevOps is a complete career change for them.

Writing code, building automation and deploying projects was a core part of IT in the 90s, but the push-button windows admin's of the 2000's kinda lost sight of it.

1

u/[deleted] Jul 04 '22

Now if that is true the the term infrsructure as code is valid. I still keep writing. New server new server. New server. Nothing appears. I must be doing it wrong. Magic terra form wand, Levioserver. With a twist and a flick. Nope no server

1

u/wdroz Jul 04 '22

IMO, all SWE should know basic devops, basic cyber security, basic networking (and many mores). Devs that are totally unaware of these tend to make stupid mistakes.

1

u/midzom Jul 04 '22

This is an excellent post. Thank you for letting writing it.

I think something that must be said too is that the DevOps concepts and tooling came for operations first because operations had the most room to grow. I personally think it’s almost certain that as the clouds grow and their tooling matures it’s almost certain that developers will begin writing less code and focusing more on serverless development in most cases. That transition hasn’t come in full force yet. I’ve seen larger businesses making that transition and seeing some success in it.

I think what we all need to remember irrespective of what side of the house we are in is technology for technology’s sake isn’t the right at to go. Our job is to deliver to market faster with fewer issues in a way that is scalable, reliable, and secure. That includes the development process also and the code that the development teams are creating.

1

u/[deleted] Jul 04 '22

YES!! I always tell people that DevOps is a specialization in the same way that being a Java developer or a .Net developer is

1

u/Carvtographer System Engineer Jul 04 '22

I know very little people who just manage clicking on web dashboard front ends and know nothing about SWE.

1

u/HamPlayz247 Jul 04 '22

Is a build engineer also devops?

1

u/[deleted] Jul 04 '22

I always felt like System Admins think they can do DevOps and Devs always think they can do (or prefer to do) their own DevOps for much the same reason.

DevOps is like the Rodney Dangerfield of Software Engineering. It gets no respect.

1

u/Bogatyrs Jul 05 '22

Well said. I'm a senior software engineer working on Infrastructure and DevOps, that's how I would describe it.

1

u/z-null Jul 05 '22

That's because, at least in my circles, ops became devops, which is just expanded ops. Why? Because the vast, vast, vast majority of SE/CS graduates (at least the ones I met) have literally zero interest in HW or operations of any kind and only want to develop. Not much mystery there.

1

u/scalable_idiot Jul 05 '22

One of the best posts I've ever seen on this sub. Kudos OP. Bridge the gap, don't burn bridges!

1

u/greetex Jul 05 '22

Thank so much for posting this it needed to be said !

1

u/[deleted] Jul 05 '22

In my experience -> modern Senior DevOps Engineer is able to cover all of those roles here:

Platform Engineer

Cloud Engineer

Infrastructure Engineer

Systems Engineer

Site Reliability Engineer

On top of that I would also put "Security Engineer", but thats something you master late late into the party.

1

u/trailstrider Jul 20 '22

And don’t forget the DevSecOps mutation. Dev and Ops… Ops already should include security… I get the need for SecOps in some groups, where security was poorly handled for so long; but, Ops/Security need to be integrated. On the other hand, arguing against myself, there is a lot to be said for understanding how to make something new secure. But the Ops team should be bringing the expertise to facilitate that process related work as well.

Y’all can organize how ya want though. There really isn’t a single silver bullet organization structure. As the OP said, it’s about the philosophy; and, I’d further state it is the associated mentality that drives behavior and sane process adherence called for by said philosophy. Leadership and organizational structures to achieve this are many and varied.

1

u/Oddomar Aug 01 '22

My title says Deployment Engineer at my job , and I work as 3rd party vendor on AT&T infrastructure they call me a Systems Engineer. Then when my coworkers leave to another company they are SRE's or Infrastructure Engineer's. So yea it's all the same shit at end of the day it depends on what are your responsibilities in that group based on your skill set and experience.

1

u/[deleted] Jan 30 '23

I prefer the title of programmer. Seems to be more inclusive

1

u/jacobs-tech-tavern Jan 16 '24

It’s a very big enterprise thing to pretend they’re different roles rather than a sub-specialisation

1

u/rokiller Feb 10 '24

DevOps as a culture is the way to go. Engineering teams should be responsible for their own infrastructure

0

u/my-ka Jul 04 '22

You missed DBA and automation qa

0

u/[deleted] Jul 04 '22

So, a developer who writes software products, doesn't need to also write software to run his own software? Tbh I always understood DevOps as "we don't have budget for both, so one person needs to do 2 jobs". At least at my job, if you can DevOps, means you are mediocre at both individually, otherwise you would be assigned to one of those and have fulltime work on it, without having any time left to manage the other.

0

u/mazznac Jul 04 '22

So all you software engineers fellas are cool with allocating cidr blocks for service vs pod networks, applying network policies, monitoring vuln scans on your built artifacts and patching them properly etc?

1

u/focus_black_sheep Jul 04 '22

I mean there's a ton of specializations in SWE field. No one is going to know every single one. Very few can write machine code from scratch doesn't mean they are not a SWE

0

u/[deleted] Jul 04 '22

In certain countries, an engineer is a protected title with a professional order. In Canada for example, if you do a software engineering degree, it is essentially an engineering degree with all the math, physics and chemistry courses that are common across all engineering degrees, whether it is construction, electrical or otherwise. Only after completing such a degree can you join the professional order of engineers of your province. You can only sign your name with "p.eng" if you are a member of that order and pay your yearly fees.

However, you don't have to be a software engineer to be a DevOps, or even a developer. You can do a normal computer science university degree as well. But software engineering is very specific and focuses a lot on software quality assurance throughout the lifecycle of the project from the requirements to the delivery with strict norms.

0

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

Those in the U.S. without a degree from an ABET accredited program, or those who are not a Civil/Construction engineer who got their P. E. in one of the few states you can sit for the exam without a degree, should not call themselves an engineer. Note there are 42 accredited software engineering programs, but this is a somewhat recent change as more CS departments have integrated into engineering departments or changed their curriculum.

This may be seem like semantics, but it's not. I'm not implying those without engineering degrees, or any degree at all, are any less compotent than those with engineering degrees. You're just going to be judged for misrepresenting yourself by some. While in your job search, be cognizant of what these positions may be labeled, but when it comes to your title, names that should be used would include:

  • Software developer

  • Embedded systems engineering technician

  • Data engineering technician

  • Machine learning engineering technician

  • Virtual reality engineering technician

  • DevOps engineering technician

  • Cloud engineering technician

  • Infrastructure engineering technician

  • Systems engineering technician

  • Site reliability engineering technician

  • Computer scientist

  • Computer programmer

  • Web developer

  • Mobile developer

  • Game devloper

  • Software technician

  • System administrator

  • Computer operator

  • Systems technician

  • Networking engineering technician

  • Database engineering technician

  • Project engineering technician

  • Platform engineering technician

  • Systems architect

*Can interchange technician, associate, specialist, architect, designer, and technologist. Also can remove engineering from the title. Finally can prepend with junior, senior, staff, lead, principal, etc.

0

u/[deleted] Jul 04 '22

[deleted]

→ More replies (2)

-2

u/Dealoite Jul 04 '22

Well said. Totally agree. It's all just software engineering at the end of the day, especially as writing code becomes more integral to DevOps.

-1

u/Warkred Jul 04 '22

You came here to show-off right? Comparing devops and software engineers is as relevant as comparing fruits and meat. They can be eaten but that's it.

-1

u/iamanenglishmuffin Jul 04 '22

Did any of you actually go to an engineering school?

0

u/haikusbot Jul 04 '22

Did any of you

Actually go to an

Engineering school?

- iamanenglishmuffin


I detect haikus. And sometimes, successfully. Learn more about me.

Opt out of replies: "haikusbot opt out" | Delete my comment: "haikusbot delete"

-1

u/Obsidian743 Jul 04 '22

I'm sorry, but if most of your job's tasks can be looked up via Google or Stackoverflow, it's not the same as having to invent a series of algorithms to accomplish various specific business needs. No dev ops engineer is sitting in all day meetings trying to flesh out requirements while toiling over architecture and sequence diagrams to be implemented (at least, they're not really paying attention if they're even present).

4

u/[deleted] Jul 04 '22

Software engineers don't do that either. Source: am software engineer

4

u/focus_black_sheep Jul 04 '22

invent a series of algorithms to accomplish various specific business needs.

inventing algorithms..? Well this disqualified 99% of all SWE's including most at FAANG.
maybe some PHd Comp Sci researchers at Google are working on new algorithms but not your average or even most SWE's

→ More replies (1)

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.

2

u/my-ka Jul 04 '22

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

0

u/[deleted] Jul 04 '22

[deleted]

→ More replies (19)
→ More replies (3)

0

u/[deleted] Jul 04 '22

[deleted]

35

u/jacurtis Jul 04 '22

This is exactly what I say. When you meet someone at a party or you’re making brief introductions with someone new and they ask what you do, I usually just say “I’m a software engineer”. If they seem technical enough or are curious enough then I’m happy to dig deeper and get into my SRE/DevOps role. But for 90% of interactions I just leave it at being a software engineer and it tells people enough about what I do to get the picture.

→ More replies (1)

11

u/Caffeine_Monster Jul 05 '22 edited Jul 05 '22

If they ask what I do daily, I tell them

"I write software to make sure all the systems are up and running efficiently"

Well I'm a professional button pusher. If I push buttons in the right order so other people have to push less buttons.

Software engineering is a subset of my field.

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?

→ More replies (1)
→ More replies (9)

6

u/chanud Jul 04 '22

Same, or sometimes I say: I work with computers, because if I say that I'm a DevOps Engineer they will ask: wut, what is that? And then you have to explain

4

u/d_maes Jul 05 '22

I also specify that I work with big (Linux) servers, so people don't come asking to fix their pc/printer/wifi.

8

u/wenttoofar Jul 04 '22

100% agree. What OP and you said is real DevOps. What I hate is people getting into an “entry level” DevOps position such as “release engineer” and they do’t even know basic nix commands. It requires years of experience as an ops and/or dev to be true DevOps.

2

u/[deleted] Jul 04 '22

Yeah very similar for me. Software Engineer first, but I tell people that I build and work on tools that other developers use and rely on.

2

u/focus_black_sheep Jul 04 '22

Same. I'm a data engineer but still a swe describe it fine

2

u/MAXIMUS-1 Jul 04 '22

I would fine Infrastructure engineer to be a but more accurate.

0

u/[deleted] Jul 04 '22

[deleted]

4

u/djk29a_ Jul 04 '22

Always depends upon what we consider "code." The same problem that's happened in any part of software engineering. The fact people are doing purity tests almost ensures it's a subset of software engineering given the elitist culture that pervades it.

0

u/[deleted] Jul 04 '22

[deleted]

5

u/Dealoite Jul 04 '22

I suppose maybe because it's the most popular / easiest to get into / in-demand ?

That, and HR being clueless as usual

→ More replies (1)