4 ms·
I'd suggest three things: 1 - subscribe to http://codeyear.com/ http://codeyear.com/ (or similar) 2 - take a couple of hours every weeks to do pair-work (not
by thibaut_barrere 15y ago
I'd suggest three things:
1 - subscribe to http://codeyear.com/ http://codeyear.com/ (or similar)
2 - take a couple of hours every weeks to do pair-work (not only programming, but also estimating etc) so he get a better idea of the daily tradeoffs
3 - let him pick a couple of screencasts at times (see http://www.learnivore.com/ http://www.learnivore.com/ for instance) to follow from a high level view at his own pace
If you do 2, be ready to question your own assumptions; you'll likely get "fresh" questions that will teach you just as much as him.
- sagacity 15y agoPoint #2 - truly well-said. >If you do 2, be ready to question your own assumptions; you'll likely get "fresh" questions that will teach you just as much as him. Bingo, again. Spot on. Having lived on both sides of the equation (hand-coder - 20+ years ago, CXO-type since then,) I can attest to the validity of this whole heartedly.