Live data from Hacker News

Why Can't Developers Estimate Time?

blog.patchspace.co.uk

1–10 of 134 posts

Re: Why Can't Developers Estimate Time?

#3
post #2

Nicely complicated--- useful if the boss or client wants verbiage. If asked directly though, I usually say "If I've done it before, I know how long it takes; if not then not."

Haha, yes. That is the bottom line. But once they ask "why?", then OMG, worms everywhere!

My post is definitely not suitable for most management, but in a discussion with a bunch of fellow geeks, it did fit in with the discussion.

Explaining this to management/clients is not easy. It's a problem that needs tackling, but it's a separate problem.

Re: Why Can't Developers Estimate Time?

#6

It's because developers are rubbish for not being pyshic ;) I'm always suprised how few estimates take account of environmental contributions!!

Re "environmental contributions", that was part of the discussion, but thinking about it - estimating total effort and elapsed calendar time are very different!

Re: Why Can't Developers Estimate Time?

#9

It's because developers are rubbish for not being pyshic ;) I'm always suprised how few estimates take account of environmental contributions!!

Re "environmental contributions", that was part of the discussion, but thinking about it - estimating total effort and elapsed calendar time are very different!

elapsed calendar time and total effort are often the same in a customer's mind. Time is actually money.
Post reply on HN