How long does it take for a new developer to become productive on your codebase?
Show this thread
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
-
-
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 threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
the experienced developers on our team often don't have the answers either though? like our legacy code base is on the order of 800k lines of PHP and JS and assorted garbage, most of it written long before anyone on our team was around
-
I'm sorry for not considering the case where nobody on your team is productive
- 1 more reply
New conversation -
-
-
Or, more likely, they are dragging down the productivity of the experienced dev with questions, while contributing nothing at all. I guess 50% of the time, they're freeing up experienced dev's previous pair to go solo and actually get something done...
-
Answering questions and distributing information is part of the duties of an experienced developer, this is how you get experienced developers in the first place
- 1 more reply
New conversation -
-
-
The newcomer still takes nonzero time to ask questions,though. Technically, the time before first-productive-moment is much shorter, but that doesn't seem like a fair metric. Still, it's like getting the best possible documentation and a perfectly-tailored tutorial. Hard to beat.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Former HP BP Analyst
#AuntieWendySez YES! And? Not a new concept! FOREVER a good way (for documentation + testing + training) to task newbie w/picking brains. The entrenched (esp. devs/engineers!) HATE IT;(QUESTIONING THEIR WORK/assumptions!) but often bugs/implications found!
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.