Atlanta, Georgia
2016-07-25 to 2016-07-29
With special guest star Andrew Clay Shafer!
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:
if you want to watch me screw up @bridgetkromhout's talk at #Agile2016, here you go https://t.co/Yv98fxIyJ0
— Andrew Clay Shafer 雷启理 (@littleidea) July 28, 2016
#Agile2016 @bridgetkromhout @littleidea talk on containers won't fix your broken culture is about to commence. pic.twitter.com/DXTIEQuoMm
— Vinayak Joglekar (@vinayakj) July 28, 2016
Excited to see @bridgetkromhout at #Agile2016 #DevOps pic.twitter.com/H2wI6iCglZ
— Jessica Joy Kerr (@jessitron) July 28, 2016
@bridgetkromhout and @littleidea talking Pokemon and devops and culture at #Agile2016 pic.twitter.com/VLrWUsJj2f
— shoutingintothevoid (@peternealon) July 28, 2016
#Agile2016 such a treat to have these big thinkers talking devops @bridgetkromhout @littleidea pic.twitter.com/UQDGZCdHBv
— shoutingintothevoid (@peternealon) July 28, 2016
At #Agile2016 watching @littleidea & @bridgetkromhout talk about #culture, #containers, & hopeful intersections. 😂😎👍 pic.twitter.com/DTGY4Xkjpe
— Mark⚡️Heckler 👨🏻💻🍃✈️ (@mkheck) July 28, 2016
@bridgetkromhout Humor: "How many DevOps does it take to have workable A/V for a presentation? - All of them!" #Agile2016 @devopsdays
— Philip Rogers (@g_philip) July 28, 2016
#Agile2016 @bridgetkromhout @littleidea technical merit isnt always reason why technical decisions are made,it's more of fashion/tribalism
— Vinayak Joglekar (@vinayakj) July 28, 2016
@bridgetkromhout on #Agile2016 "90 % of tech is tribalism and fashion" pic.twitter.com/nKOmzE1eBG
— Oscar Amelunge (@oscaramelunge) July 28, 2016
Learn to speak, write, and listen. Communication will have more impact on your career than any technical skills.@littleidea #Agile2016
— Jessica Joy Kerr (@jessitron) July 28, 2016
@bridgetkromhout @littleidea talking practices and tribalism #Agile2016 pic.twitter.com/1t5GnMfmCJ
— shoutingintothevoid (@peternealon) July 28, 2016
Regardless of paradigm, it just *fits*. @bridgetkromhout & @littleidea killing it at #Agile2016. 😎👍 pic.twitter.com/WRjY01vzW8
— Mark⚡️Heckler 👨🏻💻🍃✈️ (@mkheck) July 28, 2016
@bridgetkromhout @littleidea loss of context as a risk in large batch size deployment #Agile2016
— shoutingintothevoid (@peternealon) July 28, 2016
@bridgetkromhout @littleidea the product that is available to customers can be decoupled from the release #Agile2016
— shoutingintothevoid (@peternealon) July 28, 2016
Who thinks deploying once a month is safer?
— Jessica Joy Kerr (@jessitron) July 28, 2016
[no one]
"You're wrong."@littleidea#Agile2016 pic.twitter.com/EscNdrOENW
@littleidea @bridgetkromhout deployment pain measured in 1am decisions to drink huge cans of rockstar energy drink #Agile2016
— shoutingintothevoid (@peternealon) July 28, 2016
#Agile2016 @bridgetkromhout @littleidea reasons why we are not able to do CD pic.twitter.com/GK57HPhP4z
— Vinayak Joglekar (@vinayakj) July 28, 2016
@littleidea @bridgetkromhout the ideal is not to minimize incidents but to maximize ability to recover #Agile2016
— shoutingintothevoid (@peternealon) July 28, 2016
#Agile2016 @bridgetkromhout @littleidea when rollback is a separate process than roll forward and its used less often->more prone to failing
— Vinayak Joglekar (@vinayakj) July 28, 2016
#Agile2016 @bridgetkromhout @littleidea ad hoc automation is a problem unless supported by highly flexible/decoupled architecture
— Vinayak Joglekar (@vinayakj) July 28, 2016
#Agile2016 @bridgetkromhout @littleidea goal is not to automate but to shorten the idea to value cycle. pic.twitter.com/FGXNKmrhGf
— Vinayak Joglekar (@vinayakj) July 28, 2016
@littleidea @bridgetkromhout #Agile2016 pic.twitter.com/4jeBzo6SJS
— shoutingintothevoid (@peternealon) July 28, 2016
#Agile2016 @bridgetkromhout @littleidea pic.twitter.com/i7lU539yDQ
— Vinayak Joglekar (@vinayakj) July 28, 2016
@littleidea @bridgetkromhout any pizza is a personal pizza if you believe in yourself #Agile2016
— shoutingintothevoid (@peternealon) July 28, 2016
#Agile2016 @bridgetkromhout @littleidea value in the trend monolith->microservices is questionable pic.twitter.com/p65G7SsvqS
— Vinayak Joglekar (@vinayakj) July 28, 2016
@testidea @bridgetkromhout anyone for buzzword bingo? #agile2016 pic.twitter.com/qin7da85O3
— John Stevenson (@steveo1967) July 28, 2016
#Agile2016 @bridgetkromhout @littleidea microservices->independently deployable objects.
— Vinayak Joglekar (@vinayakj) July 28, 2016
Dev vs. Ops, pure gold. 😂@bridgetkromhout & @littleidea at #Agile2016. pic.twitter.com/JaEGNNEAGF
— Mark⚡️Heckler 👨🏻💻🍃✈️ (@mkheck) July 28, 2016
@littleidea @bridgetkromhout talking about Google borg https://t.co/WaKlmlkx8I #agile2016
— John Stevenson (@steveo1967) July 28, 2016
#Agile2016 @bridgetkromhout @littleidea this happens because development incented to change & ops incented not to pic.twitter.com/DIySj034P3
— Vinayak Joglekar (@vinayakj) July 28, 2016
#Agile2016 @bridgetkromhout @littleidea wall of confusion happens because the process is dehumanised by a system like help desk ticketing.
— Vinayak Joglekar (@vinayakj) July 28, 2016
If you don't experiment before production, then production is your experiment. @bridgetkromhout @littleidea #Agile2016
— Gene Gotimer (@CoverosGene) July 28, 2016
#Agile2016 @bridgetkromhout @littleidea if you don't experiment before putting things in production then production becomes an experiment
— Vinayak Joglekar (@vinayakj) July 28, 2016
Good judgment comes from experience, and a lot of that comes from bad judgment. - Will Rogers @bridgetkromhout @littleidea #Agile2016
— Gene Gotimer (@CoverosGene) July 28, 2016
#Agile2016 @bridgetkromhout @littleidea refactoring legacy systems is also an opportunity to refactor the organisation structure
— Vinayak Joglekar (@vinayakj) July 28, 2016
@littleidea & @bridgetkromhout quoting Deming 'it's not necessary to change, survival is not mandatory' #agile2016
— John Stevenson (@steveo1967) July 28, 2016
@littleidea @bridgetkromhout devops love cc: @sigje @beerops pic.twitter.com/TtqPkx2xFy
— shoutingintothevoid (@peternealon) July 28, 2016
#Agile2016 @bridgetkromhout @littleidea DevOps can't be bought it needs to be practiced pic.twitter.com/JjCHSlYpa7
— Vinayak Joglekar (@vinayakj) July 28, 2016
Software is made of humans.@littleidea and @bridgetkromhout at #Agile2016 pic.twitter.com/NoOey1QvpB
— Jessica Joy Kerr (@jessitron) July 28, 2016
@bridgetkromhout @littleidea deep thinking and feels, so much food for thought...write, talk, listen #Agile2016 pic.twitter.com/9OZzf6ZuGI
— shoutingintothevoid (@peternealon) July 28, 2016
@littleidea @bridgetkromhout talking CAP theorem for humans, so awesome...mind blown just a little #Agile2016
— shoutingintothevoid (@peternealon) July 28, 2016
#Agile2016 @bridgetkromhout @littleidea Cap theorem also applies to orgs.Distributed decisionmaking can overcome it pic.twitter.com/EWEcNkwcBo
— Vinayak Joglekar (@vinayakj) July 28, 2016
"Process: scar tissue from past failures."@bridgetkromhout
— Mark⚡️Heckler 👨🏻💻🍃✈️ (@mkheck) July 28, 2016
Great stuff. 👍
Separate dev and ops:@bridgetkromhout @littleidea #Agile2016 pic.twitter.com/A8BQ5dLqPN
— Jessica Joy Kerr (@jessitron) July 28, 2016
Automating deployment:
— Jessica Joy Kerr (@jessitron) July 28, 2016
if you don't reconsider the architecture, then the technology is fighting against you.@bridgetkromhout #Agile2016