I suppose I agree with this, I try not to obsess over the tools too much. It makes sense to have a standard IDE and standard tools in the company. However it's always a possibly to improve. One can suggest new tools to a small circle of coworkers, or just start using them on one's own. In most situations it's possible to install and use vim as an accompanying tool. In one workplace that has a huge Windows codebase I compile and debug from within Visual Studio, and edit either in Visual Studio or sometimes vim. When I get the chance to do explorative work on a rather standalone project I gravitate towards vim, even to printf debugging, even though Visual Studio is available. I don't know why this is, old habits, or is it genuinely more economic on some axis?
Sure IDE's are great, I love stepping through code, it really helps when you're in deep and are having problems reasoning about the state of your program.
That said, every shop I've worked in used a different IDE. Possibly one picked out by some long gone coder who thought that their choice was the best.
Finally not being saddled to any one IDE lets me use the any other tool to get a job done.