Comment by antonvs
19 days ago
> I'd still classify what they're doing as DevOps type of work.
This is very, very wrong. Why do you think that?
19 days ago
> I'd still classify what they're doing as DevOps type of work.
This is very, very wrong. Why do you think that?
> Why do you think that?
The OP wrote:
> As an SE, I'm exposed to everything. Customers running Kubernetes, ECS, Lambda, bare metal, air-gapped environments. AWS, Azure, GCP, hybrid setups. CI/CD in Jenkins, GitHub Actions, GitLab, CircleCI. I have to understand their environment well enough to actually help them, so the learning is constant. The stagnation I felt in DevOps? Gone.
These are all things I deal with in my day to day as well in a DevOps / Infrastructure / Platform type of role. I mean, not literally everything like air-gapped environments since the companies I work for don't have that but it's all things in that category of line of work.
The only difference is I usually don't interface directly with the company's customers of the services being built. It's more like the company's staff are my customers because I'm working with developers, management and sometimes other parts of the business on ways to help optimize their workflows which all funnel back to helping create a better end customer experience.
devops means a lot of different things to different people
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.
1 reply →
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 replies →