You, yourself, should not let your control over the project be 'usurped by complexity'. If you can't handle the complexity such that you need an IDE to do refactoring, you should definitely not promote this fact far and wide - its far better to promote the style of thinking where IDE is not a requirement, but rather a luxury.
It means there are parts of the project you really don't have an embracive grip over, and that does not make you a great developer. It makes you a weaker one.
No, it means that I consider there to be a difference between language constructs, variable names, strings, comments, etc. - in other words what a parser does. String/based find-replace muddles these together. An IDE is but a collection of similar tools. I’m not strong if I choose to walk and weak if I choose to use motorised transport.
You're weak if, after using motorized transport to get around most of your life, you're suddenly asked to walk - and can't do it.
Look, there's no point arguing about this any further - but I urge you to look at this alternative point of view in your professional career. Without fail, those whose proficiency depends on the features of an IDE are, in my experience, more glib about their work and problem solving, and less likely to actually push to solve common programming problems on their own. Maybe you'll start to notice this too.
