I know vim, but I don't think that change much. In fact, if I lost a month of work and did not have any printouts or even notes, I would in most cases be able t

I know vim, but I don't think that change much. In fact, if I lost a month of work and did not have any printouts or even notes, I would in most cases be able to redo it in 2-3 days, and unlikely no more than a week. The reason is that I remember most of the decisions I made along the way, and don't have to spend time on making the right decisions about the code and architecture, since they were already made, and I would spend less time reading documentation and looking up how the problem can be solved in general. What I describe is at least true when you solve relatively complex problems, and is a relative experienced programmer that take most high level decisions about the code yourself. If you have a very junior position, where most decisions are made for you by others, and you work in programming languages and framework that require a lot of boilerplate, then what I said will be less true. Then using the right editor may matter at least a bit. Even in that case I doubt it is a major factor. On the other hand, using the right programming languages, libraries and tools may boost you productivity quite a lot, and have much larger impact than typing speed or input method.