|
I have another hypothesis. Japan is a nation of craftsmen. As such, Japan excels at enterprises involving the manipulation of physical objects, like producing cars, cameras, knives, industrial equipment, computer hardware, etc. If you've ever been to Japan, you'd notice that it is a nation where physical objects/systems are very much prized. On the flip side, Japan doesn't seem to do as well with abstract objects. I'm specifically thinking of software here. You see, the modern practice of software development is heavily tied to American/European culture, where technology norms, though ostensibly universal, find a natural home in the English language. Consider concepts like generics, devops, dependency injection, static vs dynamic typing: all of these were conceived in English-centric environments. Sure there's nothing linguistically specific about them, but they reflect discourses that happen primarily in English-speaking spaces. If software development were more mathematical (and maybe more like electronics... somehow less tied to English), I suspect the Japanese would do much better than they are doing right now. (Ruby's Matz is a notable exception, and I suspect his fluent English had something to do with it) But the fact is, the practice of software development is as much sociology as it is engineering. Large swaths of it are inextricably linked to the culture, norms, and languages of Americans/Europeans. Without a good command of English, one finds oneself merely consuming content but unable to influence the discourse. |