Then once you sit down, its about reading the code, analyzing it, re factoring it, debugging it. For all those things, typing is almost irrelevant. If your typing efficiency actually makes a dent in your productivity in the grand scheme of things, your job is probably outsourcable.
This, right here, is the point. I can type in text in just about any editor ever created. But navigating through a pile of code I don't know, to find how it's structured, its call chains, what data belongs to which subsections? That's where a good IDE provides true value to me.
I use SlickEdit because it has the most functional code navigation I've found. Ctrl-/ and a sub-windows shows me every reference to a symbol, in a tagged list showing each reference, by file, and information about where it was referenced (in what scope) and how (defined, declared, called, assigned, read, other). Click on one of them and I'm taken to that reference. Ctrl-. and I'm taken to the definition of the symbol my cursor's on; Ctrl-, and I'm back where I came from (to an arbitrary depth). I use this to navigate through unfamiliar code following through call chains and data structures. 20 years ago I used grep, a text editor and a whiteboard (foo.c:782, foo.h:94, foo.c:122, bar.h:15, qux.s:343), but never again.