2023 DevOps Is Terrible
abidmoon.hashnode.dev
2023 DevOps Is Terrible
1–10 of 126 posts
Re: 2023 DevOps Is Terrible
#2The fact that we have a “devops team” at work infuriates me. It’s enough to distract me me from how “Scrum” has destroyed Agile.
Re: 2023 DevOps Is Terrible
#3The fact that we have a “devops team” at work infuriates me. It’s enough to distract me me from how “Scrum” has destroyed Agile.
What is so horrible about it? Our devs are happy they can focus on fixing unit tests in pycharm, while others care about where the code is going.
Re: 2023 DevOps Is Terrible
#4The creation of DevOps teams instead of SRE / Platform seems pretty common and I think originates from ignorant engineering leaders and poorly defined roles and responsibilities. You want to leverage the expertise of the folks who focus on cloud infrastructure, but you can't move the responsibility of operations away from the application teams without seriously compromising incentives that effect quality, throughput and reliability.
Re: 2023 DevOps Is Terrible
#5The fact that we have a “devops team” at work infuriates me. It’s enough to distract me me from how “Scrum” has destroyed Agile.
I think there is room for a DevOps team if they are focused on creating and maintaining the overall DevOps platform. But if they are taking tickets and setting up pipelines for individual applications, they are doing it wrong.
But a team focused on making a streamlined platform with ready to adopt patterns that already account for compliance and security related concerns, they can spread DevOps adoption more effectively and consistently throughout the organization.
Re: 2023 DevOps Is Terrible
#6Yep, bang on. As for the PE being the “solution” it is incredibly important and sorely needed but it won’t solve your enterprise culture.
Re: 2023 DevOps Is Terrible
#7The creation of DevOps teams instead of SRE / Platform seems pretty common and I think originates from ignorant engineering leaders and poorly defined roles and responsibilities. You want to leverage the expertise of the folks who focus on cloud infrastructure, but you can't move the responsibility of operations away from the application teams without seriously compromising incentives that effect quality, throughput…
Can you expand on what you mean by this? Specifically: "you can't move the responsibility of operations away from the application teams without seriously compromising incentives that effect quality, throughput and reliability"
Re: 2023 DevOps Is Terrible
#8Whats your SRE / DevOps ratio? In my experience, in the 10 teams I had or oversaw, I had about 1 FTE in DevOps for 15 SRE. Of course it depends, but what’s your personal experience?
Re: 2023 DevOps Is Terrible
#9I'm technologically stuck in the era when everyone hated JavaScript. I provision instances with bash and services over REST APIs.
Re: 2023 DevOps Is Terrible
#10The fact that we have a “devops team” at work infuriates me. It’s enough to distract me me from how “Scrum” has destroyed Agile.
What is so horrible about it? Our devs are happy they can focus on fixing unit tests in pycharm, while others care about where the code is going.
Because that is the software developer/systems engineer division that already existed 20 years ago.
The idea behind devops was to be a single team.