Santa Clara, CA
2017-06-14
Description
Living #opslife makes us keenly aware of the cavernous gap between lofty ideals and 3am reality. In a perfect world, everyone would be devopsing sans effort. In the real world, sharing operational responsibility is not as easy as giving developers production access, adding them to an oncall rotation, and saying “good luck! have fun!”
When incentives mean a feature team is concerned primarily with shipping and not operability, while site reliability is someone else’s concern, conflict results. We build in graceful degradation for decentralized systems but often neglect the (just-as-essential) human interactions. As the fractal complexity of our distributed systems grows, we need mindful practices that work with our tooling and effective tools that reinforce our desired culture.
Slides
Video
Tweets
@bridgetkromhout talks ops at #cloudfoundry pic.twitter.com/ixChGfMHaq
— Jim Park (@jim80net) June 14, 2017
Watching @bridgetkromhout talking about #opslife in buzzwordistan. I'm so lucky that I get to work with people like Bridget. She's awesome. pic.twitter.com/GI96TrikPY
— Mark Imbriaco (@markimbriaco) June 14, 2017
Why you don't build and operate your own platform from @bridgetkromhout at #cfsummit2017 pic.twitter.com/wYPIzIGV7S
— Chuck D'Antonio (@crdant) June 14, 2017
"i don't know who they're collaborating with, but they're devopsing really hard over there" -- too true @bridgetkromhout! 😂 #cloudfoundry
— cheesedog 🧀🌭 チーズドッグ (@melichristie) June 14, 2017
Computers are hard, people are harder - @bridgetkromhout #cfsummit pic.twitter.com/ZZTLE89Jp6
— Jared Ruckle (@jaredruckle) June 14, 2017
Learning how we got to our serverless, containerized, noops, microserviced future from @bridgetkromhout at #cloudfoundry summit. pic.twitter.com/0B7mFuzkSu
— Casey West (@caseywest) June 14, 2017
“Obviously Google has a cloud (@googlecloud). It’s delightful.” – @bridgetkromhout #cloudfoundry
— Casey West (@caseywest) June 14, 2017
Super important point from @bridgetkromhout about the right constraints being empowering rather than a barrier. Make the happy path happy.
— Mark Imbriaco (@markimbriaco) June 14, 2017
An important question for #ops to ask others: "what is your goal?" says @bridgetkromhout. Get past buzzwords & pick the right tech #cfsummit
— Jared Ruckle (@jaredruckle) June 14, 2017
Think about where your alerts go so you don't just have a person standing in as a very angry named pipe. - @bridgetkromhout
— Mark Imbriaco (@markimbriaco) June 14, 2017
"Day 1 is really short, and day 2 is probably forever." - @bridgetkromhout #cfsummit pic.twitter.com/lybPWxXVSN
— Mark Imbriaco (@markimbriaco) June 14, 2017
"Team YOLO and Team Nope" ... both considered harmful. Empathy is essential. @bridgetkromhout #cfsummit pic.twitter.com/bPkLkUeKvJ
— Mark Imbriaco (@markimbriaco) June 14, 2017
Per @bridgetkromhout: "Development and Operations. Team Yolo vs. Team Nope." #cfsummit
— Josh Stone (@stonejoshstone) June 14, 2017
Team YOLO vs. Team Nope via @bridgetkromhout. They have different motivations & incentives. Get alignment around operability. #cfsummit pic.twitter.com/Z037qR9EI8
— Jared Ruckle (@jaredruckle) June 14, 2017
"I have nothing against developers. Some of my best friends are developers." - @bridgetkromhout. Could be Stockholm Syndrome ...
— Mark Imbriaco (@markimbriaco) June 14, 2017
Don't expect Dev & Ops to be friends if Ops is putting out a fire every time Dev is at their release party/@bridgetkromhout #cfsummit2017
— Danielle Burrow (@DBurrow11) June 14, 2017