When I started a new job a few months ago, I entered an unfamiliar technology stack. Being the new guy on a project isn’t always easy. While a great team will make it easy to ask questions and learn, there seems to always be another problem to solve, or figure out how something works. This isn’t always solving a software bug, but instead often deals with coming to a greater understanding of how something works, to change the behaviour, or to duplicate it.
I have a great mentor, who knows many aspects of the code base. While he’s always willing to help, I like to reserve my questions for the tough questions. I’ve often found that when asking a colleague about a problem directly, I often wait until they’re at my desk before I rephrase the problem, and make that elusive link between what I think I know, and what the code is hiding. In other words, I can usually figure it out on my own, but I end up explaining it to someone else first.