3 ms·
> ways I've changed how I think about debugging: > bug is happening for a logical reason. there's no magic > be confident I can fix it > talk to someone Th
by wyldfire 10y ago
> ways I've changed how I think about debugging:
> bug is happening for a logical reason. there's no magic
> be confident I can fix it
> talk to someone
Those are good steps. IMO "talk to someone" is a critical step but you'll get wildly different results based on the quality of your reference resource. Ms Evans likely has access to someone (or is someone) who clearly knows their stuff. eBPF and other debugging features enabled by modern kernels are not well known by many developers.
But "be confident I can [diagnose] it" is a great first step and if you're persistent you will find the help you need. Sometimes it may take plumbing the depths of SO or IRC to find that help, but it's out there.
- phil21 10y agoFinding someone smart to talk to is important, and a lot of people fail at this step. I like to consider myself decently good at Linux troubleshooting and get asked a lot of questions most days. My sole piece of advice to folks looking for help: Be specific and help yourself. This means don't come and ask "why is my server slow?!" - it's coming into the conversation telling me the exact symptoms and what you've already tried and where you think the next steps are. If you are not at that point, you haven't put enough effort in for me to bother. Those are called paid consulting engagements. I would say most people get this wrong, and end up being ignored over time. The few folks who consistently give me interesting (even if they are trivial and I've seen it before) problems to help them with that they just need a bit of specific knowledge to solve? I look forward to them contacting me.
- soperj 10y agoYou don't even necessarily need to be talking to someone smart, or with any knowledge in the subject at all. Often times I'll figure something out just by explaining the problem to someone. The act of breaking down where the problems could be and showing someone what you've tried often leads to more ideas on how to fix it.
- AceJohnny2 10y agohence https://en.wikipedia.org/wiki/Rubber_duck_debugging https://en.wikipedia.org/wiki/Rubber_duck_debugging
- soperj 10y agoInteresting. Somehow i have no recollection of that term even after reading that book. It was a number of years ago now... perhaps it's time for a revisit.
- haimez 10y agoOnly for problems that were just out of reach for your normal mindset but still ultimately within your capability to handle. At a certain point, you need someone better than yourself to get better.
- aangjie 10y agoYeah.. I've solved quite a few problems by writing out a question on Stack overflow but found solutions/ideas before posting it.
- dtzWill 10y agoThis is good advice, and understanding this is the key to interacting with 'hacker' types. A good document to read or link from your project's "Contact" section is this FAQ on asking smart questions: http://www.catb.org/esr/faqs/smart-questions.html http://www.catb.org/esr/faqs/smart-questions.html It might not be quite right for your project but for many projects I've been part of it's pretty spot-on, at least as a starting point to avoid the worst of the 'bad' questions. Our IRC bot had a command for linking this to people, haha O:). Related: http://bash.org/?152037 http://bash.org/?152037
- baldfat 10y ago> Write out a good logical question for stackoverflow and answer my own question. 90% of the time!