Having been where you are not to long ago, and still there in a lot of ways, I would suggest using the command line. It's more error prone and will take you longer, but I think in the long run you will be better at understanding error messages and understanding the relationships between your code, other in-house code, third party libraries, and overall directory structure. These are some of my weaknesses which I think are due to relying too heavily on an IDE to set things up. There is a lot that IDEs do behind the covers for you that you might not understand if you learn via IDE.
If you choose to learn via an IDE, or switch to one at a later point, I don't think it matters which one you use. I think most of the major functionality will exist in the major vendors. They may do it differently in somecases, or you may have to download add-on packages, but for the most part they all do the same thing. Pick one and learn it well.
Michael K. Craghead
Java Official Group is created for the following topics: Java 2 Enterprise Edition - J2EE, Java 2 Standard Edition - J2SE, Java 2 Micro Edition - J2ME, XML, XSL, XSD, XPATH, Web Services, Jini, JXTA for all type of Java Geeks.
Whoever posts spam / ads / job related message will be BANNED IMMEDIATELY
No comments:
Post a Comment