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.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
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.