Skip to content
HHackerTube.videoSurprise me

Debugging with the Scientific Method - Stuart Halloway

Debugging with the Scientific Method - Stuart Halloway on HackerTube: recommended by 4 Hacker News commenters across 4 separate months, 2015–2023.

ClojureTV

talk · intermediate · evergreen

Open on YouTube

Stuart Halloway of Cognitect argues for debugging with the scientific method: form hypotheses, try to falsify them, and write everything down. The talk is given to the Clojure community but applies to any language.

Why Hacker News recommends it

HN recommends it as a talk that changed how people debug, worth rewatching periodically.

people recommended it
4
separate months
4
strong recommendations
1
discussed on HN
2015–2023
“changed how I debug problems. I try to watch it once every year or two.”
— seanc, Sep 2022, in “Ask HN: How do you get better at debugging/finding a solution?”

What HN commenters said

4 Hacker News comments link this video. Each one links back to its thread.

seancSep 2022Strongly recommends

This talk, "Debugging with the Scientific Method" changed how I debug problems. I try to watch it once every year or two. tl;dr, when debugging people naturally form a hypothesis about what is going wrong and then set about gathering evidence to support or refute that hypothesis. When you do so unconciously you are very prone to biases of all sorts, most importantly confirmation bias. When you do so mindfully, and Write It All Down then you are much more likely to a) come up with an evidence gathering exercise which will usefully falsify your hypothesis, and b) respect the gathered evidence, reject the now false hypothesis, and move on to a new one. ▶ this video

in “Ask HN: How do you get better at debugging/finding a solution?” · View on HN

simon_accaMay 2023Recommends

Stu Halloway (also a member of the Clojure core team) has a couple of great talks on using the scientific method in programming: ▶ this video [link]

in “Rich Hickey: Design in Practice” · View on HN

griersonSep 2018Recommends

Stuart Halloway from the Clojure community has some great a talks using the REPL to debug. Links: Debugging with the Scientific Method - Stuart Halloway ( ▶ this video ) REPL DEBUGGING: NO STACKTRACE REQUIRED ( [link] ) scope-capture ( [link] )

in “REPL + Debugger = REPLugger: a pleasant and scalable live code editor” · View on HN

chrislloydDec 2015Recommends

I think your criticisms are definitely valid. The learning curve is steep (intentionally so) but definitely worth it. Your programs will become more reliable and you'll get more done as a consequence. Please push through! The error messages are terrible, and there are a lot of ongoing conversations about them at the moment in the Clojure community[1]. The Clojure[script] toolchain does tend to be all-in but there's work happening now to break that up — stay tuned. StackOverflow and the Clojure Slack channel also full of people who know how to fix issues :) Stick with it, when you'll have an "ah-ha!" moment soon enough! [1]: This talk is a good backstory as to why the errors are so bad, and useful no matter what language you use ▶ this video

in “Metabase: Why we picked Clojure” · View on HN

Topics & tags

Testing, debugging & developer toolsFunctional programmingdebuggingscientific methodclojurehypothesis testingstuart halloway