Upgrade to Pro — share decks privately, control downloads, hide ads and more …

How to make better technical decisions

5ff4f1dbfd3888fba963ec7cc629e6f3?s=47 mthenw
November 18, 2019

How to make better technical decisions

5ff4f1dbfd3888fba963ec7cc629e6f3?s=128

mthenw

November 18, 2019
Tweet

More Decks by mthenw

Other Decks in Technology

Transcript

  1. @mthenw

  2. @mthenw

  3. @mthenw

  4. Maciej Winnicki Engineering Manager @ OLX @mthenw

  5. None
  6. None
  7. How to make better technical decisions

  8. @mthenw making decisions is hard

  9. @mthenw bounded rationality

  10. @mthenw for his pioneering research into the decision-making process within

    economic organizations Herbert A. Simon Nobel Prize in Economics in 1978
  11. @mthenw cognitive biases

  12. @mthenw for having integrated insights from psychological research into economic

    science, especially concerning human judgment and decision-making under uncertainty Daniel Kahneman Nobel Prize in Economics in 2002
  13. @mthenw The four villains of decision making

  14. @mthenw

  15. @mthenw narrow framing

  16. @mthenw confirmation bias

  17. @mthenw short-term emotion

  18. @mthenw overconfidence

  19. encounter a choice analyze options make a choice live with

    it @mthenw
  20. encounter a choice analyze options make a choice live with

    it narrow framing makes you miss options @mthenw
  21. encounter a choice analyze options make a choice live with

    it narrow framing makes you miss options the confirmation bias leads you to gather self-serving information @mthenw
  22. encounter a choice analyze options make a choice live with

    it narrow framing makes you miss options the confirmation bias leads you to gather self-serving information short-term emotion will often tempt you to make the wrong one @mthenw
  23. encounter a choice analyze options make a choice live with

    it narrow framing makes you miss options the confirmation bias leads you to gather self-serving information short-term emotion will often tempt you to make the wrong one you’ll often be overconfident about how the future will unfold. @mthenw
  24. @mthenw

  25. @mthenw Widen your options

  26. @mthenw multiple options reduce ego

  27. @mthenw knowledge

  28. @mthenw read books not blogs

  29. @mthenw conferences

  30. @mthenw

  31. @mthenw GitHub stars are

  32. @mthenw cognitive load

  33. @mthenw The Magical Number 7±2

  34. @mthenw

  35. @mthenw total cost of ownership

  36. @mthenw

  37. @mthenw

  38. @mthenw Reality-test your assumptions

  39. @mthenw experiment

  40. @mthenw ask an expert

  41. @mthenw RFCs

  42. @mthenw

  43. @mthenw

  44. @mthenw https://engineering.squarespace.com/blog/2019/the-power-of-yes-if

  45. @mthenw Attain distance before deciding

  46. @mthenw 10/10/10

  47. @mthenw Prepare to be wrong

  48. @mthenw post mortem

  49. @mthenw 5 whys

  50. @mthenw Users weren’t able to log in. Why? One auth

    header was missing. Why? We changed an auth library and the new one expected additional header. Why we didn’t know about the new header? Because we didn’t read the docs. Why we weren't able to quickly revert the false release? The release pipeline was failing. Why? Production credentials were not in the environment. Why? We wanted to speed up deployment and disable protection on the master branch. Why? We didn’t have hotfix process. Why we deployed the faulty release? There are no tests covering authentication. Why? It was written at the beginning of the project when we didn’t have time to write tests. Why code coverage tool didn’t catch it now? Because it was misconfigured.
  51. @mthenw pre mortem

  52. @mthenw widen your options reality-test your assumptions attain distance before

    deciding prepare to be wrong
  53. @mthenw Thanks!