I kind of view IDEs like that. You can use it as a crutch, or you can take the energy you would have used thinking about the things the IDE is now doing for you and focus it elsewhere.
IDEs are similar. If you want to be as efficient as possible and get as much done as possible, you want an IDE. But if learning and exercising your mind is the goal, you’d be better served with a text editor.
We see this in London cycle lanes. Some cycles are doing a commute, some are trying out for the olympics, some people are doing 25 on a electric scooter and these are alien - hard to predict because they don't obey our intuition about physics. A guy on a scooter does 10mph tops and puts his foot down a lot.
On a steep enough descent, a cyclist could get up to speeds beyond 50 mph, which really isn't safe given the equipment.
(They've also done some more motorized cycle and electric content lately. A recent video showed how to rebuild an old motorcycle's frame into an electric motorcycle using a kit.)
I see, your own peddling can make them go faster. Ok these things should be illegal!
So, at large, I would guess the "as a crutch" use happens far more.
Nitpicking, but in the world of regulations, electric assist tapers off until around 25-30 km/h, at which point you start carrying the entire bike anyway, plus the dead weight of the battery and the motor.
I wonder if this simile could be extended to programming. Being hindered by not being able to choose your own tools?
I live out in the country in Australia. I’m planning a velomobile with an auxiliary motor for both touring and local use, and with this combination I expect and hope to attain an average speed of over 50km/h for the ~39km trip to the nearest town for church and groceries on Sundays. (I currently tend to average 22–24km/h on my recumbent tricycle with no motor, the trip typically taking 1h35–1h50m, with an estimated average power output of 120W. 200W is quite a lot to add!)