Toronto, Canada
2017-05-25 to 2017-05-26
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
Videos
Tweets
🎙Things are getting underway with our first talk from @bridgetkromhout #DevOpsDaysTO
— DevOpsDays Toronto (@DevOpsDaysTO) May 25, 2017
@bridgetkromhout kicking off the talks at #DevOpsDaysTO pic.twitter.com/dbAG9O8ICK
— Bruce Martins (@brucemartins) May 25, 2017
Starting off with @bridgetkromhout keynoting. Looking forward to it. pic.twitter.com/bRXPdWtGql
— Arthur Maltson (@amaltson) May 25, 2017
Here we go!@bridgetkromhout kicking things off for #devopsdays in Toronto. pic.twitter.com/q2W1abXEs8
— Jason Hand (@jasonhand) May 25, 2017
And we’re off! @bridgetkromhout leads off @DevOpsDaysTO. #devopsdays pic.twitter.com/CaZYhPVrTn
— Joe Laha (@joelaha) May 25, 2017
@bridgetkromhout "can't get that other team to agree that you are right" #peopleproblems #devopsdaysto pic.twitter.com/8i1esLV6i1
— Bruce Martins (@brucemartins) May 25, 2017
. @bridgetkromhout dealing with oversimplifications and complex systems. #devopsdays pic.twitter.com/6tKiPiRm8Y
— aaron aldrich is home (@crayzeigh) May 25, 2017
Great start to #devopsdays TO! @bridgetkromhout just requested that Canada annex Minnesota. Note: that is also easier than people
— Cliffe (@Cliffehangers) May 25, 2017
@bridgetkromhout "i can't do that, it's just for unicorns" - continuous deployment #devopsdaysto pic.twitter.com/9M68YgZpO9
— Bruce Martins (@brucemartins) May 25, 2017
Flickr in 2008, today it could b you. "Everyone can do this, it's not just for unicorns anymore." @bridgetkromhout #devopsdays Toronto pic.twitter.com/IwMuossVkI
— Adam Lefkowitz (@LuckyLefky) May 25, 2017
@bridgetkromhout talking about disruption and external competition, I see in big enterprises have internal competition as well #devopsdaysto pic.twitter.com/XMmF1B9c1p
— Bruce Martins (@brucemartins) May 25, 2017
Say no to bimodule IT, it's really "awesome mode" vs "sad mode" - @bridgetkromhout #DevOpsDaysTO pic.twitter.com/hGXfTrNSXA
— Arthur Maltson (@amaltson) May 25, 2017
#devopsdaysto #teamawesome is really hard, people problems @bridgetkromhout pic.twitter.com/F04kF1Pj2F
— Bruce Martins (@brucemartins) May 25, 2017
“Just say no to Awesome Mode vs. Sad Mode”. @bridgetkromhout @DevOpsDaysTO #devopsdays pic.twitter.com/nHTNMyyHwb
— Joe Laha (@joelaha) May 25, 2017
"Day 1 is short, day 2 is forever" @bridgetkromhout - been beating that into customer and developer heads for years!! #DevOpsDaysTO pic.twitter.com/WtnmGjJ9EB
— Bruce Martins (@brucemartins) May 25, 2017
Day One is short and Day Two is forever - @bridgetkromhout #DevOpsDaysTO pic.twitter.com/kqwUIfjUuZ
— Arthur Maltson (@amaltson) May 25, 2017
@bridgetkromhout Still so awesome talk! #DevOpsDaysTO pic.twitter.com/ak4Lk5Bfy7
— Benjamin Marsteau (@bmarsteau) May 25, 2017
"Tools are necessary, but not sufficient for DevOps" --@bridgetkromhout @DevOpsDaysTO
— Abeer R. (@abeer486) May 25, 2017
"You need automation around people who are single points of failure!" --@bridgetkromhout #DevOpsDaysTO
— DevOpsDays Toronto (@DevOpsDaysTO) May 25, 2017
Devs, build for operability, observability, debuggability, reality - @bridgetkromhout #DevOpsDaysTO pic.twitter.com/SMZLtQcfno
— Arthur Maltson (@amaltson) May 25, 2017
Agree, stop with crappy commit messages "committed or deleted" - @bridgetkromhout #DevOpsDaysTO pic.twitter.com/pHPCbEo2dt
— Bruce Martins (@brucemartins) May 25, 2017
"What are you incentivizing?" @bridgetkromhout asking the question that reveals so much when talking to customers. #culture pic.twitter.com/fq1EIKAXbV
— Cliffe (@Cliffehangers) May 25, 2017
"The hard problem in computer science, is working with other people" - @bridgetkromhout #DevOpsDaysTO truth!! , too many meetings pic.twitter.com/AQHY88nCJD
— Bruce Martins (@brucemartins) May 25, 2017
The past looking to people in the future trying to record a podcast on google hangouts. @bridgetkromhout #devopsdays pic.twitter.com/wv5gSxIW8B
— aaron aldrich is home (@crayzeigh) May 25, 2017
Mindful of reality
— Keri Wong (@WCOKeri) May 25, 2017
Tools: necessary but not sufficient; shouldn't dictate your choices. @bridgetkromhout @DevOpsDaysTO #DevOpsDaysTO
“They envisioned google hangouts in the 19th century. Complete with audio issues.” @bridgetkromhout @DevOpsDaysTO #devopsdays pic.twitter.com/fq8o9HA24J
— Joe Laha (@joelaha) May 25, 2017
@bridgetkromhout talking about timebombs or ied's in our product architectures, document and revisit those!! pic.twitter.com/IP86YO1P8M
— Bruce Martins (@brucemartins) May 25, 2017
Automate where person is single point of failure.
— Keri Wong (@WCOKeri) May 25, 2017
Document process; ans WHY implemented that way.
Share~ !@bridgetkromhout #DevOpsDaysTO
Even if you can't fix it, hang a sign on it and put it in the open. Make others lives easier. @bridgetkromhout #devopsdays pic.twitter.com/bFmdlAk2kT
— aaron aldrich is home (@crayzeigh) May 25, 2017
Build for operability:
— Keri Wong (@WCOKeri) May 25, 2017
Observability, debuggabiity, reality.@bridgetkromhout #DevOpsDaysTO
"State of continuos partial failure" (tm) @bridgetkromhout #DevOpsDaysTO love it
— Bruce Martins (@brucemartins) May 25, 2017
Novel ideas are great but we also need to deal with Day 2 @bridgetkromhout #devopsdays pic.twitter.com/rgJi1CS0vp
— aaron aldrich is home (@crayzeigh) May 25, 2017
The best products aren't necessarily the ones that innovated, just ones that reached everyone in a practical way. cc: @bridgetkromhout pic.twitter.com/jAkJenv9cd
— Cliffe (@Cliffehangers) May 25, 2017
Nice talk @bridgetkromhout https://t.co/POgOnHaEK0
— Moe (@moe_rafiee) May 25, 2017
This @DevOpsDaysTO event is my second Tech. conf and I feel privileged to have see @bridgetkromhout talk at both! So informative and fun!
— Benjamin Marsteau (@bmarsteau) May 25, 2017
Quality phrases learnt #5,786 "resume driven development". Excellent talk @bridgetkromhout #DevOpsDaysTO
— Dave 'The Doctor' North (@DaveNorth) May 25, 2017
Great talk by @bridgetkromhout on Computers are easy and people are hard @DevOpsDaysTO pic.twitter.com/k1AGeYhrMh
— Nomita Chennamraju (@NomitaCh) May 25, 2017
@bridgetkromhout 's talk to kick off @DevOpsDaysTO ! Love #teamawesome ;) #DevOpsDaysTO #devopsday pic.twitter.com/akv3peEVXx
— Ashton Rodenhiser (@MindsEyeCCF) May 25, 2017
Another talk great talk by @bridgetkromhout "This is fine"! pic.twitter.com/2EIyQYXED3
— DevOpsDays Toronto (@DevOpsDaysTO) May 25, 2017