|
|
|
|
|
|
by mattbillenstein
2246 days ago
|
|
|
The problem with this whole thing is that nobody really embraces the zen of devops (really the zen of everything) -- there should be one way to do things. Prod is something that runs in the cloud, staging is something sorta like that, but the data is garbage and nobody maintains it, and dev is whatever someone could cobble together in a bash script to get something running using homebrew dependencies -- if you're lucky. Or everyone hopes to docker-ify everything, but that's its own pile of garbage. |
|
|
It's actually k8s-ifying everything (docker-ifying was 2015-2018).
> nobody really embraces the zen of devops
I know exactly what you mean, as am struggling to get people around me understand the value of tooling, developer delight but to no avail.
Management, other non-tech teams (sales, product, Ops etc) that have learn/worked mostly in regimented setups have a long long way to go before they even start to understand what DevOps really was supposed to be - all about actionable faster feedback loops.
But, faster, actionable feedback loops also bring out the the orgs's / dept's systemic rot/muck in policies/deficiencies/politics and make it visible in-the-face. That's very threatening to many who put up a make-believe fakeshow that "our stuff's all cool, that other team/dept has all the problems". Hence, all that pushback against the new or throwing the tool in (docker/k8s/cloud) and claim that it would act as deep magic to fix the fuckery happening all over.
I learnt it over my exp at big, small, medium sized firms - over last 15+ yrs.
Only way to get to achieve DevOps (yeah, not "adopt"; one can't just 'adopt' that) is to get CTO/COO/CFO to really really understand the value. Else, lost causes!