A Working Definition of Tested Code
December 29, 2022Matter and Why It Matters
December 29, 2022Working with a team that has recently added more people to its project caused me to evaluate how I answer questions. I have been helping with on-boarding and as I walk people through how we do things they naturally have questions. Questions tend to be complex when asked by someone with a level of understanding. If there is little understanding there tends to be fewer questions because they have less context to frame a question.
I have found if I start by giving the high-level answer (the “stupid” one that requires the least amount of understanding) I get feedback that helps narrow the answer to the level of understanding they have.
I have been in the position of being the new person and it is difficult to get over the fear of looking incompetent by asking a “stupid” question. However, I have found that getting over that early hump gets you further faster.
Giving “stupid” answers breaks people out of the fear of incompetency and gives them a chance to show competence or to learn what they need to with lessened anxiety of being looked down upon.
I will be starting this coming year with “stupidity” with the express purpose of becoming smarter while maintaining my proclivity for “stupid” answers and questions.