Great read, thanks for this article. Reminds me to ask more questions, even though one might be a bit experienced. But I guess we are never experienced enough so that we know all the answers.
I loved how Scott Hanselman tweeted lately, that he asks what certain abbreviations mean in a meeting, because the junior developers are afraid to ask (twitter.com/shanselman/status/9032...). I also had to ask for the meaning of an abbreviation in a sprint meeting a few days ago and nobody got mad.
Still I want to emphasize your ideas regarding doing prior research and providing proper context. Lots of questions can be answered with the help of Google, Wikipedia and/or StackOverflow. But of course there are many particular company structures or unique code bases that just can't be clarified without another colleague.
Again, great article! :)
Take care,
Patrick
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hey Sahil,
Great read, thanks for this article. Reminds me to ask more questions, even though one might be a bit experienced. But I guess we are never experienced enough so that we know all the answers.
I loved how Scott Hanselman tweeted lately, that he asks what certain abbreviations mean in a meeting, because the junior developers are afraid to ask (twitter.com/shanselman/status/9032...). I also had to ask for the meaning of an abbreviation in a sprint meeting a few days ago and nobody got mad.
Still I want to emphasize your ideas regarding doing prior research and providing proper context. Lots of questions can be answered with the help of Google, Wikipedia and/or StackOverflow. But of course there are many particular company structures or unique code bases that just can't be clarified without another colleague.
Again, great article! :)
Take care,
Patrick