I feel like this is a bit like click bait. Don't get me wrong, my career has been enormously helped by Japanese developers. (Thanks Matz) But "works better" i

I feel like this is a bit like click bait. Don't get me wrong, my career has been enormously helped by Japanese developers. (Thanks Matz) But "works better" is a hard claim when there are very few pure software tech firm in Japan that are also globally dominant (would love to hear of them if they exist). I have never in my entire career at startups, consultancies, BigTech, or Fortune50s heard _anyone_ ever care about tabs/spaces or JS frameworks beyond "oh this approach is interesting, lets try it" Additionally I don't think "The secret? They treat code like a Toyota Camry, not a Tesla." is the flex the author thinks it is. Finally, development speed is incredibly important. Napoleon is credited with saying "quantity has a quality all its own", in software it is "velocity has a quality all its own". As long as its not complete slop and has some safe guards, consistently moving very quickly fixes almost every other deficiency. - It makes engineering mistakes cheaper (just fix them fast) - It make product experimentation easy (we can test this fast and rever if needed) - It makes developers ramp up quickly (shipping code increases confidence and knowledge) - It even makes rigor more feasible as the most effective rigorous processes have to be light weight and built-in or they go unused. Code shouldn't be built to last decades, it should be built to be changed quickly and easily. Every line of code is a liability, the system that enables it to change rapidly is the asset.