News for hackers. Stuff that matters.
Re:Why are developers expected to estimate tasks at all? by dsizzle on Sunday March 26, 2023 @02:47PM (#35317967)
> I wonder if the person asking the question would be happy to let someone do a job in his home with an uncapped budget and timeline?

The author made the claim that software engineering is fundamentally different from carpentry ("Almost everything a developer writes is unique, they have never built that particular thing before. We are not cabinet makers...")

But does that hold up? Many software projects do in fact have a similar analogue, and each house is unique and carpentry projects will thus run into unexpected snags.

Re:Why are developers expected to estimate tasks at all? by gabereiser on Sunday March 26, 2023 @02:50PM (#35318006)
He/she hasn’t been around enough to see these patterns yet. The amount of times I’ve had to implement security, rbac, rest crud, modeling, service integrations, etc are too many to count. I rely on packages that help reduce the boilerplate and because I’ve done that so many times, I can give you an estimate on roughly how long it will take.

The fact that the OP doesn’t see this is fact that they are too junior to be asked for estimates at all.

Re:Why are developers expected to estimate tasks at all? by efnx on Sunday March 26, 2023 @03:02PM (#35318172)
Or they’re very senior in a pioneering domain that doesn’t have all these packages written.

It really depends on what domain you are programming in.

Re:Why are developers expected to estimate tasks at all? by gabereiser on Sunday March 26, 2023 @03:07PM (#35318262)
If that were the case, the business would know this and wouldn’t be asking you for estimates to return back to the client.
Re:Why are developers expected to estimate tasks at all? by efnx on Monday March 27, 2023 @02:50PM (#35330697)
In my experience corps doing pioneering work don’t always act as though they are pioneering.