bruh, so it's not me who was stupid all this time for not being able to put an estimate for large initiatives. It always feels forced to give an estimate.
this post was submitted on 24 Jan 2026
14 points (81.8% liked)
Programming
24586 readers
100 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
The only way to estimate work is to make up a number and then log everything that prevents that from happening to put forward a case when the “why?” question comes up when the deadline hits. Then prepare for being told you are making up excuses and being negative and not flexible to all the challenges that you just listed and that you need to manage time better and potentially think about outsourcing some work to people who lie better than you.
Take how long you think it will take, double the number and increase the units (at least until you're senior). e.g. 2 days -> 4 weeks
I…. am not actually sure if you’re joking or not.
I normally use the Scotty method - multiply by four.
I…. am not actually sure if you’re joking or not.
Bit of Column A, bit of column B...
Maybe it should have been 'Take how long you think it will take at first blush'. Scotty's method is good with a bit more experience.