Toronto, Canada
2016-05-26 to 2016-05-27
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:
Tweets:
Looking forward to some _real_ conversations about hard #devops truths with @bridgetkromhout #devopsdays
— Cliffe (@Cliffehangers) May 26, 2016
"Minneapolis, the land of 10,000 DevOps cliches." @bridgetkromhout at #DevOpsDays
— Will Weaver (@buildingbananas) May 26, 2016
"Snow is a feature, not a bug" --@bridgetkromhout
— Marguerite dTM (@des4maisons) May 26, 2016
. @bridgetkromhout bringing the hard truths to #devopsdays pic.twitter.com/NQlfaPKZWW
— Joe Laha (@joelaha) May 26, 2016
Running docker in production #2013 #yolo. Great stuff @bridgetkromhout #devopsdays pic.twitter.com/rIohYhwQAI
— brettg98 (@brettg98) May 26, 2016
Loving this. I hope some day I can deliver a message as clearly and enjoyably as @bridgetkromhout. pic.twitter.com/44FFIp6HYT
— Will Weaver (@buildingbananas) May 26, 2016
.@bridgetkromhout advocating to not be a keyboard as a service #devopsdays
— Colin Hutchinson (@hutchic) May 26, 2016
Containers won't fix your broken culture. @bridgetkromhout #DevOpsDays pic.twitter.com/fd75aSWZGs
— Brandon Pal (@brandonpal) May 26, 2016
.@bridgetkromhout: "If you don't have centralized logging, you're not going to be able to correlate problems." #DevOpsDays #devops
— Chris Kemp (@mindoverdata) May 26, 2016
My fav saying from @bridgetkromhout is that “ops shouldn’t be a keyboard as a service for developers.” #devopsdays pic.twitter.com/q8c3fxVzJm
— Arthur Maltson (@amaltson) May 26, 2016
So true. “Let’s be honest, ServiceNow is ServiceNever” @bridgetkromhout #devopsdays
— Arthur Maltson (@amaltson) May 26, 2016
“Legacy is making you money, don’t necessarily be embarrassed by it” @bridgetkromhout #devopsdays pic.twitter.com/LpkUEzOtxe
— Arthur Maltson (@amaltson) May 26, 2016
"It's not necessary to change. Survival is not mandatory."
— Roustem Karimov (@roustem) May 26, 2016
— W. Edwards Deming
Thank you, @bridgetkromhout
Another book for your summer reading list #DevOpsDaysTO via @bridgetkromhout pic.twitter.com/EYJHeJaBmc
— brettg98 (@brettg98) May 26, 2016
“Surprisingly, the company I work at is run by humans… Make right way the easy way.” @bridgetkromhout #devopsdays pic.twitter.com/Kn5YqitUGZ
— Arthur Maltson (@amaltson) May 26, 2016
Yolo! @bridgetkromhout #DevOpsDays pic.twitter.com/8PIDsqSTFn
— Brandon Pal (@brandonpal) May 26, 2016
“Wall of confusing is actually like this.” @bridgetkromhout #devopsdays pic.twitter.com/ydZLT2I6us
— Arthur Maltson (@amaltson) May 26, 2016
I gotta have more YOLO, down with the Nopes. cc: @bridgetkromhout #devopsdays
— Cliffe (@Cliffehangers) May 26, 2016
DevOps is empathy: people must communicate constantly to stay on the same page. @bridgetkromhout #devopsdays
— Max Timchenko (@MaxVT) May 26, 2016
"Sometimes I am sitting there, thinking stabity stabity stabity. #devopsdays @bridgetkromhout pic.twitter.com/BnjHJeSrZW
— Brandon Pal (@brandonpal) May 26, 2016
@bridgetkromhout thanks for a terrific talk at #devopsdaysto. Best one yet!!! NVC FTW.
— Steve Tunney (@stevetunney) May 26, 2016
"You can't make all of your decisions by consensus. Do you really need to wait for HQ to wake up?" @bridgetkromhout pic.twitter.com/8IjhQA5dF5
— Cliffe (@Cliffehangers) May 26, 2016
"You can't solve everything by telling a story. " #devopsdays @bridgetkromhout pic.twitter.com/kVrAPlxo49
— Brandon Pal (@brandonpal) May 26, 2016
"Process: scar tissue from past failure" - @bridgetkromhout #devopsdays
— Jason Harley (@redmind) May 26, 2016
"The way we've always done things, isn't a reason to stick with it." Living this. #devopsdays @bridgetkromhout pic.twitter.com/cm1MHyJ42P
— Brandon Pal (@brandonpal) May 26, 2016
"the team of 'no' is a thing of the past" via @bridgetkromhout pic.twitter.com/6XRxWVKLLw
— brettg98 (@brettg98) May 26, 2016
#devopsdays loved the presentation by @bridgetkromhout pic.twitter.com/5EwO543EUT
— jbobbylopez (@jbobbylopez) May 26, 2016
@bridgetkromhout mentioned Kyle's terrific work on failure/dist sys. On-ramp here: #devopsdays https://t.co/pzBAadJAjX
— micaldwell (@micaldwell) May 27, 2016
Awesome example @bridgetkromhout ! https://t.co/ohpHUQrLkP
— Matt Beran (@mattberan) May 27, 2016