DevOps uses a capability model, not a maturity model

Re:DevOps uses a capability model, not a maturity model by benjaminwootton on Thursday April 06, 2023 @08:24PM (#35476456)

What do you call the people who:

- Use Terraform to build infrastructure as code

- Get involve in containerising applications

- Run and operate Kubernetes

- Spend a lot of time on CI/CD

- Improve the development experience

- Implement service discovery

- Build and run developer platforms

- (To a lesser extent) Build and run cloud environments including Serverless components

This seems like a new set of responsibilities which don’t fit cleanly into Development or Sys Admin, and are substantial enough such that someone could specialise in this role full time.

I think that DevOps as a job title is one of the best things that ever happened to the industry.

[ Parent | on HN ]

Re:DevOps uses a capability model, not a maturity model by getoffmyyawn on Friday April 07, 2023 @06:28AM (#35480122)

Personally, I call this job role System Engineer.

[ Parent | on HN ]

Re:DevOps uses a capability model, not a maturity model by stevefenton on Tuesday April 11, 2023 @03:15AM (#35521870)

You may like Platform Engineering even more as there's a lot of crossover with what you mention. A key difference from your list is that you enable teams to build and run their own applications, so they remain responsible throughout. You would provide a simpler way for them to do it, so they could self-serve.

[ Parent | on HN ]