Skip to content
HomeVideos
AllLongsCategoriesPlaylists
BooksBlogsPodcasts
HistoryListsWatch laterLiked videosFollowing

The videos, books, blogs and podcasts Hacker News keeps recommending, all in one place.

VideosBooksBlogsPodcastsAboutPrivacySettings

Data from Hacker News, HackerTube, HackerBooks, HackerBlogs and Open Library. Credits · Not affiliated with Y Combinator.

HomeVideosBooksBlogsPodcasts
Ctrl K

    Debugging with the Scientific Method - Stuart Halloway

    ClojureTV

    4 HN recommenders · recommended in 4 months, 2015–2023

    YouTube

    49:09 · 25K views · Nov 17, 2015

    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.

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

    Software Engineering & LanguagesTesting, debugging & developer toolsFunctional programming
    1. 33:06
      REBL - Stuart HallowayClojureTV25K views • 7 years ago
    2. 1:02:26
      Solving Problems the Clojure Way - Rafal DittwaldClojure/north87K views • 7 years ago
    3. 41:09
      ClojureScript for Skeptics - Derek SlagerClojureTV72K views • 10 years ago
    4. 36:14
      Barliman: trying the halting problem backwards, blindfolded - William Byrd, Greg RosenblattClojureTV7.9K views • 9 years ago
    5. 1:03:29
      Maybe Not - Rich HickeyClojureTV181K views • 7 years ago
    6. 50:01
      Simplicity Ain't Easy - Stuart HallowayClojureTV24K views • 13 years ago
    7. 1:07:22
      Invited Talk - Guy SteeleClojureTV39K views • 9 years ago
    8. 1:14:52
      Effective Programs - 10 Years of Clojure - Rich HickeyClojureTV176K views • 9 years ago
    9. 45:31
      Bruce Hauman - Developing ClojureScript With FigwheelClojureTV56K views • 11 years ago
    10. 40:00
      "Agility & Robustness: Clojure spec" by Stuart HallowayStrange Loop Conference25K views • 10 years ago
    11. 47:17
      John Hughes - Testing the Hard Stuff and Staying SaneClojureTV39K views • 12 years ago
    12. 43:04
      "Stop Writing Dead Programs" by Jack Rusher (Strange Loop 2022)Strange Loop Conference468K views • 4 years ago
    13. 36:42
      Bottom Up vs Top Down Design in Clojure - Mark BastianClojureTV29K views • 10 years ago
    14. 1:01:39
      "Simple Made Easy" - Rich Hickey (2011)ClojureTV434K views • 5 years ago
    15. 1:16:14
      Spec-ulation Keynote - Rich HickeyClojureTV136K views • 9 years ago
    16. 58:39
      Tim Ewald - Clojure: Programming with Hand ToolsClojureTV48K views • 12 years ago
    17. 36:31
      Hey Underscore, You're Doing It Wrong!InfoQ141K views • 13 years ago
    18. 6:22
      Interactive programming Flappy Bird in ClojureScriptBruce Hauman55K views • 12 years ago
    19. 37:15
      Stuart Halloway - Narcissistic DesignReaktor29K views • 9 years ago
    20. 53:56
      Expert to Expert: Rich Hickey and Brian Beckman - Inside Clojurejasonofthel33t119K views • 13 years ago

    4 comments from Hacker News

    1. @seancSep 2022· in “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. this video

      Strongly recommendsView on HN
    2. @chrislloydDec 2015· in “Metabase: Why we picked Clojure”

      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

      RecommendsView on HN
    3. @griersonSep 2018· in “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 ( this video ) REPL DEBUGGING: NO STACKTRACE REQUIRED ( [LINK] ) scope-capture ( [LINK] )

      RecommendsView on HN
    4. @simon_accaMay 2023· in “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: this video [LINK]

      RecommendsView on HN