3 ms·

Because move fast and break stuff doesn’t really work in non-software business I’d say.

twblalock 4y ago
But again, how is that a Japanese problem specifically, when the same risk aversion exists in corporate culture in other countries (as I mentioned)? The reality is that only a few countries are dominant in software, and they dominate to such an extent that they draw in software engineers from the rest of the world. That didn't happen because all the other countries have a Japanese business culture... A convincing explanation of why the world is that way needs to be based on traits that are not unique to Japanese culture.
- deleted 4y ago
  [deleted]
- olivermuty 4y ago
  Fair point, I don’t really have oppinions on that. My point was the inverse, that the archetypical Japanese approach to engineering suits the iterative careful development that hardware requires.
  - galaxyLogic 4y ago
    Right when the basic product can not change much it makes sense to improve it and the process to manufacture it gradually. Really Japanese quality movement was much about process quality. You produce the same thing but with a gradually improving process that brings in better quality and better efficiency of production. But because software is "virtual" it can change-shape in whatever way as long as it does something useful. The software products change rapidly whereas we are still in the beginning of trying to understand what are the best processes for producing it, why because process depends a lot on the product. So if the product changes fast process must change too. And when it changes fast it is difficult to improve it gradually.
brewdad 4y ago
Move fast and break things gets you established in the marketplace early and can bring some advantages from that. I have yet to see evidence that it leads to companies that survive for the long haul. At some point, people want products that actually work and don't completely change with a given update.
- amadeuspagel 4y ago
  You can still move fast and break things in development.

But again, how is that a Japanese problem specifically, when the same risk aversion exists in corporate culture in other countries (as I mentioned)? The reality is that only a few countries are dominant in software, and they dominate to such an extent that they draw in software engineers from the rest of the world. That didn't happen because all the other countries have a Japanese business culture... A convincing explanation of why the world is that way needs to be based on traits that are not unique to Japanese culture.

deleted 4y ago
[deleted]
olivermuty 4y ago
Fair point, I don’t really have oppinions on that. My point was the inverse, that the archetypical Japanese approach to engineering suits the iterative careful development that hardware requires.
- galaxyLogic 4y ago
  Right when the basic product can not change much it makes sense to improve it and the process to manufacture it gradually. Really Japanese quality movement was much about process quality. You produce the same thing but with a gradually improving process that brings in better quality and better efficiency of production. But because software is "virtual" it can change-shape in whatever way as long as it does something useful. The software products change rapidly whereas we are still in the beginning of trying to understand what are the best processes for producing it, why because process depends a lot on the product. So if the product changes fast process must change too. And when it changes fast it is difficult to improve it gradually.

brewdad 4y ago

Move fast and break things gets you established in the marketplace early and can bring some advantages from that. I have yet to see evidence that it leads to companies that survive for the long haul. At some point, people want products that actually work and don't completely change with a given update.

amadeuspagel 4y ago
You can still move fast and break things in development.