Raleigh, NC
2017-10-23
Description
Designing distributed systems means considering failure scenarios—both likely and less so. Will the network let you down? (Almost assuredly.) Will some portion of your IaaS misbehave? (Have you met computers?) We build in graceful degradation for much of our automation but often neglect the (just-as-essential) human interactions.
The classic “hard problems” of cache invalidation and naming things revolve around our understanding of what’s correct and true and our agreements with one another on scope and relevance. Communication is essential for making context-dependent decisions.
Whether we’re attempting to determine the current state of reality or distinguish logical boundaries, democratized observability is key to answering our questions. As the fractal complexity of our distributed systems grows, we need to mindfully choose practices that work with our tooling. You can’t buy a silver bullet, but you can forge one from the collaborative efforts of your team.
Slides:
Video:
Tweets
Excited for @bridgetkromhout's #ATO2017 session "Computers are easy; people are hard." I know @drupaldiversity knows what's up. pic.twitter.com/mZeo50KVzk
— Ruby is visible (@Ruby) October 23, 2017
"if you were thinking that the title of my talk was a lie.... you're not wrong" - @bridgetkromhout #ATO2017 pic.twitter.com/OXwUrg95Dm
— Charlie Oliver (@charlieoliver) October 23, 2017
@Ruby Perfect topic, @bridgetkromhout. Most challenges stem from culture & team vs tech! #ATO2017 cc @dhinchcliffe @briansolis @satyanadella https://t.co/TR5RYdDLfZ
— 𝘐𝘢𝘯 𝘎𝘦𝘳𝘵𝘭𝘦𝘳 ☕️ 📲 (@IanGertler) October 23, 2017
Sad to admit that this is the first time I’ve heard @bridgetkromhout live. Happy to be remedying that. #ATO2017
— Coty Rosenblath (@Coty) October 23, 2017
Just say no to “awesome mode” vs “sad mode” @bridgetkromhout @AllThingsOpen pic.twitter.com/Jh3ICUKHtH
— Bruce E. Wilson (@usethedata) October 23, 2017
@Ruby @bridgetkromhout @drupaldiversity And computers do nothing without people so people are a core “skillset” for driving computers…
— Rachel Lawson 🇪🇺 (@rachel_norfolk) October 23, 2017
Even if you get everything working day 1, it's really important to think about day 2 operations - @bridgetkromhout #ato2017 pic.twitter.com/smGiFRTQrN
— Satsie (@StacieWaleyko) October 23, 2017
Bi-modal IT sounds bad 🤔 #ATO2017
— Adam Williams (@aiwilliams) October 23, 2017
Here, @bridgetkromhout fixed the Wall of Confusion. If security, product, etc. are against an idea, there might be a reason why #ato2017 pic.twitter.com/p7loWHFtUT
— Satsie (@StacieWaleyko) October 23, 2017
What are the incentives in your organization? Having empathy and understanding of the two sides of Dev and ops. @bridgetkromhout #ATO2017 pic.twitter.com/MyeGJ1g3M8
— Charlie Oliver (@charlieoliver) October 23, 2017
Lots of “observability” mentions in @bridgetkromhout’s talk. Not surprisingly, just included a shoutout to @honeycombio. #ato2017
— Coty Rosenblath (@Coty) October 23, 2017
"silos are great for grain, not for your teams" 😂 great observation and talk from @bridgetkromhout at #ATO2017
— 𝓡𝓲𝓹𝓹𝔂 👨💻 (@jkrippy) October 23, 2017
The dev ops magic is people > processes > tools. You can't buy it but you can create it 💯 @bridgetkromhout #ato2017
— Satsie (@StacieWaleyko) October 23, 2017
"People over processes over tools" @bridgetkromhout #opensource #AllThingsOpen #ATO2017 pic.twitter.com/f919uVhvqb
— Anna Niwa (@anna_niwa) October 23, 2017