this post was submitted on 28 Aug 2023
145 points (98.0% liked)

Programmer Humor

32070 readers
541 users here now

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

Rules:

founded 5 years ago
MODERATORS
 
top 12 comments
sorted by: hot top controversial new old
[–] user224@lemmy.sdf.org 18 points 1 year ago (1 children)

You could put the direct image link https://i.imgflip.com/7x89o9.jpg into the post URL to view the image directly through lemmy.

[–] hidden_splendor@lemmy.world 1 points 1 year ago* (last edited 1 year ago)

Thanks, that's better

[–] Norgur@kbin.social 14 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

[–] Pxtl@lemmy.ca 5 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

[–] all4one@lemmy.zip 3 points 1 year ago

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

[–] scrubbles@poptalk.scrubbles.tech 1 points 1 year ago (1 children)

Is the site down? Is email down for everyone? Is CSuite/ the entire business operation down? Then it's high priority.

Otherwise it's low priority.

[–] metaStatic@kbin.social 2 points 1 year ago
[–] beeng@discuss.tchncs.de 0 points 1 year ago (2 children)

Hello shadow IT.

Now even more Silos. Thanks IT

[–] hidden_splendor@lemmy.world 1 points 1 year ago

This is why I do everything myself if I have permission.

[–] mosiacmango@lemm.ee 0 points 1 year ago (1 children)

Shadow IT is a management failure, not an IT failure.

Personally im inclined to let buisness units blow themselves up if they like. I'll pick up whatever pieces I can, but if I can't, all well. If we dont support it and you use it, things get really simple for us.

[–] beeng@discuss.tchncs.de 1 points 1 year ago* (last edited 1 year ago) (1 children)

IT mangement is still IT.

But it's more gatekeeping by IT in my experience. Old roles that can't hand over control, so they get piles of work that they cannot handle..

Hence "LOW PRIORITY"

[–] mosiacmango@lemm.ee 2 points 1 year ago* (last edited 1 year ago)

Management is always management first, but sure.

Gatekeeping at the lower IT level comes from "responsibility." Lots of people want unlimited power, but the minute there is an issue, they throw the problems back over the fence, fingers a' pointin'.

If a different part of the org takes actual ownership, I'm always happy to let them fully control whatever. When you do the backup/monitoring/logging/provisioning/licensing/securing/load balacing/etc, go nuts.

It's why shadow IT is fine by me, but if you want to fuck shit up and then try to tell me to clean it up, nope nope nope.