I really like your last point, about not limiting what you're teaching to their context. As a junior dev myself, I find it so much more helpful when I can see the big picture or see WHY something is being done the way it is. Even if the why doesn't make sense to me at first, I can at least go along with it until it does make sense.
I also thankfully have a team that is willing to tell me the why. 😄
On the teams/jobs I have been though where I was never told the why, I get a little bit frustrated. It definitely makes it harder to put your head down and work if you don't know why you have to.
Anyway that was my little rant. Thanks for the article!
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.
I really like your last point, about not limiting what you're teaching to their context. As a junior dev myself, I find it so much more helpful when I can see the big picture or see WHY something is being done the way it is. Even if the why doesn't make sense to me at first, I can at least go along with it until it does make sense.
I also thankfully have a team that is willing to tell me the why. 😄
On the teams/jobs I have been though where I was never told the why, I get a little bit frustrated. It definitely makes it harder to put your head down and work if you don't know why you have to.
Anyway that was my little rant. Thanks for the article!