So, a very basic IDE -> basic text editor -> command-line (emacs, vim) -> a full fledged IDE is probably a really good way to learn. Why? Because it eases you into programming without the help of an IDE. It would be easier to learn to code in vim then go into an IDE, than to use an IDE before using a command-line interface.
That's dumb. Yeah, I suppose it would be difficult to go from IDE to CLI, but why would you do that? That's like saying you should learn how to cook by rubbing sticks together before moving on to an electric stove.
Also, it forces more good practices since some IDE's might have auto-complete and such meaning you don't have to think about your code as much.
I think you have very little experience with actual projects if you think that's what "good practices" and "thinking about code" entails.
Using an IDE's auto-complete features means you don't have to worry too much about
syntax, which is a good thing if your IDE is smart enough to get the auto-complete right on a consistent basis. It frees you up to spend more time thinking about code structure, and actual good practices, like separating concerns and other practices that help make sure your code will be readable by someone who isn't you.
---
http://thecrankyhermit.wikispaces.com/
Year-by-year analysis of the finest gaming has to offer, and (eventually) more!