Copenhagen, Denmark
2016-10-03 to 2016-10-04
We endeavor to build consistency, availability, and fault tolerance into our distributed systems, but how do we build them into our teams? The human factors in devops require as much attention as do our technical implementations.
Collaboration, understanding, trust: we know how important these interactions are in a devops practice, but how do we enable them between disparate team members, especially in a distributed team? My company’s in California, and I’m over three thousand kilometers away in flyover country, USA. Being one of those little squares at the bottom of every video call gives me an outsider’s perspective on the inside of our organizational optimization.
Drawing in comparisons from theoretical computer science and practical systems implementation, I’ll explore how building understanding requires a practical application of great tools in a deliberate pursuit of a constructive culture.
How do we build consistency + availability + fault tolerance in our teams? @bridgetkromhout discusses at #GOTOcph https://t.co/yIw5HQNlPN
— GOTO Copenhagen (@GOTOcph) October 4, 2016
A topic near and dear to my heart. My teammate @bridgetkromhout presenting on distributed teams #gotocph pic.twitter.com/OfAZBKipWw— Kenny Bastani (@kennybastani) October 4, 2016
Last but certainly not least, @bridgetkromhout talking distributed systems and teams at #gotocph pic.twitter.com/mQBFa0OdxU
— Camille Fournier (@skamille) October 4, 2016
Talking about distributed teams with @bridgetkromhout. #gotoCPH pic.twitter.com/562IwACh8O
— Joe Laha (@joelaha) October 4, 2016
Never seen a better, more succinct analogy of dev vs ops than this #gotocph pic.twitter.com/aDrZAa8au4
— Camille Fournier (@skamille) October 4, 2016
The wall of confusion. Sometimes even across the hallway... #gotocph pic.twitter.com/0idh8HCgfZ
— David Müller (@dmwtia) October 4, 2016
talking about ops as "them"... "i mean full stack? is that real? nobody has the time" #GOTOcph pic.twitter.com/Nf7ouTrr4M
— Jana Bork (@janananena) October 4, 2016
Setting clear expectations around comma for distributed teams is vital - @bridgetkromhout @GOTOcph pic.twitter.com/zyBHMUijLf
— Sam Newman (@samnewman) October 4, 2016
In very distributed teams it is important to have clear communication and set expectations - @bridgetkromhout at #gotocph
— Kristjan Wager (@kriswager) October 4, 2016
Follow-up: "I'd tell you a UDP joke, but there's no guarantee you'd get it." Watching @bridgetkromhout #gotocph pic.twitter.com/Qzta4NL92y
— Andrew Kurowski (@kurowdotski) October 4, 2016
Non violent communication is talking like TCP with handshakes, rather than talking like UDP... #gotocph @bridgetkromhout pic.twitter.com/bSGi18UtZt
— Kornelis Sietsma (@kornys) October 4, 2016
Maybe we need to tell more tales… @bridgetkromhout on documentation @GOTOcph pic.twitter.com/C6qqNRYDUJ
— Sam Newman (@samnewman) October 4, 2016
“It’s important to keep a record of decisions between distributed team members” @bridgetkromhout @caseywest #gotocph pic.twitter.com/xxPATaKHPs— Kenny Bastani (@kennybastani) October 4, 2016
"Move your decision making as far as possible toward the edges" - @bridgetkromhout on distributed teams #gotocph
— Andrew Kurowski (@kurowdotski) October 4, 2016
Quality slide work by @bridgetkromhout pic.twitter.com/idsLUrx9KX
— COREYHAINES! (@coreyhaines) October 4, 2016
“There is no talent shortage..Oh – and we’re hiring by the way – https://t.co/jy7DO0HJzE" 👍@bridgetkromhout #gotocph pic.twitter.com/PTDpSTAlza
— Kenny Bastani (@kennybastani) October 4, 2016
Great final talk @GotoCph distributed teams! @bridgetkromhout - San Francisco looks nice ;) #gotocph #cphftw pic.twitter.com/dPLXIv6Gyi
— Zoltan Simon (@zsim0n) October 4, 2016