The point is that this kind of productivity does not matter at all. I mean, not even 0.00001%. We deliver complex hardware + software products that have to wo

The point is that this kind of productivity does not matter at all. I mean, not even 0.00001%. We deliver complex hardware + software products that have to work correctly under challenging conditions and, ideally, not kill anyone in the process or burn down entire buildings. We do not deliver code-entry athletic performance. In a typical project code entry time is so ridiculously insignificant that I would never hire anyone who came in and made the typical vi/vim argument about efficiency. This would instantly tell me they have no mental connection to what is actually important. Another element is that, when you work in a multi-disciplinary environment you don't necessarily have the luxury of sticking with one tool. Which means devoting a lot of time on something like vi is pointless. Another view: Say you have a team of 100 software engineers and you have to get a complex product out the door. Would taking a month off to train everyone to become a vi/vim ninja make this team deliver properly working bug-free code sooner and at a lower cost? The answer is, of course, no. Or, more accurately, no f-ing way. That's why this cult of efficiency is misguided.