I can't really agree with this. I get the point, obviously - sometimes, IDE or text editor features end up curing the symptoms rather than the disease. That's v

I can't really agree with this. I get the point, obviously - sometimes, IDE or text editor features end up curing the symptoms rather than the disease. That's valid, insofar as it's probably a bad sign when a coder has to enter loads of boilerplate, or struggles to remember the correct method to call from a sprawling API. But good coders solve these issues regardless of having tools that make them easier to ignore - and I don't think that making it more time-consuming to write code, for the 99% of the time I'm not doing that, is worthwhile. I want to enter a few lines of messy code, and have my editor automatically format it; I want to be able to find all uses of a particular function across my codebase; I want my linter to pick up syntax errors or unidiomatic code before I get to the point of running it; I want to be able to autocomplete tokens; I want to easily select and move blocks of code without fiddling with a mouse. These are all features which make it easier to refactor, and not more difficult. Perhaps this is more valid in the context of people using IDEs rather than text editors, and I'd argue that when working with a new stack it's always worth having a crack at using a text editor/command line environment over an IDE to get a better feel for the environment. Whatever works most effectively for you, at the end of the day.