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

Programmer Humor

22244 readers
439 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) 33 comments
sorted by: hot top controversial new old
[–] [email protected] 3 points 1 week ago

Story points = hours

[–] [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* (last edited 1 week ago) (2 children)

So what's the actual error margin for estimating feature implementation time? It's going to be nearly the whole thing, right?

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

Wildly depends on the complexity of the feature. If it only takes 4 hours to implement, you might have good enough of an idea what needs to be done that you can estimate it with 1-hour-precision. That is, if you're only doing things that you've done in a similar form before.

If the feature takes two weeks to implement, there's so many steps involved in accomplishing that, that there's a high chance for one of the steps to explode in complexity. Then you might be working on it for six weeks.

But yeah, I also double any estimate that I'm feeling, because reality shows that that ends up being more accurate, since I likely won't have all complexity in mind, so in some sense my baseline assumed error is already 100%.

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

Hmm, so kinda O(n^1.5^) scaling? (Of the ratio between definitely required time and possibly required time, anyway, since a -110% error wouldn't make sense)

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

Really not sure an estimate for algorithmic complexity is the right way to specify this. 😅
But if your supposed input unit is days, then I guess, yeah, that kind of works out.

load more comments (1 replies)
[–] [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] 3 points 1 week ago

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

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

Do people not know how bingo cards work anymore?

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

All-day "Sprint Grooming" meeting

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

Might as well put the whole Agile/Scrum crap on there while you're at it...

[–] lambda 3 points 1 week ago (2 children)

Disagree. My company does it well and I think it helps productivity across the board. My last job called our process agile and it was really just water-scrum-fall. Which was horrible and we devs were all miserable.

load more comments (2 replies)
load more comments
view more: ‹ prev next ›