Cape Town, South Africa
2016-03-10 to 2016-03-11
Description:
Containers will not fix your broken culture. Microservices won’t prevent your two-pizza teams from needing to have conversations with one another over that pizza. No amount of industrial-strength job scheduling makes your organization immune to Conway’s Law.
Does this mean that devops has failed? Not in the slightest. It means that while the unscrupulous might try to sell us devops, we can’t buy it. We have to live it; change is a choice we make every day, through our actions of listening empathetically and acting compassionately. Iterative improvement starts somewhere for us all; let’s talk about it.
Tools are essential, but how we implement the tools and grow the culture and practices in our organizations needs even more attention. Whether you’re just starting to implement technical and organizational change, or facing the prospect that you already have legacy microservices, it’s worth considering the why and the how of our behaviors, not just the what.
Making thoughtful decisions about tools and architecture can help. Containers prove to be a useful boundary object, and deconstructing systems to human-scale allows us to comprehend their complexity. We succeed when we share responsibility and have agency, when we move past learned helplessness to active listening. But there is no flowchart, no checklist, no shopping list of ticky boxes that will make everything better. “Anyone who says differently is selling something”, as The Princess Bride teaches us. Instead, let’s talk about practical, actionable steps that will help. How do we evaluate our progress? How do we know when to course-correct? How do we react when it seems like there’s always something new we should have done last month?
Part rant, part devops therapy, this talk will explain in the nerdiest of terms why CAP theorem applies to human interactions too, how oral tradition is like never writing state to disk, and what we can do to avoid sadness as a service.
Slides:
Video:
Twitter reactions:
Next up at #scaleconf: @bridgetkromhout speaks hard truths about containers. pic.twitter.com/O7x2PjOQMk
— Joe Laha (@joelaha) March 11, 2016
"An evil marketing person who has opinions about bash" - @bridgetkromhout #scaleconf
— bob (@rjw1) March 11, 2016
call your staging environment "theory". It only works in theory #scaleconf
— shafeek_naidoo (@shafeek_naidoo) March 11, 2016
@bridgetkromhout crazy start to the last talk @scaleconf today! Good ending to another good day :) #scaleconf
— Jarrett Jordaan (@jljordaan) March 11, 2016
#scaleconf pic.twitter.com/qLi0ZzBUW1
— Telic Consulting (@TelicConsulting) March 11, 2016
“The most important word in Conway’s Law is ‘communication’” @bridgetkromhout #scaleconf pic.twitter.com/vhR4bemfoj
— Joe Laha (@joelaha) March 11, 2016
Ahh @bridgetkromhout thanks for breaking down Conway's law #scaleconf pic.twitter.com/5KI1vufVJc
— q (@quintonparker) March 11, 2016
2019 the year of the inode hypecycle #scaleconf
— bob (@rjw1) March 11, 2016
We always end up talking about the same things in tech @bridgetkromhout pic.twitter.com/mPsaoMUrov
— Siobhan O’Donovan Meier (@justshiv_) March 11, 2016
90% of tech is tribalism and fashion #scaleconf
— q (@quintonparker) March 11, 2016
Rename "staging" to "theory" so that it "works in theory" - great joke by @bridgetkromhout #scaleconf
— Brad Mostert (@bsinkwa) March 11, 2016
Ah yeah @bridgetkromhout making a Babylon 5 reference. "Nothing's the same anymore" #scaleconf pic.twitter.com/z31FQ8ffuO
— bob (@rjw1) March 11, 2016
Docker all the dockers #scaleconf
— q (@quintonparker) March 11, 2016
THIS: "legacy: your customers & 💰live here" @bridgetkromhout #scaleconf
— Yenkel (@dschenkelman) March 11, 2016
“In order to become Cloud Native do you have to go through the Cloud Immigration and Naturalization Services?” - @bridgetkromhout— Tyler McMullen (@tbmcmullen) March 11, 2016
Being afraid of tech change is okay, but avoiding it is probably not a good idea @bridgetkromhout #scaleconf pic.twitter.com/NZEVnf91jf
— Siobhan O’Donovan Meier (@justshiv_) March 11, 2016
This last talker has everyone on a high haha! She be on "tik" in a good way ;) #scaleconf really good talk.
— Jarrett Jordaan (@jljordaan) March 11, 2016
Giving someone a DevOps certification is like praising a kindergartener for not eating crayons @bridgetkromhout #scaleconf
— Siobhan O’Donovan Meier (@justshiv_) March 11, 2016
Speaking in the last slot on a Friday is tough. Inspiring this much energy in the tired crowd is amazing @bridgetkromhout #scaleconf
— Siobhan O’Donovan Meier (@justshiv_) March 11, 2016
Nerd references from @bridgetkromhout: Babylon 5, Hitchhiker’s Guide to the Galaxy, ASOIAF #scaleconf
— Joe Laha (@joelaha) March 11, 2016
Device mapper is basically just Sadness As A Service @bridgetkromhout #scaleconf
— Siobhan O’Donovan Meier (@justshiv_) March 11, 2016
"devicemapper is basically Sadness as a Service" @bridgetkromhout #scaleconf
— Michael Gorven (@mgorven) March 11, 2016
“Give people agency, within the boundaries of you organisation.” — @bridgetkromhout #scaleconf
— Andrew Inggs (@aminggs) March 11, 2016
CAP theorem applies to organisations as well - time zones = partitions #scaleconf @bridgetkromhout
— Anecdatabasis (@robinalangolden) March 11, 2016
Process: scar tissue from past failure #scaleconf
— q (@quintonparker) March 11, 2016
DevOps: I can see what it's trying to do. I just want to know *whyyyy*? @bridgetkromhout #scaleconf
— Siobhan O’Donovan Meier (@justshiv_) March 11, 2016
@bridgetkromhout @ #scaleconf "i can see WHAT your code is doing, i need to know WHY" and now i don't feel so alone anymore #goodcomments
— fisher king (@TwubTing) March 11, 2016
"choosing #javascript #frameworks is like choosing ice-cream, they all look good but you never know which one to choose" - #scaleconf
— D'lo DeProjuicer (@dlodeprojuicer) March 11, 2016
.@bridgetkromhout using my 1403 Vintage Mono Pro font in her @scaleconf slides. #scaleconf https://t.co/REY6RHHVtV
— Jeff Kellem (@composerjk) March 11, 2016
https://t.co/je7Eo1GBv6