3 ms·
Half the time the devs don't even underestimate, it's just that they're the easiest to blame them because it'll never hurt them (according to the people shiftin
by donkeyd 5y ago
Half the time the devs don't even underestimate, it's just that they're the easiest to blame them because it'll never hurt them (according to the people shifting the blame).
One time, I had to estimate a UI migration. I made the estimate and added the disclaimer that the estimation assumed X was true and Y and Z were provided. Of course, X wasn't true, because the supplier sucked and Y and Z weren't provided by the business. So it ended up taking way more time than estimated.
Guess who got the blame anyway.
- nerdponx 5y agoIt's even worse when you get pressured into giving unrealistic estimates, or even get overruled and have your estimate ignored, and then get blamed when the project runs over the estimated time. If that ever happens to you, don't wait around and suffer. Start looking for another job and save your sanity.