DEV Community

Discussion on: How do you estimate time required for assigned task?

Collapse
 
imben1109 profile image
Ben

Why?

Collapse
 
jonrandy profile image
Jon Randy 🎖️

Over many, many years of being a developer, I've come to realise it is basically a waste of time. If you are coding something new, it is largely a total unknown and trying to break it down up front and estimate how long it will take is generally futile. Coding something is mostly an organic process that, in my experience, changes all the time - and rapidly. More often than not you find your initial idea wasn't correct and the correct, or better way is much longer or possibly shorter.

Spending time upfront trying to break a task down and put a time on it merely adds time to the total - time that is largely worthless and would have been better spent just getting on with it.

However, it IS usually possible to give a rough completion time once you are at a point where you're pretty confident your solution is working

Thread Thread
 
imben1109 profile image
Ben • Edited

Yes. I know it and totally know your feeling. But the most depressing thins is that you need to response a estimated time to your customer or boss in the real life. And you need to take responsibility to the estimated time.