this post was submitted on 11 Jul 2024
161 points (99.4% liked)
Asklemmy
44122 readers
743 users here now
A loosely moderated place to ask open-ended questions
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Something doesn't work in a particular piece of software. "Don't they test their program?". "All they need to do is X, obviously they don't know how to code!".
Sometimes it isn't as easy as you think.
Though it being difficult doesn't excuse releasing an untested program or one with known issues...
Known issues that don’t interfere with the critical user stories are usually not prioritized. They should be disclosed, and even better if workarounds are published, but fixing them usually isn’t in the budget.
Since February the Uber Driver app has had a bug where elements from the “not in a trip right now” UI state render over top of the “in a trip and navigating” UI state.
It means that the user can’t see the text for the next turn, and also can’t see the direction of the next turn.
However there’s a workaround because they can see the distance to the next turn and once they’re close they can see which way route line goes.
I would still say that interferes with a critical user story.
Sometimes you have to make a tradeoff and focus on the golden path, which means comprehensive testing has to be skipped or bugs have to be explicitly left in.
Yes it's bad. Yes it sucks. But it's that or nothing gets released at all.
(I wish it wasn't that way. I try hard to make sure it isn't that way at my job, but for now that's how it is)