5 ms·

The common factor is lack of respect for software. They did very well when focused on just hardware with simple software. For example the hardware part of rob

The common factor is lack of respect for software. They did very well when focused on just hardware with simple software. For example the hardware part of robotics and very advanced features phones. But the next stage requires advanced software such as AI and the iPhone. This is an issue not just in Japan, but Asia in general. Their history had a lot of hardware success, but no major software success. In the US there is both Intel and Microsoft, major success in both hardware and software. This is actually a competitive advantage of software engineering in the US. We have a history and culture of respecting software. This is passed down generation to generation and allowed more success like Google and Facebook. In Asia, software is a low status job with little pay and status.

raverbashing 11y ago
More to the point, to have success in software development you need: - Independently minded people (incompatible with Japanese culture) - Flatter hierarchy (kind of relates to the previous point, and incompatible with Japanese culture) For simpler software, this is easier to overcome (Super Mario levels of software complexity, let's say) Steve Jobs didn't come up with the iPhone. He let people come up with great ideas then filtered them. In Japan, the structure goes: "What does the boss want?". And if the boss doesn't know, they will go with the most conservative choice possible. This set up is never going to win prizes.
- my_username_is_ 11y ago
  Can you explain why a flatter hierarchy is necessary for software development? My background is in hardware engineering, and this strikes me as surprising (although something I haven't ever given much thought to). What about software makes it incompatible with hierarchy? Don't a lot of traditional software companies have a sort of hierarchy?
  - raverbashing 11y ago
    Don't confuse lack of hierarchy with flatter hierarchy. > Don't a lot of traditional software companies have a sort of hierarchy? Yes, see what kind of crap they produce. Of course, not all software companies, but the ones that really innovate can't survive certain environments > What about software makes it incompatible with hierarchy? The sheer level of independence that every part needs. In a hardware project you pick your parts (you have some requirements, some limitations in size, power, vendor, etc so it might be a choice between a handful of parts), then put it on a PCB, solve placing, routing, EM compatibility, etc. It's complicated, but you don't have too many people doing that. And more importantly, your boss knows more or less about everything and if he doesn't believe it there are hard constraints that serve as guiding (power consumption, EM emission, performance, etc) Good? Now, you want to build the software for the iPhone. Or for the Macintosh, same thing Development is separated in many areas (design, base system, user APIs, drivers, etc) And the overlap between areas is significant. You need information flowing freely so you can come up with the best solutions (this is not 'design by committee') You also need independence and not justify every tiny decision (and why didn't you go with the 'safe' solution). This is the complete opposite of what happens in Japanese work culture http://www.hierarchystructure.com/japanese-business-hierarchy/ http://www.hierarchystructure.com/japanese-business-hierarch...
pj_mukh 11y ago
True and possibly also a lack of focus on product in general. Most Japanese products I know are STUFFED full of features too complicated to use (see: every Sony camera ever). Sometimes the focus should be on reducing the number of features to more comfortably insert yourself into the users workflow. This is probably true for almost every Japanese commercial robotics venture.

raverbashing 11y ago

More to the point, to have success in software development you need: - Independently minded people (incompatible with Japanese culture) - Flatter hierarchy (kind of relates to the previous point, and incompatible with Japanese culture) For simpler software, this is easier to overcome (Super Mario levels of software complexity, let's say) Steve Jobs didn't come up with the iPhone. He let people come up with great ideas then filtered them. In Japan, the structure goes: "What does the boss want?". And if the boss doesn't know, they will go with the most conservative choice possible. This set up is never going to win prizes.

my_username_is_ 11y ago
Can you explain why a flatter hierarchy is necessary for software development? My background is in hardware engineering, and this strikes me as surprising (although something I haven't ever given much thought to). What about software makes it incompatible with hierarchy? Don't a lot of traditional software companies have a sort of hierarchy?
- raverbashing 11y ago
  Don't confuse lack of hierarchy with flatter hierarchy. > Don't a lot of traditional software companies have a sort of hierarchy? Yes, see what kind of crap they produce. Of course, not all software companies, but the ones that really innovate can't survive certain environments > What about software makes it incompatible with hierarchy? The sheer level of independence that every part needs. In a hardware project you pick your parts (you have some requirements, some limitations in size, power, vendor, etc so it might be a choice between a handful of parts), then put it on a PCB, solve placing, routing, EM compatibility, etc. It's complicated, but you don't have too many people doing that. And more importantly, your boss knows more or less about everything and if he doesn't believe it there are hard constraints that serve as guiding (power consumption, EM emission, performance, etc) Good? Now, you want to build the software for the iPhone. Or for the Macintosh, same thing Development is separated in many areas (design, base system, user APIs, drivers, etc) And the overlap between areas is significant. You need information flowing freely so you can come up with the best solutions (this is not 'design by committee') You also need independence and not justify every tiny decision (and why didn't you go with the 'safe' solution). This is the complete opposite of what happens in Japanese work culture http://www.hierarchystructure.com/japanese-business-hierarchy/ http://www.hierarchystructure.com/japanese-business-hierarch...

pj_mukh 11y ago

True and possibly also a lack of focus on product in general. Most Japanese products I know are STUFFED full of features too complicated to use (see: every Sony camera ever). Sometimes the focus should be on reducing the number of features to more comfortably insert yourself into the users workflow. This is probably true for almost every Japanese commercial robotics venture.