Re:How I Estimate Work as a Staff Software Engineer
by chrisfosterelli on Saturday January 24, 2026 @11:34AM
(#46744974)
> Contractor estimates are just as prone to schedule slippage and cost overruns as anything estimated by software engineers
I completely agree. That's why I chose that example: They're also awful at it, especially these days in North America in particular. But any contractor that tried to put in a bid claiming "it'll be done when it's done and cost what it costs" would not be considered professionally competent enough to award a multi-million dollar budget.
Re:How I Estimate Work as a Staff Software Engineer
by danenania on Saturday January 24, 2026 @04:59PM
(#46748160)
The date is just a useful fiction to:
- Create urgency
- Keep scope creep under control
- Prioritize whatever is most valuable and/or can stand on its own
If you just say “I don’t know” and have no target, even if that’s more honest, the project is less likely to ever be shipped at all in any useful form.
Saying "I don't know" is arguably more honest, even if it's not useful for budgets or planning.