Upgrade to Pro — share decks privately, control downloads, hide ads and more …
Sign up for free

The Scientific Method of Troubleshooting

Avatar for Blithe Rocher Blithe Rocher
August 02, 2014
Programming
160
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
260
The Scientific Method of Troubleshooting
Avatar for Blithe Rocher blithe
2
720

Other Decks in Programming

See All in Programming
速く作れる。その次は、速く確かめられる開発へ 〜AIネイティブ開発を支える、Shift Down〜 / Can build fast. Next, moving to development where we can verify fast.
Avatar for r-kagaya rkaga
8
5.6k
モデルのリファクタリングが難しいと思ったら、そもそも複雑だったのはビジネス仕様だった ? / is-the-business-domain-the-real-complexity
Avatar for hatsu hatsu38
0
450
設計次第でAIコードの読む量は減らせる / designing-for-code-reading
Avatar for MinoDriven minodriven
34
16k
The Rails Doctrine Decade
Avatar for Koichi ITO koic
2
550
RAG の “R” を Swift で覗いてみる 〜「意味から探す」検索の仕組み〜
Avatar for Nao-RandD nao_randd
0
130
mrbgem 三角測量 開発
Avatar for ogom ogom
0
220
最近”作らせてる” ローカルAIアプリの話
Avatar for ITO Akihiro akit37
0
430
動作中のプログラムの中身をリアルタイムに覗く / Realtime Debugger for CSharp with Roslyn
Avatar for Prota prota
1
1.8k
R8 の設定見直しでアプリサイズ削減
Avatar for ANDPAD inc andpad
0
190
KiroのSpecで「五目並べ」を作ってみる
Avatar for Satoshi Kaneyasu satoshi256kbyte
1
360
CodeRabbitの効果検証と過ごしてみた3ヶ月
Avatar for armondando armondando
0
210
Starting & Sustaining Code-Based E2E Testing for Non-Coding QA Teams( #jasstniigata )
Avatar for teyamagu teyamagu
PRO
1
950

Featured

See All Featured
Avoiding the “Bad Training, Faster” Trap in the Age of AI
Avatar for Mike Taylor tmiket
0
270
Why Mistakes Are the Best Teachers: Turning Failure into a Pathway for Growth
Avatar for Umar Saidu Auna auna
0
320
Evolution of real-time – Irina Nazarova, EuRuKo, 2024
Avatar for Irina Nazarova irinanazarova
9
1.6k
How To Stay Up To Date on Web Technology
Avatar for Chris Coyier chriscoyier
790
250k
Understanding Cognitive Biases in Performance Measurement
Avatar for Philip Tellis bluesmoon
32
3k
Money Talks: Using Revenue to Get Sh*t Done
Avatar for Nikki Halliwell nikkihalliwell
0
520
Designing for humans not robots
Avatar for Tammie Lister tammielis
254
26k
RailsConf 2023
Avatar for Aaron Patterson tenderlove
30
1.6k
Reflections from 52 weeks, 52 projects
Avatar for Jefferson Lam jeffersonlam
356
21k
Mobile First: as difficult as doing things right
Avatar for Swwweet swwweet
225
10k
Documentation Writing (for coders)
Avatar for Carmen Chung carmenintech
77
5.6k
Information Architects: The Missing Link in Design Systems
Avatar for Michelle Chin soysaucechin
1
1.2k

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