Productivity in programming is measured from the time you start a project till the time you finish. So much time is often spent trying to find and fix bugs, and being productive is all about writing code in a way that minimizes the amount of bugs that show up, and being able to quickly find and fix them when they do.
Writing code at the optimal level of generality is a major factor, No amount of editor tricks can make up for choosing the wrong level of generality to write your methods. Too much generality and you are wasting time, too little and you have to deal with a bunch of special cases, or else rewrite large portions of code at some point.
It's important to be able to learn things very quickly on the spot when you have no other choice, but it's better to be able to immediately deal with situations without having to incur all of the productively losses that comes with doing that. So much time is saved by being able to get the algorithm's and the numbers right on the first try.
It's also about a psychological battle of how hard you can push yourself without burning out, which is no trivial matter.
Once you are good at all that, then basically it's nice to also be able to pick up an extra few seconds here and there with a keyboard shortcut, an editor trick, or some precision mouse mechanics.