Comment by mancerayder

19 days ago

Help me understand this 'embedded in developer teams' in a larger company. Do you have no central infrastructure with centralized tooling, alerting, standards and knowledge?

Team A has a devops engineer, Teams B through F have one, how do they have any capacity to pursue long term strategical projects, save money and operational effort with centralized hosting and tooling, and basically have some autonomy, when they are enslaved to a Scrum Master and some hokey pokey Fibonacci numbers and T Shirt Size nonsense having to argue priorities in every Sprint against people who don't care about operations?

That's what embedded devops is to me - an operational role enslaved to dev leads, the poor guy who has to troubleshoot a failed release while the devs are at the bar.

Unless my straw man is wildly off, no thanks to that embedded stuff.

5 comments

mancerayder

Reply
raw_anon_1111  19 days ago

That’s exactly what it means , a person who reports to the infrastructure team who decides standards and is embedded with the devs as part of the project.

If you are just throwing things over the fence - you’re an “operations” team and get none of the benefits of DevOps

  • mancerayder  19 days ago

    Understood, but so far what I observed is the embedded devops pressured/saying Yes/beholden to a PM running sprints, and the central infra team management constantly has to intervene to protect the embedded devops engineer politically.

    Maybe my experience is a rare example, but my conclusion so far is that it's tricky to prevent this painful situation, and requires vigilance.