this post was submitted on 28 Mar 2025
601 points (99.0% liked)

Programmer Humor

22219 readers
1602 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
 
(page 2) 30 comments
sorted by: hot top controversial new old
[–] [email protected] 10 points 1 week ago

I just had a contractor tell me I needed to prioritize their request because it's urgent for the task they're working on that's adding a new feature.

they want me to push the changes out by EOD....today.....Friday.

I don't like to do this, but I hold seniority....sooo....I think I'm going to take a three hour long lunch and cut out for the weekend early.

don't come to me with a request unless it's actually urgent.

I'm out

[–] [email protected] 9 points 1 week ago (1 children)

If story points are now hours, I hope you're fine with me putting a 40 on that ticket.

[–] [email protected] 7 points 1 week ago (7 children)

Storypoints are such an artificial concept it doesn't even make sense. Same thing with estimation though. Most numbers are "I pulled it out me arse" unless the task is a one line change. And even then, shit breaks and it becomes useless, so the one line change is estimated to be a day anyway

[–] [email protected] 1 points 1 week ago

Somewhat agree, but since Scrum is supposed to be bent to the team's needs, it might differ from team to team, but it's fine as long as those numbers are consistently used in one team.

load more comments (6 replies)
[–] [email protected] 8 points 1 week ago

4 hour planning

I've seen projects where this was comically too high. But a lot more where it was horrifyingly agonizingly too low.

[–] [email protected] 7 points 1 week ago (1 children)

Unpaid overtime = work is just not going to be done.

[–] [email protected] 3 points 1 week ago (1 children)

That's what I do at work, even though I'm salary.

Management decided to hire a new guy and then have a round of layoffs within 6 months, effectively canning someone to replace him. Since then, we've had multiple times where we have hundreds of tickets sitting unassigned because there's more work than people. So shit sits and falls through the cracks until someone has time or something is on fire.

It fucking sucks, but eventually the bean counters will see that we actually needed that extra body....

[–] [email protected] 3 points 1 week ago

We did have well over 100 tickets in the queue, now they split the support team into multiple sub support teams and each sub team has fewer tickets in their own queue. The total number is still massive but compartmentalising the problem makes most of it go away! I can filter it down to such a degree my queue is almost single figures by just ignoring everything else because that is someone elses problem.

Also my sub team doesn't have anyone to cover 1st line on some products so I am covering 1st line there as well as 2nd line. Upside is my stats look brilliant now that I am doing all the password reset tickets.

[–] [email protected] 7 points 1 week ago

When I started working for my current company there were really few meetings and I didn't know that it was possible. Everywhere I worked we had all the Scrum meetings and tech discussions meetings. At that time it was relatively a small company but not that small.

Now the company is getting bigger and some persons try to bring all the scrum shit. Even for small features, we do meetings to discuss them and last for hours. Some meetings have a big agenda that we always only tackle half of it. Sometimes we decide to do something with big impact and then someone suggests to include a person from another that doesn't even know our scope. And then we get "maybe we shouldn't do this as it will maybe have some negative impacts", "maybe we should add an exception" without even giving data to support their claim.

[–] [email protected] 4 points 1 week ago (1 children)
[–] [email protected] 2 points 1 week ago (1 children)

are you sure it's not blackout? lmao

[–] [email protected] 3 points 1 week ago (1 children)

Is "blackout" a bingo term for filling every box, or just falling unconscious from overwork?

[–] [email protected] 2 points 1 week ago

I was meaning filling every slot but that works too!

[–] [email protected] 3 points 1 week ago (1 children)
[–] [email protected] 3 points 1 week ago* (last edited 1 week ago)

Bing (or I guess to keep up with the song, _ingo)

[–] [email protected] 2 points 1 week ago (2 children)

Nah, time tracking is often needed for tax purposes: companies can write off R&D expenses

[–] [email protected] 8 points 1 week ago

It all depends on how time tracking is implemented.

Tell me I have to account for my time in 15-30 min increments? Fine, I can put it into a spreadsheet and track it.

Tell me I have to track real time spent? Get entirely fucked, and I hope you're ok with spending time fixing my time punches because I absolutely am going to forget to open or close a time entry because I'm working on 3-4 tasks at any given time.

I've done both, and while I won't intentionally sabotage the latter, my rampant ADHD and terrible memory have got my back on that one.

[–] [email protected] 3 points 1 week ago

Yeah but that can be done after you're finished, definitely shouldn't be part of planning!

[–] [email protected] 1 points 1 week ago

Do people not know how bingo cards work anymore?

load more comments
view more: ‹ prev next ›