3 ms·
"A week" is a terrible estimate for complex things that have components that you can't foresee. If you lose "a day" on some problem outside of your control (com
by unreal37 7y ago
"A week" is a terrible estimate for complex things that have components that you can't foresee. If you lose "a day" on some problem outside of your control (compiling starts to fail and it turns out someone checked in some code into your branch by mistake), you've basically wasted 20% of your estimate.
Never say a week when there's the chance something will require a month because you didn't understand it.
You need to learn this lesson. A week is a blink of an eye in software, and only things you understand take a week.
- ALittleLight 7y ago"Really? X will take 'a month at least'? Why?" "I don't know why, but I don't feel comfortable guessing less because I don't fully understand X." "Okay, that's not a good way to estimate. Why don't you spend some time to come up with a plan for X and we can estimate it after that. When can I have the plan?"
- aidenn0 7y agoYou can have the plan in a week.
- deleted 7y ago[deleted]