Blog Stats
  • Posts - 36
  • Articles - 2
  • Comments - 17
  • Trackbacks - 14

 

Still not sure, but it can be learned

I doubt I actually had anything direct to do with it but something seems to have clicked with one of the junior developers. I'm pretty sure it wasn't something that I had done, other then figuring out an effective way to make him realize that it is in his best interest to not need me to walk him through things.

Nothing threatening, simply reminding him of a couple of thing:

  • I brought up that I had basically reached a plateau at the company, and that I was considering pursuing other opportunities (In fact I'm planing on talking to my boss about this tomorrow).  
  • I pointed out that if I or my boss have to walk them through the entire change, especially more then once, he wasn't really needed.
  • I fixed my attitude, unfortunately it involved "flipping the bozo bit" a little.
  • I had him answer all of the newer junior developers questions for a day.

Truthfully, I think it was the last two parts that made the difference. Both yesterday and today I was able to answer most of his questions by pointing him towards areas in the code which implemented similar functionality, and he was able to take it from there. Saving me the 10-30 minutes while I tried to explain how to implement it.

Now I just need to figure out how to get them to look beyond the source file they are working in at the time.


Feedback

No comments posted yet.


Post a comment





 

Please add 4 and 1 and type the answer here:

 

 

Copyright © Sean Lynch