The first 90% of the task takes 90% of the time.
The last 10% of the task takes the other 90% of the time.Which is why you switch the project team after 90% so you can get to 99% completion in 50% of the time. Now that’s thinking like a Project Manager.
I’m in this picture and I don’t like it.
I try to remember to always under promise expectations. Even after all these years I keep forgetting that a simple change is never really that simple and has lots of overhead.
Scotty had it right. Always multiply your estimates by four.
That works until you are dictated a date you never agreed to. Going thru a little PTSD moment right now lol.
It’s crazy that they got these images from my lunch today.
I’ve been working on a single bug for nearly 3 weeks. I think my “I’m getting closer to understanding this” is starting to lose credibility with my team.
Just do what my colleagues do, ignore it completely.
Pros: Very time and resource efficient. Little documentation needed.
Cons: Doesn’t solve the problem.
I feel attacked.
How can you be a complete stranger and still hurt me so personally?
This truly hurts.
As a pessimistic (i.e. often times realistic) dev, I can tell you, management does not want to hear that either…
“I should have a PR up today sometime”…repeats that phrase in the morning huddle 4 days in a row.
What you said: “It’s almost done”
What the PM heard: “It’s done”
What the business tells its clients: “It’s deployed and already servicing customers”
Ffrom a dev perspective it’s also often “Yep that would take three days if we worked on it”. Two years later - no progress.
There’s a difference between an estimate and a promise to deliver.
I’m ded. Although my big trick lately is just adding 3x to whatever I think, and it works pretty well
Screenshot depicting my stand up exactly 3 days ago
