|
|
|
|
|
|
by Grexception
4223 days ago
|
|
|
Protip: If 80% of your agument is an analogy, it's probably not a very good argument. I think the opposite is true, IDEs help you find out what is really going on, by showing you (depending on the language) which module is used where and giving you the option to directly navigate to that source. That in turn confronts the beginner with the code and conventions of other (more experienced) coders. So yeah, IDEs rock. Also debugging... |
|
|
IDE's are great if you use them. Editors are, too. But the point is that an over-reliance on IDE's will degrade your skills, generally, and command/control over your project, precisely because it does too much work for you, and your understanding of the subject thus atrophies. If I had a Btc for every new-school "IDE's are the awesome, can't live without them" superstar programmer who nonetheless couldn't navigate his way around the build system, or even directory hierarchy for their very-valuable software system, I wouldn't have to write software for a living. Probably.
It is sage advice, this "don't become addicted to your IDE" statement, because IDE's are also a walled garden, folks. There are reasons the "Developers^3"-mindset was so ironic way back then; if, as a platform vendor, you capture developer mindsets then you safeguard your platform from being undermined by your competition: other developers. Never forget that its turtles, all the way down, folks .. and your average modern IDE is a big, hungry, fat one.