Goodbye Print Statements, Hello Debugger!
summary
Major claim: replacing print statements with debuggers speeds development. Demonstrations use a small Flask app hit by curl that drops into breakpoint() in Python 3.7, into pdb or ipdb with syntax highlighting and tab completion, and into VS Code’s graphical debugger with hover variables and a debug console. Poll shows most still use prints, ~10% use pdb/ipdb and ~20% use IDE debuggers. Practical tips include a Jupyter cell debugger preview and a pre-commit hook to block breakpoints so they don’t ship.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 2:58Why Debuggers
- 5:51Debugger
- 9:10Types of debuggers
- 10:37Breakpoints
- 14:05CLI Debugging
- 18:42IDE Debugging
- 19:38VS Code Debugging
- 22:54When do you use what tool
- 23:36Tips and tricks
- 26:51Precommit hooks
related talks
31mGoodbye Print, Hello Debugger!
28mGoodbye Print, Hello Debugger!
51mProgramming is Debugging
29mLiberating the Debugging Experience with the GDB Python API
15mGive me 15 minutes & I'll change your view of GDB
40mSo you think you can PDB?
05mDebugging, a step away from the console
37mThe Bright Future of Debuggers: Challenges and Opportunities