In this podcast Shane Hastie, Lead Editor for Culture & Methods, spoke to Aurynn Shaw about how DevOps, Microservices and other “technical” approaches are in fact cultural constraints on technical ideas and what’s needed to make the culture sustainable.

Key takeaways:

* Running and testing a program on the developer desktop is not running the program

* You must rethink the approach to building the software based on the way it will be deployed

* DevOps isn’t about the tooling – it is about the context in which we find ourselves

* Sustainable DevOps is about understanding the system that makes up the organisation ecosystem and what needs to change to enable the new ways of working

* Design the system to help prevent dangerous actions rather than laying blame when something goes wrong

* As a technologist you want to say “yes” – fix the systems around you that force you to say “no”

* When examining the system we will discover that we’ve done things that we’re not happy about and must accept that they happened without apportioning blame