“Culture is a Lie,” Paul Czarkowski – Highlights

A good, and fun talk from Paul. He tries to refocus DevOps-y energy from “culture change” to more practical things for individuals to do.

Highlights:

  • You can’t change culture from the bottom. Leaders change the culture, they define it.
  • Culture is behavior.
  • If you want to change culture, you need to change your leadership.
  • Culture: as a practitioner, you can’t change it. And if you’re in a leadership position, you’re incentivized not to change it.
  • “If you choose to die on a hill, you’re gonna die on that fucking hill.”
  • Corollary: “If you don’t decide to die on a hill, you won’t die on that hill.”
  • Generative orgs can create microservices.
  • Others will make monoliths.
  • Most people spend more time justifying not working than working.
  • People who do good work will be pulled down.
  • Most people around you aren’t bad people, they’re just a product of their surroundings.
  • As soon as you start fighting the organization, it’ll start fighting back harder than you.
  • Often said: if your company is acquired by a larger company, leave.
  • Then, some examples of automating governance.

🗂 Link: Introducing VMware Tanzu Mission Control to Bring Order to Cluster Chaos

With VMware Tanzu Mission Control, we are providing customers with a powerful, API driven platform that allows operators to apply policy to individual clusters or groups of clusters, establishing guardrails and freeing developers to work within those boundaries.

Source: Introducing VMware Tanzu Mission Control to Bring Order to Cluster Chaos

Link: Pivotal Build Service, Now Alpha, Assembles and Updates Containers in Kubernetes

The service provides the layer of automation and operational control enterprises need to utilize Cloud Native Buildpacks at scale. In particular, Build Service includes three key capabilities: automated image updates, image promotion, and build configurations.

Source: Pivotal Build Service, Now Alpha, Assembles and Updates Containers in Kubernetes

Link: The Fast and Slow of Design

On the top layer there is rapid change. On the bottom, change happens at a glacial pace. It’s this combination of everything, from seconds at the top, to millennia at the bottom, that give resilience to the system.

And:

A key concept to this is that each layer has to respect the pace of another.

Source: The Fast and Slow of Design

If compliance is so important, bake it into the platform

Can we take that governance and work with the platform team to codify, to automate that which they were doing on a per application basis – that’s, quiet frankly slowing down the delivery of the software – can we take that governance and can we have them work with the platform team to codfiy, to actually automate on a per application basis, have them expose that as a service on the platform

Cornelia Davis on governance and cloud-native, “Who Does What? Mapping Cloud Foundry Activities and Entitlements to IT Roles,” August 2016

In other words: you should not only automate the audit three-ring binders of compliance, but enforce as much as possible in the platform.

The rest of the talk is good stuff on how think through re-arranging your organization to be all DevOps-y, with the help of Pivotal Cloud Platform to automate all the infrastructure and middleware stuff: