this post was submitted on 28 Aug 2023
215 points (97.4% liked)

Programmer Humor

32483 readers
397 users here now

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

Rules:

founded 5 years ago
MODERATORS
215
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 18 points 1 year ago (2 children)

Ppl misjudge the implications of those priorities.
Low priority: your shit is broken, well deal with it during office hours
Medium priority: a whole department's shit is broken. We'll stay longer to fix it if needed.
High priority: EVERYONE'S SHIT IS BROKEN HOLY FUCK, SEVENTEEN TECHS ARE IGNORING THE SPEED LIMIT ON THEIR WAY TO FIX THIS RIGHT NOW

[–] [email protected] 17 points 1 year ago

That's IT. In software development?

Important stakeholder wants something: drop everything that's top priority.

High priority: we'll get to it next sprint, an important stakeholder wants something right now.

Medium priority: we'll get to it after all the high priority items are done, but we're getting an important call from another important stakeholder right now, we'll get back to you about timelines.

Low priority: you're starting to sense the pattern here, right?

Code quality, documentation, testability, test automation: lol

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

I just wish they would call it "normal" instead of "low" priority.