Hacker News new | ask | show | jobs
by tzs 2230 days ago
Anecdotally, based on experience with shipping software with an annoying bug to Japanese consumers, the Japanese people are way more patient than Americans.

I worked at an American company that made utility software for DOS/Windows. A major Japanese distributor liked our stuff, and made a distribution deal with us. They also helped with localization, and suggested feature changes to better fit what Japanese consumers wanted. Later this expanded to where they would also suggest new products they wanted for Japan and we'd develop them.

One product under development was very rarely causing a system lockup during installation. By "lockup" I mean it appears completely dead. No mouse motion. No keys worked. Hitting "CAPS LOCK" would not even toggle the light on the keyboard. Hard reset seemed to be the only way out.

It was rare enough that we always saw the install attempt after that hard reset work.

We just could not figure out what was causing this. The Japanese distributor decided we should go ahead and release, and their tech support people would deal with any complaints.

So we released...and their tech support got a lot of calls. People were hitting it a lot more than we had seen in testing.

...except they were not calling to complain about their system locking up. No, they were calling to complain about a slow install.

Apparently, when it became completely unresponsive all you had to do was wait 20-25 hours and it would complete the install.

I cannot imagine any American consumer whose PC has become completely unresponsive going 20-25 hours without giving up and resetting the thing. Not only were there such people in Japan, there were a lot of them. We didn't get one complaint about a lockup--all of the many many people who called called about it taking around a day to finish.

(Oh, and the knowledge that it was not a complete lockup was enough of a clue to let us figure it out. It suggested it was some sort of timeout, not a lockup. Our product needed to know what optical drives were available, and it turned out that the way it scanned for them did not get alone well with one particular brand of optical drive controller card, which could trigger about an hour timeout per drive checked for. We switched to a much more cautious drive scan, and the problem went away).