Re:DevOps uses a capability model, not a maturity model
by galleywest200 on Thursday April 06, 2023 @08:40AM
(#35467555)
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.
[ Parent
| on HN ]
Re:DevOps uses a capability model, not a maturity model
by toyg on Thursday April 06, 2023 @09:01AM
(#35467772)
> 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
by imwillofficial on Thursday April 06, 2023 @02:57PM
(#35472788)
I like to describe it as "we are the helper elves helping Santa deliver presents"
Re:DevOps uses a capability model, not a maturity model
by Leo_Germond on Friday April 07, 2023 @01:42AM
(#35478448)
That view of the development process is a bit reductive, I'm not sure the dev working on fixing a regression on some crusty, old, ugly, but contractually maintained branch of the product considers itself to be a big shot. But that's where most of the money comes from, so that's where this function has to act. Maintenance caused by unprovoked changes is not the lot of any single person or job in the company, it is in fact probably the most common facet of any tech job.