4 ms·
Using an IDE is like playing the piano and putting stickers with the name of each note. There's no objective downside to doing this, but it's not really going
by enriquto 5y ago
Using an IDE is like playing the piano and putting stickers with the name of each note. There's no objective downside to doing this, but it's not really going to help you play better music once you go beyond the very basic stuff. It may give some people a false sense of security, but it won't make a difference to a professional programmer. Some of those programmers (but not all, and that is OK) will become annoyed at the stickers once they know how to play the instrument.
- thinkharderdev 5y agoI'm not sure the piano analogy is really apt. A piano has 88 keys (and really it's just the same keys repeated across multiple octaves) so any competent player will of course quickly memorize the keys and playing the piano would be impossible by actually reading the labels on the key anyway. Doing software development means using a variety of different standard APIs which many combinations of methods/parameters/etc as well as any number of custom, project-specific APIs. Sure, if you work on the same project using the same codebase for years on end then you can probably effectively memorize all the relevant APIs, but few developers are in that situation. You move from project to project and have to drop in to large, existing codebases with their own conventions and abstractions.