Santa Clara, California
2016-06-21 to 2016-06-23
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:
Link to O’Reilly’s site for the video
Tweets:
It's @bridgetkromhout in her natural habitat: backstage before a keynote. #velocityconf pic.twitter.com/xnnyMxzuax
— Matt Broberg 📊 CHAOSScon / Fosdem (@mbbroberg) June 22, 2016
Containers will not fix your broken culture, & other hard truths — @bridgetkromhout 9:50am PT #VelocityConf keynote https://t.co/gzyTtcaRaW
— O'Reilly Infrastructure & Ops (@OReillyInfraOps) June 22, 2016
Minnesota: The land of 10,000 #DevOps cliches. - @bridgetkromhout #velocityconf
— Jason Yee (@gitbisect) June 22, 2016
Time for @bridgetkromhout‘s keynote. #velocityconf pic.twitter.com/916XTnQfPC
— Joe Laha (@joelaha) June 22, 2016
You are not going to get devops in a box because you have containers! @bridgetkromhout #velocityconf
— Milin (@milin82) June 22, 2016
'Cloudy with a chance of DevOps' @bridgetkromhout says: DevOps in a box does not exist #VelocityConf
— Rich Howard (@flowlabs) June 22, 2016
"You won't get devops in a box, and you also won't get it in a shipping container." @bridgetkromhout #velocityconf pic.twitter.com/DGrE4bfmbB
— Ryn Daniels (@rynchantress) June 22, 2016
"Cloudy with a chance of DevOps" - containers will not fix your broken culture. So true!! @bridgetkromhout #velocityconf
— Eric Gatenby (@eric_gatenby) June 22, 2016
"Organizations that aren't afraid of things are inherently fun" - the fabulous @bridgetkromhout keynoting #velocityconf
— Naomi Reeves (@animumrege) June 22, 2016
"I have actually run #Docker in production." @bridgetkromhout #VelocityConf -- I somehow found that funny
— Andrew Storms (@st0rmz) June 22, 2016
Dev: YOLO! Ops: Nope! @bridgetkromhout #velocityconf
— Tori (@ToriWieldt) June 22, 2016
You don’t get devops in a box. Or a shipping container. Containers dont solve the problem. Wall of confusion @bridgetkromhout #velocityconf
— Mike Loukides (@mikeloukides) June 22, 2016
"You can't buy Devops in containers" - @bridgetkromhout #velocityconf
— Abner (@abnerg) June 22, 2016
Very true @bridgetkromhout - Containers will not fix your broken culture. #velocityconf
— Milin (@milin82) June 22, 2016
Containers and pdx carpet in @bridgetkromhout's keynote #velocityconf pic.twitter.com/Y2N6b5oNNk
— bletchley punk (@alicegoldfuss) June 22, 2016
Containers are a useful boundary object. But they don’t eliminated the liminal space between dev and ops. @bridgetkromhout #velocityconf
— Mike Loukides (@mikeloukides) June 22, 2016
W00t! @bridgetkromhout using PDX Carpet to explain containers.
— Jason Yee (@gitbisect) June 22, 2016
PS: see the carpet live! Come to @DevOpsDaysPDX pic.twitter.com/Zq3FuaogWW
'Wall of confusion' created when orgs are incentivized differently vs being aligned & focused on biz goals @bridgetkromhout #velocityconf
— Sangeeta Narayanan (@sangeetan) June 22, 2016
Silos are for grain! lol @bridgetkromhout #velocityconf pic.twitter.com/bs3yHZRFuF
— Rich Howard (@flowlabs) June 22, 2016
woop, the #pdxcarpet makes an appearance in @bridgetkromhout's awesome keynote at #velocityconf
— Gareth Rushgrove (@garethr) June 22, 2016
The important issues are communicating between people on teams and across teams. @bridgetkromhout #velocityconf
— Mike Loukides (@mikeloukides) June 22, 2016
Containers will not fix your broken culture..well put @bridgetkromhout #velocity pic.twitter.com/J9cyOPpXOf
— Duncan Winn (@duncwinn) June 22, 2016
“Containers will not fix your broken culture…unless I missed an announcement from #dockercon” *chuckle* :) @bridgetkromhout #velocityconf
— Jay Fry (@jayfry3) June 22, 2016
Re: 🍕🍕 two-pizza teams - "How hungry are these people and what size are the pizzas?" - @bridgetkromhout #velocityconf
— Calvin F (@CalvinF) June 22, 2016
"Containers Will Not Fix Your Broken Culture" @bridgetkromhout use #ValueStreamMaps to find and kill #handoffs #queues #waste #velocityconf
— Adam Zolyak 🛠 (@azolyak) June 22, 2016
"Serverless is just servers that you can't ssh into." Loving this keynote from the amazing @bridgetkromhout #velocityconf
— Ryn Daniels (@rynchantress) June 22, 2016
the cloud is just servers that you can't SSH into @bridgetkromhout #velocityconf
— Tori (@ToriWieldt) June 22, 2016
If you can't have an unambiguous 200 msg, you need better monitoring. @bridgetkromhout #velocityconf @honest_update pic.twitter.com/4aL81LhOPi
— Jason Yee (@gitbisect) June 22, 2016
Containers are useful boundaries, but they don’t eliminate possible huge conflict. @bridgetkromhout #velocityconf pic.twitter.com/JqR4Klxdhs
— ginablaber (@ginablaber) June 22, 2016
With microservices you need better monitoring says @bridgetkromhout. Else solving an outage is like solving a murder mystery. #VelocityConf
— Peter Arijs (@p_arijs) June 22, 2016
Reminder that design follows communication patterns @bridgetkromhout love me my @flowdock #chatops #velocityconf pic.twitter.com/9P8RFCH9WO
— Adam Zolyak 🛠 (@azolyak) June 22, 2016
If we want to build a future that we want to live in, we have to talk to each other. - @bridgetkromhout #velocityconf #DevOps
— Jason Yee (@gitbisect) June 22, 2016
Fantastic talk by @bridgetkromhout at Velocity Conf! Quite awesome. Livestream is great if anyone is interested in https://t.co/v69bRLvRRt
— Nathan Oyler (@NathanOyler) June 22, 2016
Best advice from @bridgetkromhout regarding doing all this tech stuff: “Talk to each other.” Tools: necessary, not sufficient. #velocityconf
— Jay Fry (@jayfry3) June 22, 2016
"Don't forget to enjoy the #hallwaytrack" #velocityconf great reminder @bridgetkromhout !
— Adam Zolyak 🛠 (@azolyak) June 22, 2016
Software reflects org culture -Mel Conway ~1960s (thanks @bridgetkromhout #velocityconf ) pic.twitter.com/JlwHNB4rOb
— Colin Bendell (@colinbendell) June 22, 2016
I want to highlight all of @bridgetkromhout talk, underline it and send it to management #velocityconf
— boo radley : 20xx (@boo_radley) June 22, 2016
Tools are essential, but not sufficient. To build a future you want to be in, you have to talk to each other. @bridgetkromhout #velocityconf
— Jo Rhett (@jorhett) June 22, 2016
RT @jorhett: Tools are essential, but not sufficient...you have to talk to each other. @bridgetkromhout #velocityconf
— Tori (@ToriWieldt) June 22, 2016
Great talk by @bridgetkromhout at #velocityconf pic.twitter.com/1TxZrxCMeU
— Melissa Kilbourne (@mrskilbo) June 22, 2016
Nice to see @bridgetkromhout #velocityconf keynote: https://t.co/92FDzBQy6b
— Jeff Kellem (@composerjk) June 23, 2016
using my font: https://t.co/REY6RHHVtV pic.twitter.com/wAsusQue3F
Containers will not fix your broken culture, and other hard truths https://t.co/Vrl9UGOS4R < Spot on @bridgetkromhout 3 minute watch
— Jonah Kowall (@jkowall) June 24, 2016