← Back to context

Comment by tristor

20 hours ago

Probably not, Japanese firms excel at hardware and generally build extremely poor software. This a hardware product, so consequently it is probably fairly good.

What caused this?

  • Japanese software don't get much recognition. Nintendo Switch(1 and 2) isn't running Linux, and it supports NVIDIA graphics stack. That shouldn't be possible unless Nintendo is actually capable of building a graphical operating system, which it is. Hardly anyone realizes this. There are also tons of (trashy)software embedded in Japanese hardware and none of those somehow mentally register.

    Japan is also extremely weary of getting in the way of US. Software is one of few remaining consumer high tech domains that US leads. Challenging that without a good reason isn't a great idea.

  • I think Ruby would be a counterpoint - although it's the only one I know of.

    I worked for a Japanese company although in a local office with local management. Through all those layers of protection I got the impression that they suffer from what all corporates suffer from - no software engineers that have made it to the top. Software companies run by people who have no clue.

    In the US, for example, I think some people who have a clue or a partial clue have made it up the ladder in some places and therefore although everyone there has their horror stories of idiotic behavior it is probably somewhat better.

  • This is just my hypothesis, but I believe the language barrier is an issue. English is effectively a necessity for programming because real programming languages with ecoystems, error diagnostics, documentation, and useful articles/blogs/books are written in English. Japanese software developers know enough to get by, but they're still by-and-large insulated from the Anglosphere learning culture, where ideas and best practices rapidly propagate in the open. I'm not involved in hardware, but I'm guessing this is less of a barrier for hardware because hardware/documentation tends to be proprietary rather than open anyways, so whereas the Anglosphere gains a cumulative learning advantage from an open source + technical blogging culture in their fluent language, this does not manifest so much in hardware.

  • Honestly, no idea. In my career I have worked with a lot of Japanese firms and have always found their engineers to be excellent. I used to think it was a lack of consideration for UX, but that obviously can't be true when you see excellent examples of UX in hardware (e.g. Switch controls), even though its exceedingly rare on the software side.

    If anyone on HN knows (there are several other commenters more deeply steeped in Japanese engineering culture), I would love to know why as well.

    • Japanese culture and work culture is very hierarchical/top down. They excel at waterfall but it's basically impossible to do agile in a Japanese office environment, and waterfall is suitable for hardware but terrible for building software.

      1 reply →