498
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 06 Oct 2023
498 points (100.0% liked)
Technology
59299 readers
3947 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
Or maybe they engineered a "multifunction" device with shitty error handling: if any subsystem has an error, all functions fail, even those that don't depend on that subsystem.
A junior engineer filed a bug report about it and submitted a patch that allows subsystem errors to gray-out only certain functions in the UI.
The PM didn't consider the bug launch-critical enough to merit an engineer's time to review the patch. One senior engineer did briefly look at the patch and said "sorry, we can't alter the UI without brand & design review, i18n, and a lot of shit you don't wanna do."
The system shipped with the bug intact. The PM was rewarded for launching the product on time, and got promoted into a different position.
A year later when the users start fussing, the people on the team say "we never heard of that problem."
(This is hypothetical. Tech companies do be like that sometimes though.)
Just because they accidentally made ransomware doesn't make it not ransomware.
Exactly, yeah. The incentives within the company generate shitty behavior towards users, even if no individual wrote out a design for that shitty behavior.