Comment by raw_anon_1111
18 days ago
If you are a “DevOps engineer” - how is what you are doing any different from operations folk 25 years ago if you aren’t working with developers and embedded into their teams?
18 days ago
If you are a “DevOps engineer” - how is what you are doing any different from operations folk 25 years ago if you aren’t working with developers and embedded into their teams?
Why are you assuming that devops engineers aren’t embedded in development teams?
The problem you’re suffering from is assuming that the limited range of situations you’re familiar with is the same as what everyone else is doing.
Rule #1 is never make assumptions about anyone on the internet…
In the past 8 years I’ve led the architecture of a startup - cloud + app dev. Then spent almost 4 years working at AWS ProServe involved with large cloud + app dev “cloud application modernization” projects and now 2 years doing the same as a staff level consultant at a 3rd party consulting firm. I think I’ve seen my fair share of how large private companies, startups, government organizations and colleges work.
A lot of my projects pre AI involved bringing modern DevOps practices to an organization - convincing operations to use IAC and best practices and have them more embedded into the dev teams.
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.
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
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.
3 replies →