This content originally appeared on Go Make Things and was authored by Go Make Things
Today, I wanted to share a simple formula I use and suggest to students for debugging broken code and effectively asking for help from others…
- This is the behavior I’m seeing (include a screenshot or video grab).
- This is the behavior I expected to see (include a screenshot, sketch, or video).
- Here’s what I’ve tried so far… {list of things}.
- Here’s a reduced test case that shows the problem.
I see a lot of requests for help online and on open source projects that say some variation of…
This isn’t working properly. Any idea why?
Without any explanation of what was expected, how what they’re seeing differs from it, or what they’ve already tried. That makes it incredibly hard for folks to help.
I can recall doing this kind of thing myself, and for me at least, I was a lot more junior in my career and generally didn’t even know where to look or what to ask for.
This four-step formula can often help you isolate the issue yourself by forcing you to break down your code into smaller steps. And if it doesn’t, you’ve given people a lot more information to help you get things sorted out.
🎉 New Year Sale! Now through the New Year, get 40% off your first year of Lean Web Club membership. Level-up as a developer. Click here to learn more.
This content originally appeared on Go Make Things and was authored by Go Make Things
Go Make Things | Sciencx (2024-12-18T14:30:00+00:00) A formula for debugging (and asking for help). Retrieved from https://www.scien.cx/2024/12/18/a-formula-for-debugging-and-asking-for-help/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.