I might be in group 2, rely heavily on command line tools and vim to do what vscode and a load of plugins provides younger programmers.
My answer to the fairly common question of "how do you do it" is always the same though.
I always relay that it's taken an evolving 20 year career to learn all that voodoo, I never imply it's simple to gain that knowledge nor do I encourage others to change their working patterns to match mine. I do like showing off a few tricks though!
One thing I do always mention though is the longevity of vim + the command line. I went through a period of swapping IDEs like most junior devs, now I have a setup that I feel can last me till retirement and I can just continually invest in learning to use the same tools better
No that's not my point. Becoming very proficient at vim or knowing you way in depth around the command line takes time, years in my experience.
Maybe with 50+ years there's a limited amount left to learn, but with my 25 I'm still picking things up regularly.
So it's usually more junior and less experienced developers who ask "how do you do that" - sometimes with wonder, sometimes genuine confusion.
My answer is never "it's simple" or "it's just" but always something along the lines of "it's a culmination of using the same tools consistently for many years", usually followed by "hey have you seen this trick too".
My answer to the fairly common question of "how do you do it" is always the same though.
I always relay that it's taken an evolving 20 year career to learn all that voodoo, I never imply it's simple to gain that knowledge nor do I encourage others to change their working patterns to match mine. I do like showing off a few tricks though!
One thing I do always mention though is the longevity of vim + the command line. I went through a period of swapping IDEs like most junior devs, now I have a setup that I feel can last me till retirement and I can just continually invest in learning to use the same tools better