2 ms·
The reason this happens is because users reason that if the program worked but had a problem, it would not show "an error". They see so many errors they can't d
by cratermoon 6y ago
The reason this happens is because users reason that if the program worked but had a problem, it would not show "an error". They see so many errors they can't do anything about, they just dismiss them and look at the non-erroring program for guidance. Users then see an "error" that pops up as being an error that's getting in the way of seeing the problem. A good program doesn't say "that was an error", because users are now habituated to assuming the error is nothing they can do about, and ignore it. A good program just gives feedback as if it were performing normally. A good program simply says, implicitly because it's not framed as a problem, "You wanted to do X and expected a Y but got a Z because.."