The first rule of dev club is: You don't talk about the backlog
this post was submitted on 18 Oct 2023
285 points (92.8% liked)
Programmer Humor
32472 readers
564 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 5 years ago
MODERATORS
But I need to poop. I can’t hold that backlog in for longer.
I've got a backlog that's about 900 long... you can definitely hold more and your company depends on you doing so. If your product department sees you closing their tickets they're definitely get uppity... and the golden rule of development is to never do a product tickets.
Second rule of the dev cub: You DO NOT talk about the backlog
Omg, I have SOOoo many questions about what is going on in this picture.
I think almost all of them can be answered with "It's an AI-generated image."
Look up 'Gumbo Slice' for more.
Oh shit, I remember watching Gumbo Slice backyard street fights back in the day. Didn't realize this was meant to be him!
It's AI generated
Ah, that's a shame in a way because I liked the idea of this guy walking around irl. Still a great image though.
Yes, but it's just soon good. I love it.
I always kind of hated how non-committal POs were with that. It seems like any experienced dev knows backlog is effectively /dev/null. So, if you actually treat it as such, you can skip refining stories that will not be tackled any time soon and you can purge stories from backlog aggressively (or work with filters to hide them), so that your board shows actually relevant stuff.
But POs will always be like, oh no, we can't delete this story that we spent all of 5 minutes to write. It might still be relevant. We must remember that we still need to do this (and then not do it anyways)...
In my experience, that's not a problem of commitment, but rather budgeting and priorities.
There's always something more urgent than that one refactoring ticket, but you also don't want to effectively delete a clear indication of a problem.
I mean, I agree with that. Maybe "non-committal" isn't necessarily the best word. I'm mostly saying, assuming that POs realize backlog won't get prioritized nor they'll be gifted money to work on it, they should lean into that fact more.
They could sort backlog for chance of ever becoming relevant enough again and then delete the lower 90%.
Or I don't know, any card that sits around for more than 6 month is deleted. I've rarely seen an issue older than 6 months that wasn't wildly outdated anyways.
Or my preferred flavor of chaos: If it's actually a problem, you don't need a card on a board to remind yourself of it. You want a card for the when and how, but not that you need to do it.
Lately I felt like AI have bought mankind plausible deniability. Like please tell me this picture is AI generated