←back to thread

Estimates are difficult for developers and product owners

(thorsell.io)
225 points todsacerdoti | 1 comments | 07 Dec 25 19:17 UTC | HN request time: 0.221s | source
Show context
pyrolistical ◴[07 Dec 25 21:46 UTC] No.46185494[source]▶
My success rate went way up by only making 4 estimates.

1 day

1 week

1 month

1 year

This communicates the level of uncertainty/complexity. 5 days is way too precise. But saying 1 week is more understandable if it becomes 2 weeks.

I don’t estimate in hours or use any number other than 1

replies(1): >>46185503 #
bdangubic ◴[07 Dec 25 21:47 UTC] No.46185503[source]▶
But saying 1 week is more understandable if it becomes 2 weeks.

Amazing to read this… everything wrong with our industry summed up neatly in one sentence :)

replies(1): >>46185766 #
pyrolistical ◴[07 Dec 25 22:14 UTC] No.46185766[source]▶
Why is that a problem? It is an estimate. Not a hard commitment.

By definition estimate can be wrong

replies(2): >>46185950 #>>46185983 #
bdangubic ◴[07 Dec 25 22:30 UTC] No.46185950[source]▶
thats fantastic as long as you are not the one paying for it
replies(1): >>46194930 #
1. Capricorn2481 ◴[08 Dec 25 17:19 UTC] No.46194930[source]▶
I know it's easy internet points to say we should have accurate estimates, but that's not an actionable comment. That's like saying "cars should be safer" and expecting applause.

Most clients would rather you just give an estimate with 15 minutes of eyeballing it and hold you to that. That's not realistic, and it's not on developers.