Snipd home pageGet the app
public
Software Engineering Radio - the podcast for professional software developers chevron_right

Episode 512: Tim Post on Rubber Duck Debugging

whatshot 32 snips
May 17, 2022
Guest
Tim Post
49:52
forum Ask episode
view_agenda Chapters
auto_awesome Transcript
info_circle Episode notes
1
Introduction
00:00 • 4min
chevron_right
2
Is There a Problem Statement?
04:19 • 2min
chevron_right
3
The Process of Becoming Stuck
05:58 • 2min
chevron_right
4
Getting Out of the Loop Is Part of the Process
08:28 • 3min
chevron_right
5
Stack Overflow
11:56 • 3min
chevron_right
6
Stack Overflow
15:13 • 2min
chevron_right
7
Rubber Ducking
17:17 • 3min
chevron_right
8
How to Get to the End of a Problem
20:42 • 3min
chevron_right
9
Time Boxing
23:47 • 3min
chevron_right
10
Permission to Learn Rit - I Like That
26:45 • 5min
chevron_right
11
You're Not Meant to Solve the Problem
31:21 • 4min
chevron_right
12
Documentation
35:24 • 4min
chevron_right
13
Stack Overflow - A Nice Example Levelling the Playing Field of Mulles
39:16 • 2min
chevron_right
14
Code Review
41:37 • 3min
chevron_right
15
Code Reviews
44:32 • 2min
chevron_right
16
Is There a Rubber Duk for Rubber Bugging?
46:12 • 4min
chevron_right

Tim Post of echoreply.io discusses Rubber Duck Debugging, a way to wrap your head about problems and solutions. Host Felienne spoke with Post about Rubber Duck debugging, and how it can help you to find answers to complex problems.

HomeTop podcastsPopular guests