Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
“Devops stuff”
🙄
I mean it’s not (because I think we’d all be better off rejecting any notion that “devops stuff” is shit you just shunt over to a couple of people because the parent company lacks any damn hiring discipline) but to answer your question directly: 90%+ of companies that have “devops teams” don’t actually know wtf they need beyond a slightly more than run-of-the-mill admin type who knows their way around some IaaS interfaces. -
@Ison and the real damned tragedy is how common this is.
Related Rants
Too true, too true...
On my twitter feed today.
Story of my life.
In my current company (200+ employees) we have 3 guys who deals with everything related to service desk (format computers, fix network issues, help non-tech people...)
The same team is responsible for the AWS accounts and permissions, Jenkins, self hosted Gitlab... anyway, DevOps stuff.
Thing is: only one of them have enough DevOps background to handle the requests from the engineering team (~15 people). Also, he usually do anything "by hand" clicking trough the AWS interface on each account, never using tools like Infrastructure as Code to help (that's why I started to refer to his role only as Ops, because there's no Dev being done there).
Anyway... I asked my manager why that team is responsible for both jobs, despite the engineering guys having far more experience with those tools. He answered with a shamed smile, as he probably questioned the same to his manager:
- Because they are responsible for everything related to our Infrastructure.
Does it make sense for anyone? Am I missing something here? In what universe this kind of organization is a healthy choice?
rant
devops