|
Whatever works for you. I'll just say three more things.
1. When a problem occurs (in the production environment where your IDE will not be available) will you actually understand what has gone wrong and how to fix it? Probably not.
2. When your company says "We've switched to IDE a as IDE b is whatever, so we will no longer use it." and IDE a is completely different from IDE b, how long will it take you to get used to it, when you don't understand the processes behind what you where doing with the other IDE?
3. I've seen this argument of "getting productive ASAP" so often, I'm getting sick of it. Never put being able to limpingly jog today ahead of being able to sprint like a champion tomorrow, which is usually what happens you apply that "getting productive ASAP" label. Being able to finish your assignments quicker because the IDE is able to tell you how to spell something (when what you should be using is already clearly defined) is a difference of maybe a few days over the long haul while learning. But the benefit achieved from having learned it the right way first, then going to an IDE and getting that bonus added to what you really learned, is made up in a very short time, and the person that learned it the right way is then much more productive than the person who learned it on the IDE. That argument is the lamest excuse for taking shortcuts that anyone has ever thought of, and everyone uses it.
|