B) Interacting with programmers other than yourself.
On a more specific note:
Don’t work “around” problems. Identify what the problem actually IS and work backwards. When you try to take a step and find that you don’t know what step to take, or you’re stepping into something you don’t understand, go research and learn about it.
Learning how to read technical documentation is a valuable skill.
Recognize and challenge your assumptions. Which plays into working “around” problems. Do I know the error I’m researching came from this bit of code? Is this bit of code even running? Is the source file I’m looking at even part of the binary I’m running? Is the binary that’s running actually the one I’m trying to test?
A) Practice.
B) Interacting with programmers other than yourself.
On a more specific note:
Don’t work “around” problems. Identify what the problem actually IS and work backwards. When you try to take a step and find that you don’t know what step to take, or you’re stepping into something you don’t understand, go research and learn about it.
Learning how to read technical documentation is a valuable skill.
Recognize and challenge your assumptions. Which plays into working “around” problems. Do I know the error I’m researching came from this bit of code? Is this bit of code even running? Is the source file I’m looking at even part of the binary I’m running? Is the binary that’s running actually the one I’m trying to test?