btw, LSP is not the only way to make go to definition work.
The fact that the market hasn't outright eliminated such people goes to show that things like LSPs aren't that extreme of an advantage.
But that advantage becomes a weakness when you need more complex text replacement or specific repetitive actions.
That is why I use vim with an LSP, I find it to be the best of both worlds (especially the macros in vim): a smart but limited tool, and a dumb but powerful one.
Maybe we'll get a smart and powerful one some day (but I doubt it).
I expect that especially hardcore and purist Vim users (the likes that does not use any plugin or configuration) should know to use macros and other available tools (not even mentioning bash) to make the work faster.
With enough experience on those, you can get a level of productivity that is not much different than IDEs like IntelliJ.
The intern was tasked with a large-scale refactoring of some modules which the senior devs estimated would take months of work to complete. After shadowing a senior dev to get an idea of the work involved, they realized the dev was literally string replacing a lot of the code, hence why the estimate was ridiculously long. The intern instead loaded the project into IntelliJ and used the built-in refactoring tools to get the task done in a couple days. This caused a bit of an internal shit-storm with the product owners because the intern made the devs "look bad".