Hacker News Reader

Comment by corobo | Hacker News Reader

> both are expected to produce HA, Automated, Well Documented Infrastructure, to allow developers to run their code

Wait have I been using the wrong definition? I thought DevOps were devs that also setup/maintain their own infrastructure

View on HN

Yeah, please stop using that definition immediately. It's incredibly unhelpful, and just encourages management to understaff.

To be fair it does look like that's what it's supposed to mean. It looks like a combination of Dev and Ops, at a glance it should mean it describes a combination of roles too.

I tut at management as much as the next guy but whoever came up with DevOps didn't really help themselves there :)

Well, the full term is Development Operations, meaning the branch of Operations concerned with supporting Development. I recoiled from the definition you offered because I've actually witnessed an organization use that as a justification for not hiring any Operations staff, which is a terrible idea.

That is NoOps, but somewhat depends. You could have a developer who has a dedicated job of managing the infrastructure, but still doing some development work. Also don't forget the build engineer part for automating deploys. But if the responsibility is spread across the team, that is NoOps. It also tends to lead to a tragedy of the commons situation, because no one steps up to do the things that aren't fun.

Reply on news.ycombinator.com