Quickest way to come up to speed in Java?

Discussion in 'Mac Programming' started by ChrisA, Dec 3, 2008.

  1. ChrisA macrumors G4

    Joined:
    Jan 5, 2006
    Location:
    Redondo Beach, California
    #1
    What's the quickest way to come up to speed in Java and the java Beans IDE? I don't need to learn programming.

    Some background:
    I've got 25+ years full time experience with C, C++, Ada, Perl, Assembly and lots more. I just found out I need to fix a long list of bugs in a large Java based system. It's an industrial control app that has interfaces to many devices and a GUI. As they say a "non-trivial" application. I've worked on this kind of stuff for years but just not in Java or java beans.

    I's not like I can't find a book on this subject. But which to get.

    Thanks.
     
  2. toddburch macrumors 6502a

    Joined:
    Dec 4, 2006
    Location:
    Katy, Texas
    #2
    Well, you know OO concepts, and you know programming concepts and syntax.

    And you are taxed with fixing some bugs and/or adding some features.

    Just hop into it. With all that background, it's not that big a deal. You might spend more time on learning the IDE than than language.

    (Did you mean Netbeans IDE?) I don't know how good Netbeans is, but Eclipse is awesome - syntax checking as you type, so once it tells you there are no syntax errors, your compile should work perfect.
     
  3. ChrisA thread starter macrumors G4

    Joined:
    Jan 5, 2006
    Location:
    Redondo Beach, California
    #3
     
  4. plinden macrumors 68040

    plinden

    Joined:
    Apr 8, 2004
    #4
    The standard Java APIs are well documented - eg. http://java.sun.com/j2se/1.5.0/docs/api/index.html

    If you come across a Class that's not in the JDK, just google for the full class name followed by API (e.g. google for "org.hibernate.query.Query API") and the JavaDocs are usually in the first couple of results.

    On the other hand, custom inhouse APIs are generally not well documented due to laziness.

    I second the recommendation to use Eclipse. Its syntax checking and auto-completion means I hardly ever look up API documentation any more. That's not to say that Netbeans is not a good IDE - I've used both - but I just prefer Eclipse.
     
  5. Cromulent macrumors 603

    Cromulent

    Joined:
    Oct 2, 2006
    Location:
    The Land of Hope and Glory
    #5
    Eclipse is okay but I find it rather poor when working with JSP. Slow too.
     

Share This Page