>> Like say, writing Windows software in Visual Studio? If you can't wean yourself off the IDE tit that's exactly what you'll be doing.
Yeah, that's it, go ahead and make your childish remarks. We'll all wait until you've grown up enough to continue the discussion.
>> We don't use IDE's at my work (and that's at NASA). IDE's have their place, and their appeal is understandable, but programmers owe it to themselves to learn the language and the underlying tools that the IDE encapsulates.
Well lets all pat you on the back. Fact is, a company that doesn't allow the use of an IDE is rather ignorant. There are plenty of useful reasons why you'd use one and to not allow that just doesn't make sense. I've never been in a company that wanted their developers to work slower or less effectively.
>> IDE's can also have the side-effect of injecting dependencies into your build system that needs expensive porting and maintenance when said IDE is superseded.
I've never encountered that and if in fact you do, choose another IDE. There are plenty of options out there. There's no reason your IDE should get in the way of your development, build, or test processes.