We are asked questions every day.  Also, part of the expectation of our job is that we will have an answer.  However, we do not have to answer immediately.  It is acceptable to say that I can find that out or let me get back to you for that answer.  Do not rush into a solution when you have time to think through a response or ping others.

Experience Is Half The Battle

Experience is one of the best teachers.  When we are not clear on an answer, we often know where to start looking.  This approach may utilize search engines, reference materials, or co-workers.  The method we take is not as important as the results we get.  Therefore, do not hesitate to take advantage of every source available in pursuing a solution.  Proper research takes time, so buy some of that resource with a simple answer like “let me get back to you.”

Correct Later Is Better Than Partial Sooner

I know I jump to an answer too quickly at times.  It is sort of an 80-20 rule I have to fight against.  When I am fairly confident in a solution, I have times where I have been too quick to provide that one rather than utilize the option to confirm my instincts.  This situation is not uncommon in my experience.  We want to be able to help sooner rather than later.  However, that inclination can sometimes lead us to provide a partial or incorrect solution too quickly rather than a complete solution later.  This approach can cause communication and expectation setting problems.  Thus, it is better to bite your tongue or provide an answer that you think you know a solution, but you want to verify it.  Patience and the “I’ll find that out” response happen to be signs of experience.  There is a reason we have a saying that refers to fools rushing in.

We Have a Lot To Provide

All of this steady work on becoming a better developer leads to being a better source for solutions.  We should have confidence in our ability to research and learn new things.  That leads to us being an excellent resource for answering questions and solving problems even if we do not always provide an immediate response.  We know it takes time to learn and improve.  Use that knowledge to slow your approach, say you will find that out, and allow yourself to craft the best answer possible.

Episode Challenge: Spend the next week listening for problems to solve in your daily conversations.  Maybe pick one and see if you can provide a solution.

Read more about advancing your career.

Rob Broadhead

Rob is a founder of, and frequent contributor to, Develpreneur. This includes the Building Better Developers podcast. He is also a lifetime learner as a developer, designer, and manager of software solutions. Rob is the founder of RB Consulting and has managed to author a book about his family experiences and a few about becoming a better developer. In his free time, he stays busy raising five children (although they have grown into adults). When he has a chance to breathe, he is on the ice playing hockey to relax or working on his ballroom dance skills.

Leave a Reply