[philipov]

For me, it's tracing code/pipelines to figure out how a result was produced, typically in the context of that result being wrong somehow. Go To Definition is the most useful function in any editor.

I'm always surprised by how frequently colleagues don't think to do this and are left helpless.

[tibbar]

This reminds me of my further theory that everyone needs one 'heavy' and one 'light' technique. The 'light' technique is something that often works well as a heuristic and can be an effective unit of iteration. The 'heavy' technique is something that you can fall back on in difficult cases, something that can reliably solve hard problems, even if it's slow.

Sometimes the heavy technique is: just ask someone else. ;)

[TeMPOraL]

> Sometimes the heavy technique is: just ask someone else. ;)

For a lot of people I know, this is the light technique!

[jcmorrow]

I have both felt and seen this at work and I would add to this the meta-technique of binary search. Once it is added to your light and heavy technique you can solve what seems intractable at first glance faster than many people can even orient to the problem.

[ant6n]

For me the heavy technique is integer linear programming.

I’m not a software developer anymore.

[globnomulous]

Likewise. I don't always do this, but for problems that cost me much time or effort, I like to try to make sure that, if I wanted to reproduce a bug or problem, I'd know exactly how to write it.

Writing and understanding working correct software is, it turns out, a rather different skill from that of writing and understanding broken (or confusing) software. I'd also wager good money that the latter skill directly builds the former.

[cyberax]

Another example: debuggers.

It's amazing that a lot of new developers don't know how to use them at all! I'm not even talking about using the command line gdb, but just the basic "Set Breakpoint" feature and attaching to processes.