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

The Scientific Method of Troubleshooting

Avatar for Blithe Rocher Blithe Rocher
August 02, 2014
Programming
150
0

The Scientific Method of Troubleshooting

This version of the talk was presented at eurucamp 2014.

Avatar for Blithe Rocher

Blithe Rocher

August 02, 2014

More Decks by Blithe Rocher

See All by Blithe Rocher
Microservices War Stories
Avatar for Blithe Rocher blithe
1
220
The Scientific Method of Troubleshooting
Avatar for Blithe Rocher blithe
1
250
The Scientific Method of Troubleshooting
Avatar for Blithe Rocher blithe
2
710

Other Decks in Programming

See All in Programming
ふつうのFeature Flag実践入門
Avatar for irof irof
7
3.7k
Semantic Version 単位で戦略を柔軟に変えて、パッケージアップデートを自動化する
Avatar for daitasu daitasu
0
220
ユニットテストの先へ：テスト技法で要求・仕様を整理するJava開発実践 / Beyond_Unit_Testing_Practical_Java_Development_Techniques_for_Organizing_Requirements_and_Specifications
Avatar for SHIMANE, Yoshikazu shimashima35
0
390
Contextとはなにか
Avatar for chiroruxx chiroruxx
1
290
正しくソフトウェアを作る、前提を疑うための認知の視点 / doubt-premise
Avatar for MinoDriven minodriven
20
6.5k
[2026年度第1回ORセミナー] 計画最適化ベンチャーと競技プログラミング人材
Avatar for terry-u16 terryu16
0
260
Swiftのレキシカルスコープ管理
Avatar for kntk kntkymt
0
220
「AIで開発し、AIを届ける」をEvalでつなぐ 〜AIネイティブに始めるプロダクト開発の実践〜 / Connecting "Develop with AI, deliver AI" with Eval
Avatar for r-kagaya rkaga
4
4.9k
The Arts and Crafts of Work in the AI Era — Toward Mastery in Software Development
Avatar for Yoshihito Kuranuki / 倉貫義人 kuranuki
1
750
例外の正しい扱い方 そのエラー try-catchして大丈夫？
Avatar for Watanabe Jin jinwatanabe
0
210
Developing with AI Agents — Codex, Claude Code & Cowork Practical Guide
Avatar for Daisuke Masuda x5gtrn
PRO
0
1.3k
Dataformのリポジトリを立ち上げるときにまずやること / dataform-day0-2026
Avatar for snhryt snhryt
0
150

Featured

See All Featured
Leveraging LLMs for student feedback in introductory data science courses - posit::conf(2025)
Avatar for Mine Cetinkaya-Rundel minecr
1
280
Agile Actions for Facilitating Distributed Teams - ADO2019
Avatar for Mark Kilby mkilby
0
200
Navigating the Design Leadership Dip - Product Design Week Design Leaders+ Conference 2024
Avatar for Andy Polaine apolaine
1
340
Ten Tips & Tricks for a 🌱 transition
Avatar for Manu Carrasco Molina stuffmc
0
130
Exploring the Power of Turbo Streams & Action Cable | RailsConf2023
Avatar for Kevin Liebholz kevinliebholz
37
6.5k
Beyond borders and beyond the search box: How to win the global "messy middle" with AI-driven SEO
Avatar for David Carrasco davidcarrasco
3
150
Into the Great Unknown - MozCon
Avatar for Noah Learner thekraken
41
2.6k
CoffeeScript is Beautiful & I Never Want to Write Plain JavaScript Again
Avatar for Sam Stephenson sstephenson
162
16k
Accessibility Awareness
Avatar for Sarah Abderemane sabderemane
1
140
<Decoding/> the Language of Devs - We Love SEO 2024
Avatar for Nikki Halliwell nikkihalliwell
1
240
First, design no harm
Avatar for Per Axbom axbom
PRO
2
1.2k
Chasing Engaging Ingredients in Design
Avatar for Sebastian Deterding codingconduct
0
220

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