this post was submitted on 10 Aug 2026
215 points (99.5% liked)
Not The Onion
22221 readers
900 users here now
Welcome
We're not The Onion! Not affiliated with them in any way! Not operated by them in any way! All the news here is real!
The Rules
Posts must be:
- Links to news stories from...
- ...credible sources, with...
- ...their original headlines, that...
- ...would make people who see the headline think, “That has got to be a story from The Onion, America’s Finest News Source.”
Please also avoid duplicates.
Comments and post content must abide by the server rules for Lemmy.world and generally abstain from trollish, bigoted, ableist, or otherwise disruptive behavior that makes this community less fun for everyone.
And that’s basically it!
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Distributed decision making, and these are all systems that are transactional or regulatory and not necessarily driving revenue / customer value.
The IT / Systems team was told “stand up an SMTP server so we can send emails” and there’s no more discussion of capturing / trapping / dead boxes. And as an engineer if you start to add that scope, “why are you taking so long? I just need to send emails.”
And then the delete account project is “GDRP says we need to delete accounts. So delete them in the least expensive way possible.” Which means, as an engineer, don’t spend a ton of time on this. In my previous company, we were still manually deleting accounts. As in SRE connected to the DB and ran a SQL command, by hand, with a piped in user ID.
The notifications team is responsible for sending messages. Why do they care, or should be responsible for, identifying if a user is deleted? They’re responsible for maintaining the SPAM/unsubscribe list but not the user accounts.
it’s distributed decision making, no one cross-cutting or thinking about these edge cases that impact multiple systems