Perhaps an interesting analogy, but offers nothing in terms of how to improve estimation. The only thing I can take away from this is to always add contingency to an estimate.
this post was submitted on 19 Feb 2025
15 points (85.7% liked)
Technology
69770 readers
4353 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
Instead of four hours, this could have taken half an hour by properly exploring the problem and mapping out a solution first. Everyone seems to shit on drawing up an architecture first and wants to immediately start coding, but taking a little time up front to think through the problem pays huge dividends in the long run.
You can just throw away your code and you don't need to go back to the store to continue. Starting to code right away would work just fine if you're not doing real world tasks
With the software part ai agree with him but his washing machine problem is easy to fix by going through the steps and looking at things, measuring them, etc making a plan before going to the shop for the first time. That doesn't remove all unkown unknowns but most of them.