I develop exclusively in Jetbrains IDEs these days, and never let the IDE control the build. A working Gradle or Make target is required for CI/CD anyway. Our projects are officially editor independent and each contributor can use whatever they want. It is nice to click in a test and run it, but you can do that from command line too.

What I do get is correct autocomplete, documentation hinting, inline git hunk visualization, inline linter and compiler output, go-to-definition that always works and sees through implicitly satisfied interfaces, language aware refactoring tools, well designed interactive debugger, etc.

Sure you can hand assemble this stuff in Vimrc, or you can buy a tool that’s already functional.

Just one feature alone - being taken directly to compiler error sites - has saved me so much stumbling around from back when I was trying to be a shell purist.

As I’ve gotten more senior, I’ve really come around to the importance of investing in tooling (whether build or buy), having high expectations for tooling support, and having low tolerance for frustration/tedium/trickery. Not just IDEs. The right interactive debugger output, profiler trace, custom visualization, etc. easily pays for itself vs. trial and error or trying to squint at the source + output and reason about it.