this post was submitted on 23 Sep 2025
652 points (100.0% liked)

Programmer Humor

26603 readers
2861 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
 
top 24 comments
sorted by: hot top controversial new old
[–] xxce2AAb@feddit.dk 78 points 5 days ago* (last edited 5 days ago) (4 children)

"I'd like you to to give me a time estimate, including the time taken to define the task and it's exact scope."

"You want me to do that before telling me what you want me to do or letting me think about what that'll entail?"

"Look, I just need you to pull an arbitrary number out of your ass and give it to me in writing, so I can hang you out to dry when you inevitably get it wrong."

[–] Godnroc@lemmy.world 34 points 5 days ago

Gives a number.

"Why is it going to take so long?"

[–] favoredponcho@lemmy.zip 14 points 4 days ago

“We need it, so we can determine timelines. Btw, it needs to be done in three months.”

[–] JackbyDev@programming.dev 17 points 5 days ago (1 children)

The irony being that really fully understanding what all a task will require and getting exact specificaion can often make a task take longer.

[–] SpaceNoodle@lemmy.world 7 points 5 days ago (1 children)

In my experience, it takes exactly as long as the task itself requires, but the bonus is that the task is then also complete

[–] JackbyDev@programming.dev 3 points 4 days ago (1 children)

Doing the task estimates the task.

[–] SpaceNoodle@lemmy.world 3 points 4 days ago

It's the bestimate.

[–] squaresinger@lemmy.world 3 points 4 days ago

Easy solution: Add a large margin for uncertainty.

[–] deadbeef79000@lemmy.nz 25 points 5 days ago

I had a PM get really unhappy when they asked how confident I was with an estimate.

Apparently +/-100% upsets them.

[–] MonkderVierte@lemmy.zip 11 points 4 days ago (1 children)

My last employer used to ask this, i gave a estimate (best case to worst case) and he always picked the lower number. Learned something from this: never give a range, give the worst case.

[–] psud@aussie.zone 1 points 12 hours ago

I give them reasonable case and tell them it's if everything goes right.

After we exceed the estimate if they ask I tell them that not everything went right. I like my current management, they let us estimate in very low resolution, and expect that nothing will be delivered on time

[–] SpaceNoodle@lemmy.world 26 points 5 days ago (1 children)

I've used a variety of different tactics to deal with this issue while on different teams:

  • Story points all based on Fibonacci numbers: set all values to 4
  • Five days (do not mention that they are not consecutive)
  • Two weeks (no matter the scope)
  • Give a time estimate on when a time estimate can be delivered (do NOT follow through)
  • Repeatedly ask to borrow the requester's time machine
[–] frezik@lemmy.blahaj.zone 22 points 5 days ago* (last edited 5 days ago) (1 children)

We once had a consulting company try to sell us on an automated test solution. Some higher ups were really keen on them. We had a suspicion they hadn't actually made the thing, but were presenting it as such. They were likely hoping they would get us to backdoor bankroll its creation and sell it to other clients.

So after they were done, I asked when we could get a demo of the app. They started to hem and haw. Then someone else asked when we could get an estimate on when we could get a demo. Still more hemming and hawing.

Then we asked for them to get back to us on that, and they never did. Problem = Solved.

[–] squaresinger@lemmy.world 5 points 4 days ago

I worked in a startup that was expanding to the US. For that purpose we hired two sales people with really good connections to the largest potential customer company in the US.

We had this product on our price list. It was a small and relatively inexpensive product (in the order of a few €100, while most of our other products had four to six figure prices). This product was stuck in development hell. We had a half-functioning prototype with the wrong chip in there, and it would need a full rework. It was a terrible product and far from usable.

So that new sales guy calls up my boss, the CEO, who's a notorious lier and proud of that fact and asks him if that device is ready to be sold. The sales guy says they don't have any customers asking for this and it's totally ok if it's not ready to be sold, he just wants to know whether it's ready.

With no need and no pressure at all, the CEO says "Oh, it's completely finished. You can sell that with no issues at all."

The sales guy believes it, and tries to sell this to that one biggest potential customer. The customer likes the idea and asks for a demo. Of course, we cannot provide one.

That was it. That customer blacklisted us and never bought anything at all from us. It burned the two sales people, they never managed to get any of our products sold in worthwhile quantities and a year later we shut down the US division.

[–] HubertManne@piefed.social 18 points 5 days ago (1 children)

This is definitely the thing I hate the most. Let me just work on it till it works.

[–] SpaceNoodle@lemmy.world 4 points 5 days ago

But then how will middle management justify their jobs?

[–] WanderingThoughts@europe.pub 14 points 5 days ago

"What did you sell them?"

"I basically just said yes if they asked if it was in the system. So how long?"

[–] MalReynolds@piefed.social 10 points 5 days ago (1 children)

Rule of thumb.

Double the number, bump the units.

[–] I_am_10_squirrels@beehaw.org 3 points 3 days ago

40 hours? Nah, 400 kilohours

[–] artifex@piefed.social 10 points 5 days ago

I'm literally on this call right now!

[–] lugal@lemmy.dbzer0.com 4 points 5 days ago (3 children)
[–] JackbyDev@programming.dev 4 points 5 days ago

See title. I got 195.