Oh right, I guess I forgot the punchline to this one: with pair programming, the answer is "no time at all". The newcomer is paired with an experienced developer. They are immediately productive
Show this thread
How long does it take for a new developer to become productive on your codebase?
-
-
-
I suppose you might want to add a few days for the newcomer to set up their environment. That's probably a solo task for them and the wiki
Show this thread
End of conversation
New conversation -
-
-
Two programmers share a screen and work on a task together. They discuss the problem, pool ideas, agree on an approach, share information about the codebase, learn from one another, type the code out and commit it
-
I don't think it's a magic bullet but for quickly bringing a newcomer up to speed on a new codebase it's about the best approach I can imagine
End of conversation
New conversation -
-
-
Yes. Sometimes two keyboards and mice, sometimes one.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
How do you measure productivity in that context?
-
It's your codebase, define it how you like! But how about "It is no longer a net loss of resources to have this person working here"
- 1 more reply
New conversation -
-
-
instantly , because choding in a Team is mosltly communication.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.