In my years of pretty much working only in Visual Studio/C#, I've occasionally poked around in vim for a few things and always immediately turned back. It was j

In my years of pretty much working only in Visual Studio/C#, I've occasionally poked around in vim for a few things and always immediately turned back. It was just weird. I didn't see the benefit of giving up all of the features and familiarity. Recently, I've found occasion to work in other languages, and after dabbling in vim for a little while, I switched to VS Code. After gaining a little bit of enlightenment about what a comfortable developer workflow looks and feels like outside of the C# ecosystem, I've had three key insights: - I actually appreciate the transparency and flexibility of delegating so many tasks to command line tools that can be run via scripts and task runners. Thing still aren't quite as discoverable as they are in VS, but I have enough general dev experience that I know what to Google for. - I still don't care for vim. Maybe someday, when I want to invest time in becoming a keyboard Jedi. - Most importantly: it turns out the only feature I really, really missed leaving Visual Studio was IntelliSense. Not just semi-intelligent word completion, but real IntelliSense, with inline documentation, snippets and parameter info. I don't know why anyone who has ever taken advantage of it would go without it if given the option - it is a bicycle for the programmer's mind at every skill level, from early discovery of a language's syntax and standard libraries to extreme proficiency.