Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

DevOps uses a capability model, not a maturity model

octopus.com

Post reply on HN
Print view View original

31–40 of 115 posts

Re: DevOps uses a capability model, not a maturity model

#31

Post by morelisp »

stevefenton wrote: post #25
a_c wrote: post #14

What is devops here again? Is it the The Phoenix Project one on one extreme or system admin for the cloud on the other extreme?

DevOps part one was just "developers and operations working more closely together". It only really required the managers to update the goals of the two specilizations to remove the conflict (developers are rewarded for delivering more, operations are rewarded for stability). Once the research picked up, they started building out a broader picture of what a DevOps organization did and whether those things made them mo…

Reading this made me ill.

Re: DevOps uses a capability model, not a maturity model

#32

Post by totetsu »

samsquire wrote: post #8

What upsets me about devops work is that everything I do at a client is a lineage of architecture and design that needs to be maintained going forward and it only exists at that client. The lineage of interesting or useful things I do are tied to the client and dies with that client or when I leave. I just think of the thousands of CI/CD systems, build systems, attempts at parallelising builds, impressive optimisatio…

What upsets me about DevOps, is I know ops pretty well, but am not on par with dev, and every job that just needs someone to ops work now wants to quiz me about O(n) before they'll interview. Then I look around at the people who are good at the Dev part and the don't know their way around an os or cloud infra.

Re: DevOps uses a capability model, not a maturity model

#34

Post by toyg »

galleywest200 wrote: post #26
a_c wrote: post #14

What is devops here again? Is it the The Phoenix Project one on one extreme or system admin for the cloud on the other extreme?

It really is nebulous. My title is DevOps. I do a lot of SysAdmin work, but I also work escalated tickets, write automation and integrations, read the flagship code bases when errors occur, I complain about the flagship code bases when bugs occur, and I file JIRA tickets about the flagship code bases when bugs occur -- but I do not write code for the flagship product. I think that is a key.

> but I do not write code for the flagship product. I think that is a key.

Basically you clean up after big-shot devs, got it.

Re: DevOps uses a capability model, not a maturity model

#35

Post by hendry »

samsquire wrote: post #12
hendry wrote: post #9

Earlier quoted context omitted.

Surely Github workflows https://github.com/actions/starter-workflows or Gitlab templates is the culmination of your devops work? Not Kubernetes (?) unless I missed something. The rewarding thing for me is applying this and other sensible defaults like observing iteration speed and driving delivery..

I'm imagining something similar to a 3D wireframe model of networks and systems, with particles that move around between nodes that represent requests or IOPS. Circuit breakers, bottlenecks, IOPs, load shedding, traffic behaviours can all be visualised. I'm not sure how you would represent latency with this visualization but that's also important. It more represents throughput. Can also be used to represent human wor…

Sounds a bit complex, I usually stick to the R.E.D. method for services and from the devops perspective largely iteration speed.

Re: DevOps uses a capability model, not a maturity model

#36

Post by Karellen »

a_c wrote: post #14

What is devops here again? Is it the The Phoenix Project one on one extreme or system admin for the cloud on the other extreme?

As far as I can tell, being in DevOps is like being a SysAdmin, except you write code to automate as much of your job as possible.

...so, exactly like being a SysAdmin.

Re: DevOps uses a capability model, not a maturity model

#37

Post by khochesh_kushat »

stevefenton wrote: post #25
a_c wrote: post #14

What is devops here again? Is it the The Phoenix Project one on one extreme or system admin for the cloud on the other extreme?

DevOps part one was just "developers and operations working more closely together". It only really required the managers to update the goals of the two specilizations to remove the conflict (developers are rewarded for delivering more, operations are rewarded for stability). Once the research picked up, they started building out a broader picture of what a DevOps organization did and whether those things made them mo…

There was a step in the middle there you missed where it was coopted by software vendors to not be about how you collaborate with others, but which tools you use, and has now become essentially meaningless.

Re: DevOps uses a capability model, not a maturity model

#38

Post by indymike »

stevefenton wrote: post #25
a_c wrote: post #14

What is devops here again? Is it the The Phoenix Project one on one extreme or system admin for the cloud on the other extreme?

DevOps part one was just "developers and operations working more closely together". It only really required the managers to update the goals of the two specilizations to remove the conflict (developers are rewarded for delivering more, operations are rewarded for stability). Once the research picked up, they started building out a broader picture of what a DevOps organization did and whether those things made them mo…

Wow, I remember the first exposure I had to the term DevOps was not at all about working closely, it was about replacing admins with code. This made sense at the time because Puppet, Chef, SaltStack and other tools made it seem like you could pull this off...

Re: DevOps uses a capability model, not a maturity model

#39

Post by KrugerDunnings »

Lately I've been made to understand that DevOps or Software Engineering is not for me, capability/maturity models, processes written in anything other then code, or metrics this and that just ism't me. We can argue about the meaning of words all day long but like I said this just isn't me. Some of us just prefer to say close to the metal (as in reality with all its complexity that escapes the precision of words and that is totally ok) and are deeply suspicious of any excessive abstractions. There must be others like me, so I am in search for my tribe, and I want to know what do we call ourself, maybe we don't want to call ourself anything, but where can we meet, who want to hire us, please tell me if you know, Thanks!

Re: DevOps uses a capability model, not a maturity model

#40

Post by Chico75 »

robertlagrant wrote: post #4

This article is highlighting a problem with badly designed maturity models in general. If you have a good maturity model (e.g. for DevOps one based on DORA metrics) then the capabilities needed to arrive at a higher level can be determined per-org. That solves the real problem. I think the article has a fundamental "AB problem" issue.

I would encourage you to read the book "Accelerate" which was at the source of the DORA metrics, as it clearly advocate for a capability model, not a maturity one.
Post reply on HN