Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
@bridgetkromhout
Computers are easy;
people are hard
@bridgetkromhout
lives:
Minneapolis,
Minnesota
works:
Pivotal
podcasts:
Arrested
DevOps
organizes:
devopsdays
Bridget Krom...
@bridgetkromhout
Massively scalable fault-tolerant
distributed systems require a
significant engineering effort to build
and...
@bridgetkromhout
Image credit: visual_dichotomy on Flickr
“In the last week there were
67 deploys
of 496 changes
by 18 peo...
@bridgetkromhout
quoted in “10+ Deploys Per Day:
Dev and Ops Cooperation at Flickr” at Velocity 2009
John Allspaw & Paul H...
@bridgetkromhout
Not the goal: resumé-driven development
@bridgetkromhout
The goal: shorter time from
idea to value
Image credit: leadliasionImage credit: thebigword
@bridgetkromhout
How do we
get to
the goal?
@bridgetkromhout
complex
ecosystems
@bridgetkromhout
disruption
@bridgetkromhout
just say no to “awesome mode” vs “sad mode”
Image credit: stock
bimodal IT?!?
@bridgetkromhout
Attack
Kitten
growls
about
Day 2
@bridgetkromhout
Attack Kitten Cat Reality Check
@bridgetkromhout
tools: necessary but not sufficient
@bridgetkromhout
Image credit: James Ernest
@bridgetkromhout
The Wall of Confusion
@bridgetkromhout
The Wall of Confusion
yolo nope
@bridgetkromhout
for ops, don’t tell devs: gl;hf!
do: automate
document
share
@bridgetkromhout
for devs, build for operability:
observability, debuggability, reality
@bridgetkromhout
hard problems & human factors
@bridgetkromhout
hard problems & human factors
@bridgetkromhout
@bridgetkromhout
communication &
disconnects
@bridgetkromhout
observability: answering questions we didn’t know to ask
@bridgetkromhout
understand your environment
@bridgetkromhout
monitoring: the old way
@bridgetkromhout
Monitoring
monitoring: the new way
@bridgetkromhout
Who owns your availability? The answer may surprise you!
Image credit: Wikipedia
@bridgetkromhout Image credit: Wikipedia
“Any organization that designs a system…
will produce a design
whose structure is...
@bridgetkromhout Image credit: IpTel
1. The network is reliable.
2.Latency is zero.
3.Bandwidth is infinite.
4.The network ...
eight fallacies of distributed humans
@bridgetkromhout
1. Your personal network is a reliable hiring source.
2.Communicati...
@bridgetkromhout
@bridgetkromhout
“In a world that celebrates pioneers—
be the settlers instead.”
— Laura Bell (@lady_nerd)
@bridgetkromhout
devops: a culture of collaboration
@bridgetkromhout
devops MSP
monthly meetup
June 12
at SPS Commerce
devopsdays Minneapolis 2017
annual conference
July 25-2...
Upcoming SlideShare
Loading in …5
×

of

Computers are easy; people are hard (Open Source North) Slide 1 Computers are easy; people are hard (Open Source North) Slide 2 Computers are easy; people are hard (Open Source North) Slide 3 Computers are easy; people are hard (Open Source North) Slide 4 Computers are easy; people are hard (Open Source North) Slide 5 Computers are easy; people are hard (Open Source North) Slide 6 Computers are easy; people are hard (Open Source North) Slide 7 Computers are easy; people are hard (Open Source North) Slide 8 Computers are easy; people are hard (Open Source North) Slide 9 Computers are easy; people are hard (Open Source North) Slide 10 Computers are easy; people are hard (Open Source North) Slide 11 Computers are easy; people are hard (Open Source North) Slide 12 Computers are easy; people are hard (Open Source North) Slide 13 Computers are easy; people are hard (Open Source North) Slide 14 Computers are easy; people are hard (Open Source North) Slide 15 Computers are easy; people are hard (Open Source North) Slide 16 Computers are easy; people are hard (Open Source North) Slide 17 Computers are easy; people are hard (Open Source North) Slide 18 Computers are easy; people are hard (Open Source North) Slide 19 Computers are easy; people are hard (Open Source North) Slide 20 Computers are easy; people are hard (Open Source North) Slide 21 Computers are easy; people are hard (Open Source North) Slide 22 Computers are easy; people are hard (Open Source North) Slide 23 Computers are easy; people are hard (Open Source North) Slide 24 Computers are easy; people are hard (Open Source North) Slide 25 Computers are easy; people are hard (Open Source North) Slide 26 Computers are easy; people are hard (Open Source North) Slide 27 Computers are easy; people are hard (Open Source North) Slide 28 Computers are easy; people are hard (Open Source North) Slide 29 Computers are easy; people are hard (Open Source North) Slide 30 Computers are easy; people are hard (Open Source North) Slide 31 Computers are easy; people are hard (Open Source North) Slide 32 Computers are easy; people are hard (Open Source North) Slide 33 Computers are easy; people are hard (Open Source North) Slide 34 Computers are easy; people are hard (Open Source North) Slide 35
Upcoming SlideShare
What to Upload to SlideShare
Next
Download to read offline and view in fullscreen.

