Computers are easy; people are hard (Open Source North)

1. @bridgetkromhout
Computers are easy;
people are hard

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

3. @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
Image credit: visual_dichotomy on Flickr
“In the last week there were
67 deploys
of 496 changes
by 18 people”

5. @bridgetkromhout
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
Not the goal: resumé-driven development

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

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

9. @bridgetkromhout
complex
ecosystems

10. @bridgetkromhout
disruption

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

12. @bridgetkromhout
Attack
Kitten
growls
about
Day 2

13. @bridgetkromhout
Attack Kitten Cat Reality Check

14. @bridgetkromhout
tools: necessary but not sufficient

15. @bridgetkromhout
Image credit: James Ernest

16. @bridgetkromhout
The Wall of Confusion

17. @bridgetkromhout
The Wall of Confusion
yolo nope

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

19. @bridgetkromhout
for devs, build for operability:
observability, debuggability, reality

20. @bridgetkromhout
hard problems & human factors

21. @bridgetkromhout
hard problems & human factors

22. @bridgetkromhout

23. @bridgetkromhout
communication &
disconnects

24. @bridgetkromhout
observability: answering questions we didn’t know to ask

25. @bridgetkromhout
understand your environment

26. @bridgetkromhout
monitoring: the old way

27. @bridgetkromhout
Monitoring
monitoring: the new way

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

29. @bridgetkromhout Image 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

30. @bridgetkromhout Image credit: IpTel
1. The network is reliable.
2.Latency is zero.
3.Bandwidth is infinite.
4.The network is secure.
5.Topology doesn't change.
6.There is one administrator.
7. Transport cost is zero.
8.The network is homogeneous.
eight fallacies of distributed computing

31. eight fallacies of distributed humans
@bridgetkromhout
1. Your personal network is a reliable hiring source.
2.Communication is easy.
3.You can have it all!
4.Safety looks the same for everyone.
5.Your challenges are universal.
6.You’re good at computers; manage people!
7. If you could do it, why can’t they?
8.Tech is a meritocracy.

32. @bridgetkromhout

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

34. @bridgetkromhout
devops: a culture of collaboration

35. @bridgetkromhout
devops MSP
monthly meetup
June 12
at SPS Commerce
devopsdays Minneapolis 2017
annual conference
July 25-26
at Hilton Minneapolis