As a lawyer and programmer, I use text editors daily.
I have 3 loves I cycle between: Sublime Text, JetBrains IDEs, and Vim (separately or within Visual Studio Code).
Over the years I've significantly revised the key bindings of the first two to accommodate my workflow, for a pure keyboard-only/mouse-less experience.
My familiarity is such that I never have to think about my fingers at all these days. I work based on motor responses; my fingers respond to my thoughts almost as fast as I can interact with whatever's on screen. (Which is why I can't stand writing by hand anymore; it's too slow.)
Some thoughts, with consideration for muscle memory, comfort, and speed:
Sublime Text - I use STX for everything in my life: writing, editing, and code, due to its powerful build system, programmable Python internals, snippets/macros/extensions, etc. My keybindings are tied to my most heavily-used packages, and to handle split cursors/motion/text segments at speed.
JetBrains IDES (i.e. PyCharm/Datagrip/Clion) - for large codebases, I prefer the JetBrains suite. My keybindings there reflect STX's almost entirely, but with variations to account for the IDEs' numerous dialogs/modals, run/debug configs, editor/terminal jumps, etc. My gradual improvements have all been aimed at removing finger dissonance when context-switching.
Vim / Visual Studio Code - I do a fair bit of terminal work and Bash automation in Vim. Unlike the heavily modded STX/IDEs, I prefer a vanilla Vim experience, with minimal packages (e.g. fzf.vim). So as to keep my Vim chops current, I use Vim keybindings entirely when running VSC.
I confess: this decision is mostly ideological. Vim is an impervious text-editor for POSIX devices - and its keybindings are immortal. I always want Vim as a non-IDE alternative, particularly for remote work. Most importantly: I like Vim. I enjoy Vim's motions; they feel fancy. Like I'm flying everywhere.
However, since my STX-like bindings live alongside Vim's motions in VSC, the experience can be... interesting. Things feel different. For instance:
CTRL+A selects all, but doesn't actually work - I still must do
Certain conveniences remain accessible - e.g. CTRL/ALT modifiers for window dialogs, standard shortcuts like CTRL+S, etc, on top of Vim's
I use hyper keys for motion/navigation (particularly with the Caps Lock key, which I've rerouted via
xmodmap) in addition to standard arrow keys, - and on top it, Vim's own motions.
Juggling key bindings between editors can be quite the fun exercise when you're new to them! But honestly, motor memory is a boon. Switching between bindings has never been a real hurdle, and the boost to productivity really improves my writing/coding happiness.