Skip to content
0:00 / 0:00

#clojure#debugging#scientificmethod

Debugging with the Scientific Method - Stuart Halloway

ClojureTV

111K subscribers • 135 videos on Hallway

YouTube
  • Recommended by 5 people: 4 on Hacker News and 1 curated list.
  • A classic. People kept recommending it from 2015 to 2023.
  • Presented by Stuart Halloway, co-founder of Cognitect
  • An opinion. It argues one side of a question engineers disagree on.

Intermediate. Assumes working knowledge.

25K views10 years ago5 recommendations

Tools and practiceSoftware designDebuggingTestingFunctional programming

Stuart Halloway explains how to apply the scientific method to debugging by forming hypotheses, trying to falsify them, and keeping careful records.

About the speaker: Stuart Halloway (@stuarthalloway) is a founder and President of Cognitect (formerly Relevance). He is a Clojure committer, and a developer of the Datomic database. Stuart has spoken at a variety of industry events, including Strange Loop, Clojure/conj, EuroClojure, ClojureWest, SpeakerConf, QCon, GOTO, OSCON, RailsConf, RubyConf, JavaOne, and NFJS. Stuart has written a number of books and technical articles. Of these, he is most proud of Programming Clojure.

Why it's here

5 people recommend this

What people say. Highly recommended as a transformative talk on debugging mindfully to avoid confirmation bias and other cognitive traps.

seancon Hacker News • Recommends

On “Ask HN: How do you get better at debugging/finding a solution?”

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. link to this video

programming-talkscurated list on GitHubRecommends

Under “Debugging”

Debugging with the Scientific Method 00:49:08 by **Stuart Halloway** (2015)

chrislloydon Hacker News • Recommends

On “Metabase: Why we picked Clojure”

…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 link to this video…

griersonon Hacker News • Recommends

On “REPL + Debugger = REPLugger: a pleasant and scalable live code editor”

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

simon_accaon Hacker News • Recommends

On “Rich Hickey: Design in Practice”

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