4 ms·
Always very wary about suggesting people cut their teeth in the warm embrace of a IDE. It's often unrealistic. If it's the industry standard —like it was and p
by oliwarner 10y ago
Always very wary about suggesting people cut their teeth in the warm embrace of a IDE. It's often unrealistic.
If it's the industry standard —like it was and probably still is completely normal to use VS.NET for .NET development— that might be okay but reducing exposure to things that the rest of your industry like a makefile or [gp]db, Maven/Gradle/Ant, or whatever... It's a real disservice to your students.
If you're an educator and you want your students to get a job, make sure you're teaching the stuff we're actually using.
- jsight 10y agoI'm not sure that I get your point. Is there anything about using an IDE that keeps you from learning a build system? Although I do think it is unfortunately that a lot of CS courses pay little attention to build tools.
- oliwarner 10y agoThere's nothing stopping you learning other stuff but I've found from both personal experience and dealing with new hires, people like to stick with what they learnt on. My experience is green graduates who grew up on IDEs struggle —for much longer than you'd expect— to get on with command line scripting and tools. They avoid a lot of very necessary experience when you have an IDE do everything. I'll stop well short of saying "real programmers only use VIM" but experience is everything, especially when differentiating juniors. Learning how to do everything with one IDE is a great way to get very little real-world experience.
- jsight 10y agoThat is a fair point, although my experience was that the IDE didn't matter much. Most of my fellow students didn't learn build systems regardless of whether they worked in the popular IDE at the time or just a text editor. I would hope that build systems would be taught regardless of the IDE.