←back to thread

When did estimates turn into deadlines?

(domainanalysis.io)
324 points alexzeitler | 2 comments | 19 Nov 24 20:03 UTC | HN request time: 0.427s | source
Show context
jappgar ◴[19 Nov 24 23:41 UTC] No.42189272[source]▶
A lot of ink has been spilled on this topic.

The solution is simple: get better at estimating.

Software engineers act as if they're the only ones in the world who are asked to estimate and then held accountable.

It's a skill issue.

replies(6): >>42189327 #>>42189384 #>>42189421 #>>42189431 #>>42189600 #>>42189601 #
HelloMcFly ◴[19 Nov 24 23:48 UTC] No.42189327[source]▶
It's literally impossible to know what you don't know. Sometimes you discover things in the process of your work that couldn't have reasonably been accounted for on first estimate, and it is not good practice to always give an estimate that assumes a 5x difficulty multiplier for some unforeseen reason.

Yes, if this is an "every time experience" then there could be a skill issue or possibly some other undiagnosed or unrecognized systemic factor

replies(1): >>42190024 #
1. jappgar ◴[20 Nov 24 01:40 UTC] No.42190024[source]▶
When I cut open my ceiling to fix a plumbing issue I didn't know what I was going to find exactly, but I had a pretty good idea of the possibilities. My estimate for how long the fix would take was pretty close.

Software is the same thing. There are unknowns but there aren't unlimited possibilities.

replies(1): >>42194088 #
2. HelloMcFly ◴[20 Nov 24 14:15 UTC] No.42194088[source]▶
It's a great analogy, but I think it's the kind of analogy that works on the surface and not in the details most of the time due to a) much more codification of practice in construction and b) more "fixed" knowledge of what's likely based on location and build era of the home, whereas software is much more dynamic and often subject to individual whims of developers or management.