Re:Ask HN: How do you define a junior developer?
by allsystemsgo on Thursday September 22, 2016 @11:25AM
(#12557467)
A good junior dev asks lots of questions and eventually gets tasks done assigned to him or her on a somewhat reasonable timeline. Tasks get done progressively faster as they grow and they ask fewer and fewer questions (and usually said questions are unique, so no repeat questions for the most part).
[ Parent
| on HN ]
Re:Ask HN: How do you define a junior developer?
by ebiester on Thursday September 22, 2016 @12:37PM
(#12558055)
That's a cultural thing. On a team of mine, I would worry if people weren't asking as many questions. It means they aren't finding the problems and pitfalls.
The questions should change, to be sure, but they shouldn't diminish unless we're not throwing progressively more complex tasks at them.