~/talk

Rub-A-Dub Rubber Duck: Don't be Afraid to Debug!

Talkat DjangoCon US 2016 · 2016-07-17..07-22· [testing, developer-experience]
slides:none on file

Concrete debugging tactics and what they accomplish: read and parse Python error types to locate syntax runtime or logical faults, form and test explicit hypotheses, reproduce bugs on another machine, bisect by commenting or copying blocks, use print/pdb and linters (pyflakes pylint pep8) and the django-debug-toolbar for Django. Practical claim: explaining the problem out loud often reveals the fix — rubber duck debugging — and yes there are 200 rubber ducks on hand as a literal prompt to try it.

AI-written summary · about

  1. 0:00Start
  2. 4:56Debugging Strategies
  3. 5:19Error Messages
  4. 5:54Types of Error Messages
  5. 7:45Runtime Errors or Exceptions
  6. 9:17Common Types of Runtime Errors
  7. 9:56Using a Try and Accept Block
  8. 10:54Logical Errors
  9. 13:15Rubber Duck Debugging
  10. 14:38Come Up with Different Hypotheses
  11. 16:40Commenting Out Parts of Code
  12. 20:26Django Debug Tool
  13. 21:25Ask for Help
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.