4 ms·
We can't remember all the methods our code needs to call, so we use autocompleting IDEs to remind us. I thought memorizing all of the details of these was only
by argv_empty 16y ago
We can't remember all the methods our code needs to call, so we use autocompleting IDEs to remind us.
I thought memorizing all of the details of these was only important in school, and even then only at exam time.
- olavk 16y agoI always thought it strange to consider it 'cheating' to rely on a powerful IDE. A programming language is a tool - nobody think it is cheating or a sign of weakness to use the most powerful/productive programming language suitable for a task. An IDE is similarly a tool, which complements the language - just as the code we write is basically a tool.
- regularfry 16y agoNot true. If you have the details in your head, you can manipulate and compare them far faster than if you have to rely on an external tool. That means you can rehearse more ideas, faster, which will lead to a better likelihood of picking the best one.
- points 16y agoRemembering things is VERY important. It means you have an instant grasp of the code base, the APIs available to you. It means you can solve problems much quicker than someone who only has a limited memory, or uses auto-complete all the time.
- kenjackson 16y agoRemembering the right things is very important. I know the code base far better now with an IDE than I ever did without one. Because it lets me focus on what is really important in the code. I get to focus on code structure, algorithms, I can quickly drill into the code and back out. I can in a few seconds see all uses or all definitions. The thing that makes IDEs great IMO, is when I'm looking at code that isn't mine. The ability to abstract structure from other peoples code quickly is a godsend.