|
|
|
|
|
by jakear
2269 days ago
|
|
Why not both? User testing won't help you with questions like "there's a bug in feature X, but the fix will potentially impact feature Y in unforeseen ways. Given we're shipping soon, is it a good idea to apply the fix now or should we apply a much simpler mitigation and postpose the full fix till next iteration so we can get more testing in or even implement a larger refactoring that would resolve this category of bugs by design?" If feature X is used way less frequently than feature Y, the answer is obvious. If feature Y is used way less frequently than feature X, the answer is obvious. If its a wash, you move on to look at different metrics. This isn't a hypothetical, I ran this exact scenario yesterday against the VS Code telemetry. I applied the mitigation, the refactoring is coming next week. :) |
|
Because you respect your users and know their privacy has value.