DEV Community

Discussion on: DevOps teams are an anti-pattern, but ...

Collapse
 
thebouv profile image
Anthony Bouvier

Amazing response and I love the CAC/IAC angle. The great thing about that is it allows for that merging of Ops and Dev teams. Devs can see the config/infra as code and treat it as such. Ops can have repeatable builds and finally grok the benefits of version control and pipelines for more than "just code".

Another important win from this like you pointed out is devs seeing more about the skeleton underneath the muscle and skin they've been adding to the body so to speak. I'm surprised again and again at how many devs I talk to when I'm mentoring or even when I'm talking to senior level devs. They've always focused so much on the code, they really know very little about servers, how DNS works, hell even how the Internet works. With CAC/IAC as you say they can see, learn, ask questions and grow.

The DevOps Handbook is great! I love the mini-whitepaper style when companies growth through the DevOps journey is discussed. I just wish there were more examples of small to medium sized companies currently doing digital transformations into DevOps shops. I wish more articles were out there about that. Too much focus is given to how "the big boys" are doing it and 99% of devs will never work at places like that.

And of course I always recommend The Phoenix Project. I've read it once and listened to the audiobook twice. I need to pick up The Unicorn Project sometime too or finish listening to it.

Again, thanks for the comment!