Timeline for Harmful temptations in programming
Current License: CC BY-SA 2.5
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 16, 2020 at 10:01 | history | edited | CommunityBot | Commonmark migration | |
| Mar 17, 2011 at 16:12 | comment | added | jwenting | always double your gut feeling to get your estimate, then double it again before giving it to any manager or commercial guy (because they'll half it again before putting it in any of their documents). | |
| Feb 26, 2011 at 11:43 | comment | added | Rei Miyasaka | Evidence-based scheduling might help with this problem: joelonsoftware.com/items/2007/10/26.html | |
| Feb 26, 2011 at 1:11 | comment | added | DaveE | One of my old bosses tripled developer estimates, then negotiated down to double with the clients. Clients thought they got a deal, developers got the time they needed even if they didn't know it. Win-win! | |
| Feb 25, 2011 at 6:29 | comment | added | detly | Alternatively, try the SMBC approach. | |
| Feb 25, 2011 at 1:39 | comment | added | zzzzBov | My college professor once told me to, "Figure out your best estimate, then double it." It's worked for me so far. | |
| Feb 25, 2011 at 0:39 | comment | added | PeterAllenWebb | When they ask you if it will really take that long, just say yes and then sit in silence until they feel the awkwardness... | |
| S Feb 24, 2011 at 17:04 | history | answered | Nicole | CC BY-SA 2.5 | |
| S Feb 24, 2011 at 17:04 | history | made wiki | Post Made Community Wiki |