3 ms·

This blog perfectly articulates the strife that inspired and drove the DevOps trend. I am always saddened when I hear "our organisation has a DevOps team" - im

by Jenk 5y ago

This blog perfectly articulates the strife that inspired and drove the DevOps trend. I am always saddened when I hear "our organisation has a DevOps team" - immediately this demonstrates the fundamenetal lack of understanding the very premise of what DevOps set out to solve: Bringing Development and Operations together. Even the very name "DevOps" was constructed such to symbolise the combining of the two domains into one. But no. Now we just have a new cool title to throw on people who will be ringfenced just as they were before.

dogleash 5y ago
I'm more and more convinced that "DevOps" (and "Agile" before it) are just buzzwords that can be leveraged to make whatever change the person implementing it wanted to do all along, with zero regard for what the buzzword actually means. If real devops was going to happen, it wouldn't take a brand to sell cross functional collaboration. It would have just been yet another one of the constant stream of incremental improvements we make by folding lessons learned in industry into our own orgs. "DevOps" today is just codified Shadow IT.
mrweasel 5y ago
> Bringing Development and Operations together Yep, because developer might not know what ops needs in terms of traceability, logs and so on, to be able to run their code in production without having to wake them up at 2AM. Similarly Ops knows a lot about what can be done with existing infrastructure, or off the shelf components, which can save a huge amount of work, while providing a more stable system. I do mostly operations now, and I'm lucky enough to work with really talents developers, who care to listen to input, before writing 5000 lines of code. I also work with customers, who have their own developers, with their own weird ideas about the world. The biggest problem I see right now, except for occasions cowboy pretending to be a professional developer, is developer picking technologies without understanding it. We work with customer who picked technologies because they're interesting, not because it's what they need. When performance is terrible it becomes and operations issue and being told "Kafka is not actually a database and should be used as one" often isn't the answer they want. Or try telling a developer that the code he worked on for three months can be done by the existing load balancer in a few hours or that the ORM is actually writing terrible queries. DevOps team, as in: "We use the shared knowledge of both parties" is fantastic, but operations is frequently an afterthought and not involved in the design fase. If we're to take "DevOps" as developers doing operation, I'd prefer that we do the opposite and let operations do development. I think we'd get better results.
- loopz 5y ago
  Not within the confines of agile scrum sprints and multiple attached rituals. Senior sysadmins also would refuse to do the free labour thing.

by Jenk 5y ago

dogleash 5y ago

I'm more and more convinced that "DevOps" (and "Agile" before it) are just buzzwords that can be leveraged to make whatever change the person implementing it wanted to do all along, with zero regard for what the buzzword actually means. If real devops was going to happen, it wouldn't take a brand to sell cross functional collaboration. It would have just been yet another one of the constant stream of incremental improvements we make by folding lessons learned in industry into our own orgs. "DevOps" today is just codified Shadow IT.

mrweasel 5y ago

> Bringing Development and Operations together Yep, because developer might not know what ops needs in terms of traceability, logs and so on, to be able to run their code in production without having to wake them up at 2AM. Similarly Ops knows a lot about what can be done with existing infrastructure, or off the shelf components, which can save a huge amount of work, while providing a more stable system. I do mostly operations now, and I'm lucky enough to work with really talents developers, who care to listen to input, before writing 5000 lines of code. I also work with customers, who have their own developers, with their own weird ideas about the world. The biggest problem I see right now, except for occasions cowboy pretending to be a professional developer, is developer picking technologies without understanding it. We work with customer who picked technologies because they're interesting, not because it's what they need. When performance is terrible it becomes and operations issue and being told "Kafka is not actually a database and should be used as one" often isn't the answer they want. Or try telling a developer that the code he worked on for three months can be done by the existing load balancer in a few hours or that the ORM is actually writing terrible queries. DevOps team, as in: "We use the shared knowledge of both parties" is fantastic, but operations is frequently an afterthought and not involved in the design fase. If we're to take "DevOps" as developers doing operation, I'd prefer that we do the opposite and let operations do development. I think we'd get better results.

loopz 5y ago
Not within the confines of agile scrum sprints and multiple attached rituals. Senior sysadmins also would refuse to do the free labour thing.