Programmer Humor

42698 readers

292 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.

founded 6 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

cat_programmer@lemmy.ml

118

It has been 0 days since I last had this conversation (lemmy.ml)

submitted 18 hours ago by raindrop1988@lemmy.ml to c/programmerhumor@lemmy.ml

49 comments fedilink hide all child comments

Manager: We (meaning you) need to do task A. How long will it take?

Me: Task A will take X days to do.

Manager: That seems awful long.

Me: How long do you think it should take?

Manager: It surely could not take any longer than Y days.

Me: Ok, it seems you have an answer to your question then.

Later:

Manager: It’s been Y days, why isn’t task A done yet?

you are viewing a single comment's thread
view the rest of the comments

[–] leftascenter@jlai.lu 5 points 14 hours ago (1 children)

The person doing the work the one best suited to estimate it.

As a manager in found this to be partially false.

Most persons doing the work quote forget that shit happens. Except for the few reliable persons I supervised, I usually always asked the follow-up question: what "unforeseen crap" time did you include, and made sure to leave with 3 values: all goes well (which I kept to myself), usual estimate, what if bad shit happens. Then I'd just use the standard pert guesstimate for my official schedules, making sure to include normal dead time which employees often forget (e.g. 8 days work is really 2 full weeks when accounting for meetings).

[–] Shanmugha@lemmy.world 1 points 7 hours ago* (last edited 7 hours ago)

Oh yeah. It takes experience and clear head to remember to account for all the inevitables that are going to happen besides actual dev-hours-to-create-this. A hard lesson I am still learning