Sure. Spend a day learning how to use a debugger, and force yourself to use it until it feels natural. In the most common cases, the bug is in code on your computer, even if it's buried deep in some dependency. Even if you're working on a distributed system, you should have a local test environment and hopefully some sort of tracing capabilities. With a properly configured debugger, you should be able to quickly find the source of most problems.

After replicating a bug, I usually follow a process that looks roughly like this. I try each step, and if it's not resolved by then, I move onto the next.

1) Examine git log to hopefully determine which commit introduced the bug, in order to narrow the search space

2) Set breakpoint when the bug becomes observable, attach debugger and identify root cause of bug.

3) Verify that any function calls to dependencies are correct according to documentation, and any conditionals are working as expected (double check logic too)

4) Try a bunch of google searches

5) Read dependency documentation more closely, and read its code on GitHub to understand how it works

6) Ask for help in an IRC channel if available

7) Re-evaluate priorities