DEV Community


Discussion on: Good Programmer vs Average Programmer - and, Why Asking questions and Paying attention to Details matters.

190245 profile image

I'm sorry, but "don't commit time" sounds like bad advice.

We have a junior dev that refuses to give story point estimates & his reasoning is always "I need some time for analysis first" (even when seniors & PMs have broken the task into simple statements that require no thought).

That dev has been parked on our documentation project, and if that ever dries up, they'll be fired.

A good developer needs to learn how to forecast time, manage expectations & deliver on time.