I'd argue that by spending less time configuring and learning an editor, you have more time to actually focus on the code and architecture itself.
Note that things like code completion, method extraction, and all the things filed under 'intellisense', are perfectly doable by the human brain, but those tasks can be done/automated more accurately (i.e. with less errors) and with less effort by your IDE. That's essentially devops-before-devops.
Thanks for commenting Alain!
I agree that human brain can handle those tasks but people build machines, robots to make some trivial tasks for them. Why shouldn't they do it?
Note that things like code completion, method extraction, and all the things filed under 'intellisense', are perfectly doable by the human brain, but those tasks can be done/automated more accurately (i.e. with less errors) and with less effort by your IDE.
Then again, the less you "need to" do yourself, the less you will understand about what happens. Never underestimate the laziness of your brain.
I'd argue that by spending less time configuring and learning an editor, you have more time to actually focus on the code and architecture itself.
Note that things like code completion, method extraction, and all the things filed under 'intellisense', are perfectly doable by the human brain, but those tasks can be done/automated more accurately (i.e. with less errors) and with less effort by your IDE. That's essentially devops-before-devops.
Thanks for commenting Alain!
I agree that human brain can handle those tasks but people build machines, robots to make some trivial tasks for them. Why shouldn't they do it?
Then again, the less you "need to" do yourself, the less you will understand about what happens. Never underestimate the laziness of your brain.
Well, I can see what you're saying.
I never do. It's a significant contributing factor to humanity having the technology we have.