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

The Scientific Method of Troubleshooting

Sponsored · Ship Features Fearlessly Turn features on and off without deploys. Used by thousands of Ruby developers. →
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
1B+ /day規模のログを管理する技術
Avatar for Broadleaf Co., Ltd. broadleaf
0
130
Haskell/Servantを通してWebミドルウェアを捉え直す
Avatar for pizzacat83 pizzacat83
0
400
なぜ関数型プログラミングで「型」と「証明」が語られるのか #fp_matsuri
Avatar for Takuma Kajikawa kajitack
3
530
Language Server 使ってる？ 〜VSCode と Zed の場合〜 / Are you using a Language Server? ~For VS Code and Zed~
Avatar for NAGATA Hiroaki handlename
0
830
SREの積み重ねがAI駆動開発のガードレールになった ― 7つの実践/SRE Guardrails The 7
Avatar for TomoyaKitaura tomoyakitaura
7
2.1k
「なぜそう決めたのか」を残し続ける仕組み ― Notion AI カスタムエージェント × Slack連携による設計判断の自動記録 - NIKKEI Tech Talk #47
Avatar for ニフティ株式会社 niftycorp
PRO
0
250
技術記事、 専門家としてのプログラマ、 言語化
Avatar for Koutarou Chikuba mizchi
14
7.3k
地域 SRE コミュニティ最前線 - ホンマでっかSRE勉強会
Avatar for tk3fftk tk3fftk
0
120
Developing with AI Agents — Codex, Claude Code & Cowork Practical Guide
Avatar for Daisuke Masuda x5gtrn
PRO
0
1.3k
Performance Engineering for Everyone
Avatar for Elena Tanasoiu elenatanasoiu
0
260
例外の正しい扱い方 そのエラー try-catchして大丈夫？
Avatar for Watanabe Jin jinwatanabe
0
340
才能？センス？知らん、 続けたもん勝ちだ。-- 結婚・出産・癌を越えてなお、私がプロダクトを創り続ける理由
Avatar for 16bit_idol 16bitidol
2
780

Featured

See All Featured
<Decoding/> the Language of Devs - We Love SEO 2024
Avatar for Nikki Halliwell nikkihalliwell
1
270
個人開発の失敗を避けるイケてる考え方 / tips for indie hackers
Avatar for panda_program panda_program
123
22k
SEOcharity - Dark patterns in SEO and UX: How to avoid them and build a more ethical web
Avatar for Sara Fernández Carmona sarafernandez
0
220
How to Talk to Developers About Accessibility
Avatar for Jason CranfordTeague jct
2
280
Jess Joyce - The Pitfalls of Following Frameworks
Avatar for Tech SEO Connect techseoconnect
PRO
1
180
The Psychology of Web Performance [Beyond Tellerrand 2023]
Avatar for Tammy Everts tammyeverts
49
3.5k
Templates, Plugins, & Blocks: Oh My! Creating the theme that thinks of everything
Avatar for Michelle Schulp Hunt marktimemedia
31
2.8k
Docker and Python
Avatar for Tania Allard trallard
47
3.9k
The Invisible Side of Design
Avatar for Vitaly Friedman smashingmag
301
52k
The SEO identity crisis: Don't let AI make you average
Avatar for Varn varn
0
510
Visualization
Avatar for Eitan Lees eitanlees
152
17k
Designing Experiences People Love
Avatar for Jonathan Moore moore
143
24k

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