1 Like

Share

Download to read offline

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

Download to read offline

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

Related Books

Free with a 30 day trial from Scribd

See all

Related Audiobooks

Free with a 30 day trial from Scribd

See all

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

  1. 1. @bridgetkromhout Computers are easy; people are hard
  2. 2. @bridgetkromhout lives: Minneapolis, Minnesota works: Pivotal podcasts: Arrested DevOps organizes: devopsdays Bridget Kromhout
  3. 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. 4. @bridgetkromhout Image credit: visual_dichotomy on Flickr “In the last week there were 67 deploys of 496 changes by 18 people”
  5. 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. 6. @bridgetkromhout Not the goal: resumé-driven development
  7. 7. @bridgetkromhout The goal: shorter time from idea to value Image credit: leadliasionImage credit: thebigword
  8. 8. @bridgetkromhout How do we get to the goal?
  9. 9. @bridgetkromhout complex ecosystems
  10. 10. @bridgetkromhout disruption
  11. 11. @bridgetkromhout just say no to “awesome mode” vs “sad mode” Image credit: stock bimodal IT?!?
  12. 12. @bridgetkromhout Attack Kitten growls about Day 2
  13. 13. @bridgetkromhout Attack Kitten Cat Reality Check
  14. 14. @bridgetkromhout tools: necessary but not sufficient
  15. 15. @bridgetkromhout Image credit: James Ernest
  16. 16. @bridgetkromhout The Wall of Confusion
  17. 17. @bridgetkromhout The Wall of Confusion yolo nope
  18. 18. @bridgetkromhout for ops, don’t tell devs: gl;hf! do: automate document share
  19. 19. @bridgetkromhout for devs, build for operability: observability, debuggability, reality
  20. 20. @bridgetkromhout hard problems & human factors
  21. 21. @bridgetkromhout hard problems & human factors
  22. 22. @bridgetkromhout
  23. 23. @bridgetkromhout communication & disconnects
  24. 24. @bridgetkromhout observability: answering questions we didn’t know to ask
  25. 25. @bridgetkromhout understand your environment
  26. 26. @bridgetkromhout monitoring: the old way
  27. 27. @bridgetkromhout Monitoring monitoring: the new way
  28. 28. @bridgetkromhout Who owns your availability? The answer may surprise you! Image credit: Wikipedia
  29. 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. 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. 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. 32. @bridgetkromhout
  33. 33. @bridgetkromhout “In a world that celebrates pioneers— be the settlers instead.” — Laura Bell (@lady_nerd)
  34. 34. @bridgetkromhout devops: a culture of collaboration
  35. 35. @bridgetkromhout devops MSP monthly meetup June 12 at SPS Commerce devopsdays Minneapolis 2017 annual conference July 25-26 at Hilton Minneapolis
  • fernandoike

    Jun. 8, 2017

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

Views

Total views

407

On Slideshare

0

From embeds

0

Number of embeds

172

Actions

Downloads

0

Shares

0

Comments

0

Likes

1

×