Earlier quoted context omitted.
I think the sane architecture is the only relevant part. Real world "10x" developers are almost always in that class because they can solve the same problem with 1/10th the code of a 1x developer. Ability to solve problems with less code will always outpace faster typing.
To be clear, you don’t mean code golf levels of code-shortening, right? E.g. they’re also not sacrificing on clarity and readability of code to shorten it. They’re just removing unnecessary work. I think this is definitely good and creates a net gain for other devs. Because the people who shorten code at the cost of clarity are some of my least favorite people. I once saw “half = num >> 1” instead of, say, “half = fl…
half = num >> 1
Was standard practice and understandable by most engineers, as well as far and away much faster than a divide.
Now-a-days, using a compiled language they are going to be translated into the same machine code supporting your point. However, it might still be a good idea in a scripting language doing heavy math lifting.