I do face this as well. Age does slow down a person. But age also helps us make haste slowly. I've seen younger engineers scattering their energy around, and then coming to realize that the common sense option was the best. And older programmers (like me) might be too set in our ways.
Can an old dog be taught new tricks? I'd say to test that, make sure you learn a new programming language every year. Show it with non-trivial projects on your github or other profile. Thats proof that you're still sharp.
Edit : Also adopt a new editor every year. That shows you can step out of your comfort zone. (I need to kick that emacs habit).
So rather than learn a new language every year I aim to learn something about the languages I already spend most of my time in. Functional techniques in Python, the new features in C++14... things like that.
Nor do I see any value in learning a new editor. Really, editing is a solved problem and if you're familiar with vi, teco, emacs, VisualStudio, Eclipse and that other one whose name I don't remember that Microchip based MPLABX on you've covered enough ground that anything you encounter is going to look basically familiar.
I've met programmers young and old who won't leave their comfort zone that I acknowledge it's a real problem, but I don't think you need to spend too much time very far afield of your core expertise to keep current.
I'm fine with having bled the captains of big data and presentation (thereof) hysteria of enough resources to live the rest of my life on comfortably, and now enjoy embellishing whatever terminal window I'm inhabiting to suit my needs of the moment.
I'm happy in vi, wish I'd stuck with emacs, blah, blah. But when you can make things happen in a terminal window, does it really matter?
Personally, I'm finding a ton of joy in Lua. So clean and simple and fast and portable and easily extensible in venerable 'ole C. So much to love!
I have never used emacs, but vim is horribly limited in what it can truly do in terms of handling code. You can add all the nifty little plugins you want, but it just isn't efficient. The mistake people make moving to a full IDE is installing the vim plugin to add some familiarity. I've seen coworkers take literally 5 minutes to hammer out the vim keystrokes to refactor a block of code that can be done in 15-30 seconds with 2-3 native IDE keyboard shortcuts and a mouse click or two. It's important to know how to use vim or similar for remote command-line work. When developing though, the functionality and built-in tools provided by a full-fledged IDE are priceless.
There was a time I didn't judge new developers for using vim to edit code - and a long time ago I was one of them. I used to see these people as "true developers" for mastering an editor like vim. Now, after years of encountering developers with hampered productivity and ability to work on a team with coding standards, I see a vim/emacs person as someone who is stuck in their ways, refusing to even try to modernize their workflow.
Just a random example: in PHP projects, my teams use CodeSniffer for coding standards validation. The settings for common IDEs are committed to the VCS so they are automatically in place for new developers cloning the project. In any modern IDE, notices/warnings are instantly and unobtrusively made available as you type code. You can also run the inspection against the entire codebase or files you have modified since last VCS update to catch anything you missed.
What do Vim users do? They write code for hours or days at a time without validating what they are writing. When done, they either a) commit without running their code against CodeSniffer while egotistically proclaiming that their personal coding style is clean and doesn't need to match what the rest of the team abides by; or b) they spend hours running the command-line version manually, ridiculously trying to parse the output and hunt each problem down.
This is the real problem with vim/emacs users. Nearly none of them are capable of following the same coding practices as the rest of the team who are sharing a set of project settings in modern IDEs. The worst I've seen was a team that had once had amazing code quality completely abandon all forms of coding standards when two new senior developers were hired who both used vim. They refused to follow the standards because vim simply doesn't contain the necessary tooling. The entire codebase went from being beautifully clean to a complete mess, all because the new guys used vim. That was the job I walked away from so fast after fighting over the ridiculousness and then learning that both new developers were basically hired for the simple reason they went to the same university as the hiring manager.
tldr; Use vim/emacs if you want; but if you're not going to be as productive as, or match the code quality of, your teammates - that's a problem.
Honestly, I have seen so many developers fumbling around with their "intellisense" and the kinda of things you are talking about, it makes me sleepy watching them. I feel like if only spent time learning how to program than their code completion and refactoring tools, they might produce better, more efficient work.
Web browsers were created by emacs users. The entire industry we make a living in came from the belly of emacs.
But 2 guys at some company refused to follow coding standards, so yeah...
The problem is when they don't do it right, and it's impossible to configure it to have the correct behavior.
For example, JetBeans, when you type a ", automatically inserts the matching ". I couldn't figure out how to disable this feature, and it leads to strings like "data"".
Don't judge text editor users based on your experience with a few people. Writing code for hours without style checks or execution is not a common workflow for an emacs user. I've met quite a few inept Eclipse and Visual Studio users but I know better than to correlate IDE's with traits.
To me, Vim or Emacs are more like a violin, and software that enforces style more like a kazoo. While some might consider the sound of the latter music, those with ears to hear - and hands to play - know better.
I'll take a developer who can create consistently beautiful code in Vim or Emacs over someone who can't be as productive without style-enforcing crutches any day.