Remix.run Logo
Remix clone Hacker News
new | show | ask | jobsGithub
▲ pyrolistical a day ago

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

▲bdangubic a day ago | parent [-]

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 :)

▲pyrolistical a day ago | parent [-]

Why is that a problem? It is an estimate. Not a hard commitment.

By definition estimate can be wrong

▲deely3 a day ago | parent | next [-]

How often you spend a week doing 2-day job?

▲bdangubic a day ago | parent [-]

I’d be fired if that happened without a reasonable explanation why I was so terrible at the task I took on and let my team down by taking that long

▲bdangubic a day ago | parent | prev [-]

thats fantastic as long as you are not the one paying for it

▲Capricorn2481 8 hours ago | parent [-]

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.