|
|
|
|
|
by tennis_80
972 days ago
|
|
Spitballing here but perhaps it's because people don't realise the DevOps work that can be done in a team, rather than just what has to be done. I work in a cultural DevOps place at the moment, and often spend my time improving CI workflows, improving the local dev environment and upgrading dev tools to make it easier to write features when requests come in. I could easily spend my entire week doing things like this, and it seems to pay off as we have a very low cycle time and fix bugs within minutes. However if you have a non-technical manager - they struggle to see value in this work. DevOps becomes "the way we get the project we built into our production environment" which is usually quite a small piece of work compared to actually building the project. So it becomes - we don't need one per team, hmm, maybe they should be centralised so we can share their time between teams, and then you lose the culture DevOps was supposed to create. |
|