Hacker News Reader

Comment by unit_circle | Hacker News Reader

First of all: If you have the title of "DevOps" what you're doing is "Operations", you aren't practicing DevOps.

Anyway, this company has had incident after incident. This will keep happening every few years for them like it has for the past 10. As will lack of transparency/ outright lying.

Some commenters are saying they wish the company the best. I don't. Use something else. LastPass needs to die.

View on HN

> First of all: If you have the title of "DevOps" what you're doing is "Operations", you aren't practicing DevOps.

So what title do you need to have to practice DevOps?

"DevOps enables coordination and collaboration between formerly siloed roles like development, IT operations, quality engineering, and security." - https://learn.microsoft.com/en-us/devops/what-is-devops

It's not a job title, it's an engineering practice. People who participate in DevOps include "software engineer", "network engineer", "IT operations engineer", "platform engineer", "cloud engineer", "quality engineer", "security engineer", "manager", etc.

I'm also one of the people who does "operations" but has a DevOps job title. I've grown to accept this as a second definition, it's quite common now.

I do not like the title either, but I do understand the motivation of taking all those "non-software engineering", technical roles and putting them under the same umbrella, due to a lack for a better title, because a company might not afford to have separate roles for each of those areas you have listed above.

"OPERATIONS ENGINEER" might work, but it raises another set of problems, e.g. does it imply operational responsibility (on-duty) work, which I don't think is a given in DevOps jobs nowadays.

What's wrong with system administrator? IT specialist? Cloud engineer? Reliability expert?

There are many options that don't tack "dev" into your non-dev job titles.

Did you even read my comment? None of your provided alternatives solve the issue of the current market being in demand of such a wide set of skills outside of the "normal software development" practice (whatever that even is), that labeling all of those under whatever title will get some people butthurt.

If its a matter of gatekeeping the "developer" status, go read some actual job posts with the title DevOps in them. Its not uncommon to come across proficiency requirements in at least one programming language (e.g. Go/Python/Rust), used in automation libraries, cli tools or whatever, which the applicants are expected to "develop". Or is it just constructions that can be developed?

If you start on that tone, you get what you ask for. I will obviously not read this comment.

Something according to "You build it, you run it".

Reply on news.ycombinator.com