News for hackers. Stuff that matters.
Re:Why are developers expected to estimate tasks at all? by mewpmewp2 on Sunday March 26, 2023 @08:58PM (#35321591)
Did you say what you are saying here?

Did you say that

1) Without knowing further best case is it takes N time, worst case M time, and if there are certain obstacles it could be completely unfeasible. 2) To get more accurate time and to understand whether it's feasible I would need O time to figure that out first, and I can give you the more accurate estimate then.

Re:Why are developers expected to estimate tasks at all? by IIsi50MHz on Sunday March 26, 2023 @10:56PM (#35322364)
This seems unexpectedly optimistic, to me. I'd think: best case = it's already done; worst case = it's impossible, but we don't know that until we've spent too much time and money on it; the "certain obstacles" are almost always uncertain or completely unknown; and the "O time to figure out [how much time it will take] is also unknowable until the "figuring" is already complete. Now, if this were manufacturing with well-known processes, then I feel I could use your formula.
Re:Why are developers expected to estimate tasks at all? by Scarblac on Monday March 27, 2023 @01:37AM (#35323216)
Yes, of course. To the bad managers it sounds like just yet another excuse, and they ask other devs until they find one who gives a number.