debugging strategy: try out a new tool

(are there any major categories of tools I'm missing here?)

I'm also trying to figure out if there's more advice to give about how/when to try out new tools. right now I just have "try to do it when you're in a low-stress situation"

@b0rk pair with someone the first time if you possibly can - if they're more experienced (even a little bit) they can steer you clear of landmines, and if they're a newcomer like you, they can share your bewilderment. flip side: pair with people (even for a few minutes) if you're more experienced (even a little) and they're new - you'll probably learn something, their increased productivity will help you in the long run, and it's the kind thing to do.

@gvwilson thanks! this is so key, I can't believe I didn't think of it before :)

@b0rk is "draw diagrams" already in your list? I realize it's not an option for everyone, but I don't think I've ever debugged anything involving a complex data structure, back-tracking, or more than two agents exchanging messages without doodling something...

Follow

@gvwilson @b0rk whiteboarding the problem, then explain it to the rubber ducky step by step, flow by flow.

Sign in to participate in the conversation
mastod1.ddns.net

Mastod1 be nice. (sorry, closed for new registrations after a bunch of 'commercial/spamming' accounts jumped in - rule 3 on site)