Yes, when you have full blown IDE and use typed language. It is somewhat weaker when you have full blown IDE and use something like javascript (e.g. which find function from gazimillion find functions in project was it supposed to be)?
It is really weaker with sublime or vim, at least from what I have seen. They often did not found right function even when it was in the same file and there was no ambiguity - leading to harder to read code with deep nesting and loooong functions (that really should have been split into named steps).
It does not do that at all when vim user did not bothered to configure right plugins or did not bothered to learn them.
It's funny because I went from vim to intellij a year ago and recently tried out sublime text, and found my intellij code to be worse than my vim code. Mostly because intellij's auto complete and easy "go to implementation" makes up for (and can cause, if you aren't aware of the problem) a lot of quality issues - things you can't ignore in vim unless you want an codebase you won't be able to easily change.
I would gather that sublime text pushes you towards more focused, tight code, because their auto complete isn't context aware.
To your specific point, helper functions should be as close as possible to the function it is helping. If you have easy "go to function" functionality, some people will slack off on this.
I found the "tight" code collegues generated (quite possibly much different then yours) harder to read. It was pretty much impossible to read high level overview of what was supposed to happen without having to go through all the low level details. When things were split into smaller functions, I could come to unknown code and read it fast. Reading what it is supposed to do from vim written code took much more time. It was harder to mentally split it into self contained pieces that means something.
Refusal to use helper fuctions also led to a lot of code repetition in various (especially on click) handlers. When you have bugs from people forgetting to change fourth place where pretty much same thing is done, then the code is bad.
We had deadlines and I really think that everything would be way more effective if we took advantages of ide and generated code that express intent better and is composed of smaller units. Instead everything took longer and complexity was pretty much unmanaged (since they refused to use helper fuctions they never learned how to use then effectively nor how to effectively modularize code - the codebas was fine while small and increasingly unmanageable as it grew).
It is really weaker with sublime or vim, at least from what I have seen. They often did not found right function even when it was in the same file and there was no ambiguity - leading to harder to read code with deep nesting and loooong functions (that really should have been split into named steps).
It does not do that at all when vim user did not bothered to configure right plugins or did not bothered to learn them.