Getting Unstuck
summary
Four concrete debugging cases show what actually worked: a factory error caused by two unkeyed array values producing SQL "unknown column 0"; a package hang traced by removing layers to a ZeroMQ client failing due to file permissions; a PHPUnit test silently passing because a GET was used instead of POST; and a CSV import that fails because PHP's fileinfo (libmagic) classifies CSV only when there are three lines (trailing newline) present discovered by stepping through code and using Beyond Compare to diff CSV hex. Tools used: Laravel, PHPUnit, Xdebug, fileinfo, Beyond Compare; fixes include formatting, permission change, method correction, template and validation message updates.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 3:51First bug and formatting
- 9:29Second bug and abstraction
- 12:57Third bug and human error
- 16:50Fourth bug and deep dive
- 25:02Eight key principles
- 29:20Final thoughts and Q&A
related talks
33mCode Archaeology: Becoming Indiana Jones
17mWorking Smarter: 5 Steps To Getting Unstuck
38mFrom the Exorcist to Hercule Poirot
24mThe Scientific Method of Troubleshooting
20mDebugging: Techniques for Uncertain Times
47mHow to Un-Flake Flaky Tests- a New Hire's Toolkit
38mGetting Unstuck: Strategies For Solving Difficult Problems
49mDebugging with the Scientific Method