when relevant content is
added and updated.
DevOps has never really excited me and I never understood why until I read about DevOps team structures – https://web.devopstopologies.com/
The article suggests 7 bad practices or ‘anti-types:
- Dev and Ops Silos
- DevOps Team Silo
- Dev doesn’t need Ops
- DevOps as tools team
- Rebranded administrators
- Ops embedded in dev team
- Dev and DBA silos
It then looks at some team structures that can be made to work
- Dev and Ops collaboration
- Fully Shared Ops responsibilities
- Ops as Infrastructure as a Service
- DevOps as external service
- DevOps team with expiry date
- DevOps evangelist team
- Site Reliability Engineering team
- Container driven collaboration
- Dev and DBA collaboration
One thing that’s often not explicitly mentioned when discussing DevOps is the need for whatever teams, and individuals, to communicate. This is often anathema in my experience and why a DevOps type approach is so badly needed.
As to why DevOps hasn’t excited me – the article made me realise I’d spent a good part of my working life moving between Dev & Ops and often occupying the middle, grey area that DevOps makes its own. Its what I’ve been doing for a long time mainly without the tools we have today and not viewing it as anything special – just getting the job done.