Computers are easy; people are hard (ATO 2017)

1. @bridgetkromhout #ato2017
Computers are easy;
people are hard

2. @bridgetkromhout #ato2017
lives:
Minneapolis,
Minnesota
works:
Microsoft
podcasts:
Arrested
DevOps
organizes:
devopsdays
Bridget Kromhout

3. #ato2017@bridgetkromhout
Massively scalable fault-tolerant
distributed systems require a
significant engineering effort to build
and operate; complex socio-technical
systems are even more challenging.
Computers are easy;
people are hard

4. @bridgetkromhout #ato2017
Image credit: visual_dichotomy on Flickr
“In the last week there were
67 deploys
of 496 changes
by 18 people”

5. @bridgetkromhout #ato2017
quoted in “10+ Deploys Per Day:
Dev and Ops Cooperation at Flickr” at Velocity 2009
John Allspaw & Paul Hammond
Flickr Dev Blog, December 17th 2008
Image credit: visual_dichotomy on Flickr
“In the last week there were
67 deploys
of 496 changes
by 18 people”

6. @bridgetkromhout #ato2017
Not the goal: resumé-driven development

7. @bridgetkromhout #ato2017
The goal: shorter time from
idea to value
Image credit: leadliasionImage credit: thebigword

8. @bridgetkromhout #ato2017
How do we
get to
the goal?

9. #ato2017@bridgetkromhout
complex
ecosystems

10. @bridgetkromhout #ato2017
disruption

11. @bridgetkromhout #ato2017
just say no to “awesome mode” vs “sad mode”
Image credit: stock
bimodal IT?!?

12. #ato2017@bridgetkromhout
“In a world that celebrates pioneers—
be the settlers instead.”
— Laura Bell (@lady_nerd)

13. @bridgetkromhout #ato2017
Attack
Kitten
growls
about
Day 2

14. @bridgetkromhout #ato2017
Attack Kitten Cat Reality Check

15. #ato2017@bridgetkromhout
empathy

16. #ato2017@bridgetkromhout
tools: necessary but not sufficient

17. @bridgetkromhout #ato2017
Image credit: James Ernest

18. @bridgetkromhout #ato2017
The Wall of Confusion

19. @bridgetkromhout #ato2017
The Wall of Confusion
yolo nope

20. #ato2017@bridgetkromhout
for ops, don’t tell devs: gl;hf!
do: automate
document
share

21. #ato2017@bridgetkromhout
for devs, build for operability:
observability, debuggability, reality

22. @bridgetkromhout #ato2017
Image credit: Vasa Museet
probably fine

23. @bridgetkromhout #ato2017
hard problems & human factors

24. @bridgetkromhout #ato2017
hard problems & human factors

25. @bridgetkromhout #ato2017

26. #ato2017@bridgetkromhout

27. #ato2017@bridgetkromhout
understand your environment

28. @bridgetkromhout #ato2017
observability: answering questions we didn’t know to ask

29. #ato2017@bridgetkromhout
monitoring: the old way

30. @bridgetkromhout #ato2017
Monitoring
monitoring: the new way

31. @bridgetkromhout #ato2017Image credit: Wikipedia
“Any organization that designs a system…
will produce a design
whose structure is a copy of
the organization's
communication
structure.”
Mel Conway

32. @bridgetkromhout #ato2017
communication &
disconnects

33. @bridgetkromhout #ato2017

34. #ato2017@bridgetkromhout
Who owns your availability? The answer may surprise you!
Image credit: Wikipedia

35. @bridgetkromhout #ato2017
operational investments architecture
observability
culture

36. #ato2017@bridgetkromhout
not actually
20 units of devops

37. #ato2017@bridgetkromhout
silos are for grain

38. #ato2017@bridgetkromhout
still computers

39. @bridgetkromhout #ato2017
The Wall of Confusion
(kinda lonesome)

40. #ato2017@bridgetkromhout
people > processes > tools

41. #ato2017@bridgetkromhout

42. #ato2017@bridgetkromhout
thanks!