Top Banner
@bridgetkromhout #mvpbuzz Computers are easy; people are hard
34

Computers are easy; people are hard (MVP Chicago 2017)

Mar 17, 2018

Download

Technology

bridgetkromhout
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
  • @bridgetkromhout #mvpbuzz

    Computers are easy; people are hard

  • @bridgetkromhout #mvpbuzz

    lives: Minneapolis,

    Minnesota

    works: Microsoft

    podcasts: Arrested DevOps

    organizes: devopsdays

    Bridget Kromhout

  • #mvpbuzz@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

  • @bridgetkromhout #mvpbuzz

    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

  • @bridgetkromhout #mvpbuzz

    Not the goal: resum-driven development

  • @bridgetkromhout #mvpbuzz

    The goal: shorter time from idea to value

    Image credit: leadliasionImage credit: thebigword

  • @bridgetkromhout #mvpbuzz

    How do we get to

    the goal?

  • #mvpbuzz@bridgetkromhout

    complex ecosystems

  • @bridgetkromhout #mvpbuzz

    disruption

  • @bridgetkromhout #mvpbuzz

    just say no to awesome mode vs sad mode

    Image credit: stock

    bimodal IT?!?

  • @bridgetkromhout #mvpbuzz

    Attack Kitten

    growls about Day 2

  • @bridgetkromhout #mvpbuzz

    Attack Kitten Cat Reality Check

  • #mvpbuzz@bridgetkromhout

    empathy

  • #mvpbuzz@bridgetkromhout

    tools: necessary but not sufficient

  • #mvpbuzz@bridgetkromhout

    91F: yolo into production!

    samizdat.cc/cyoa

    yolo!

  • @bridgetkromhout #mvpbuzz

    Image credit: James Ernest

  • @bridgetkromhout #mvpbuzz

    The Wall of Confusion

    yolo nope

  • #mvpbuzz@bridgetkromhout

    for ops, dont tell devs: gl;hf!

    do: automate document

    share

  • #mvpbuzz@bridgetkromhout

    for devs, build for operability:

    observability, debuggability, reality

  • @bridgetkromhout #mvpbuzz

    Image credit: Vasa Museet

    probably fine

  • @bridgetkromhout #mvpbuzz

    hard problems & human factors

  • @bridgetkromhout #mvpbuzz

  • @bridgetkromhout #mvpbuzz

    communication & disconnects

  • @bridgetkromhout #mvpbuzz

    observability: answering questions we didnt know to ask

  • #mvpbuzz@bridgetkromhout

    understand your environment

  • #mvpbuzz@bridgetkromhout

    monitoring: the old way

  • @bridgetkromhout #mvpbuzz

    Monitorin

    g

    monitoring: the new way

  • @bridgetkromhout #mvpbuzz

    operational investments architecture observability

    culture

  • @bridgetkromhout #mvpbuzzImage 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

  • #mvpbuzz@bridgetkromhout

  • #mvpbuzz@bridgetkromhout

    Who owns your availability? The answer may surprise you!

    Image credit: Wikipedia

  • #mvpbuzz@bridgetkromhout

    silos are for grain

    not actually devops

    still computers

  • #mvpbuzz@bridgetkromhout

    In a world that celebrates pioneers be the settlers instead.

    Laura Bell (@lady_nerd)

  • @bridgetkromhout #mvpbuzz

    thanks!