We hear a lot about devops these days, and the promise is temendous. It originally evolved out of Agile operations. But how to get those benefits at *my* organization?
Join 38,000 others and follow Sean Hull on twitter @hullsean.
How do we become a high performing organization, to move faster and build more secure and resilient systems? That’s the $64,000 question!
A16Z strikes again! Andreeson Horowitz’s epic podcast hosts world class guests around all sorts of startup & new technology topics. This week they interview Jez Humble and Nicole Forsgren. They run Dora which is DevOps Research and Assessment, which shows organizations just how to get the advantages of devops in the real world.
Technology does not drive organizational performance
Check out section 16:04 in the podcast…
“the point of distinction comes from how you tie process and culture together technology through devops”
It’s the classic Amazon model. They’re running hundreds of experiments in production at any one time!
Day one is short, day two is long
The first interesting quote that caught my attention was at 4:40…
“Day one is when we create all of these systems. Day two is when we deploy to production. We have to deploy and maintain forever and ever and ever. We hope that day two is really long.”
As a long time op, this really really resonates for me. Brownfield deployments, which have already seen a wave of developers finish, and leave, and trying to manage that. Not easy!
Mainframes of Kubernetes?
What about tooling? Is that important? Here’s what Jez has to say. Jump to 29:30…
“Implementing those technologies does *not* give you those outcomes. You can achieve those results with Mainframes. Equally you can use Kubernetes, Docker and microservices and not achieve those outcomes.”
Related: Is Amazon too big to fail?
Fast forward to timecode 28:45…
“Conways Law: Organizations which design systems are constrained to produce designs that are copies of the communication structures of these organizations.”
ie your software code looks like the shape of organization itself, and how we communicate. Super interesting. 🙂
Related: 6 devops interview questions