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

The Scientific Method of Troubleshooting

98bcb9a1d462d6ea907fade0d601ea04?s=47 Blithe Rocher
August 02, 2014
Programming
0
84

The Scientific Method of Troubleshooting

This version of the talk was presented at eurucamp 2014.

98bcb9a1d462d6ea907fade0d601ea04?s=128

Blithe Rocher

August 02, 2014
Tweet

More Decks by Blithe Rocher

See All by Blithe Rocher
Microservices War Stories
98bcb9a1d462d6ea907fade0d601ea04?s=48 blithe
1
140
The Scientific Method of Troubleshooting
98bcb9a1d462d6ea907fade0d601ea04?s=48 blithe
1
170
The Scientific Method of Troubleshooting
98bcb9a1d462d6ea907fade0d601ea04?s=48 blithe
2
570

Other Decks in Programming

See All in Programming
デュアルトラックアジャイル × Agile Testingから 見えてきたQAのミライ
F0a8d07597a19192791bf663504d2a17?s=48 atamaplus
0
480
【Qiita Night】新卒エンジニアによるSwift6与太予想
3fc2c76b81e2acd1a263f30db01a248a?s=48 eiji127
0
190
Oculus Interaction SDK 概説 / xrdnk-caunity-LT4
270b0c7883545117a9a618dc7ca7cc83?s=48 xrdnk
0
280
NieR Re[in]carnationにおけるUnityアニメーション活用術
Ea7f7af2b8f62b7abf8cf0c9af394cc0?s=48 applibot
1
940
クリエイティブ系のウェブサイト制作で役立つCSS技法 / CSS for develop creative website
4b7124f2f5989173c8ce3b0934817a32?s=48 clockmaker
2
1.7k
SRE bridge the gap: Feature development to Core API / 機能開発チームとコアAPIチームの架け橋としてのSRE
5520f7e791c2f63da603f6b089b07c6f?s=48 kenzan100
1
520
CLI構築のススメ
1bf2570004ba1a6261e5a252deef2719?s=48 nyankotaro
1
260
Architectural practices for greater scalability and innovation
C8709f1d7ae6cc5f057e37e01d6e28db?s=48 otaviojava
0
120
読みやすいコードを書こう
A7048be18b1c2e712e5b564b1adb1f7e?s=48 yutorin
0
440
OSS Forward Workshop
011714704c4a925e542d426d4cdaa4e3?s=48 giginet
2
330
You CANt teach an old dog new tricks
Bd5b8981a308c94b642befb656d8cf8f?s=48 michaelbukachi
0
120
TextPruner による大規模言語モデルの軽量化 / Large language model pruning using TextPruner
0c60fb0fa226940755988c40b28e0c19?s=48 misawann
0
330

Featured

See All Featured
CoffeeScript is Beautiful & I Never Want to Write Plain JavaScript Again
5b9fe87ec1faa67a4599782930f45ec9?s=48 sstephenson
151
12k
ReactJS: Keep Simple. Everything can be a component!
Af6a12710770ad9a7cfd08c97efd40d3?s=48 pedronauck
655
120k
No one is an island. Learnings from fostering a developers community.
6bb82b13cda86d3b821fa44100335ddf?s=48 thoeni
9
1.1k
Designing for Performance
245cee81a9c424266e5e401d844ea881?s=48 lara
596
63k
Refactoring Trust on Your Teams (GOTO; Chicago 2020)
A9a491b0fcbe0fbce3d64063a37add99?s=48 rmw
19
1.4k
Thoughts on Productivity
A16eb159db895e3b01d3dc95767ad595?s=48 jonyablonski
43
2.2k
Designing the Hi-DPI Web
C157b16234f1e75e8eac3698c1d4414a?s=48 ddemaree
272
32k
Designing with Data
F57e2136eb9895eb95ff5dc8a1c02677?s=48 zakiwarfel
91
3.9k
Stop Working from a Prison Cell
C1daf20e5c49ff910745198ef9869ac2?s=48 hatefulcrawdad
261
17k
Navigating Team Friction
245cee81a9c424266e5e401d844ea881?s=48 lara
175
11k
The Invisible Side of Design
B3d6434763caa0ef5dc4b792662c49f7?s=48 smashingmag
289
48k
Support Driven Design
1519587b1a0febb658c36c94f6272b0d?s=48 roundedbygravity
86
8.5k

Transcript

  1. The Scientific Method of Troubleshooting

  2. @blithe

  3. Big Nerd Ranch Atlanta, Georgia

  4. Scientist

  5. PhD in Physical Chemistry

  6. Physics

  7. Chemistry

  8. 6 Years!

  9. Experiments

  10. Scientific Method

  11. Developer < >

  12. StackOverflow

  13. Problem solved?

  14. Learn anything?

  15. Most Important Part

  16. Scientific Method

  17. Set of Techniques For Acquiring Knowledge

  18. Methodical

  19. Systematic

  20. “Has anyone seen string interpolation fail?”

  21. Define the Problem

  22. Expected behavior? ! ! !

  23. Expected behavior? ! Actual behavior? !

  24. Expected behavior? ! Actual behavior? ! Criteria for success?

  25. Do Your Research

  26. Know your environment

  27. Read the literature

  28. Discussions

  29. Make it fail!

  30. Establish a Hypothesis

  31. Design the Experiment

  32. Divide and conquer!

  33. Limit the variables

  34. Try something weird

  35. None

  36. Hierarchy of Blame

  37. Gather Data

  38. Current status?

  39. Read the error message!

  40. Analyze Your Results

  41. Problem solved? ! Learn anything?

  42. Understand the Why

  43. Future Experiments

  44. Embrace the Success

  45. Keep a Good Lab Notebook

  46. None

  47. You won’t remember

  48. Logs aren’t enough

  49. Commit Messages

  50. Update the Docs

  51. Contribute

  52. None

  53. Share the Knowledge

  54. Thanks! @blithe