Requirements for j2ee developer

Discussion in 'Java' started by Sachin, Oct 16, 2006.

  1. Sachin

    Sachin Guest

    Hello All,
    I am a newly recruited software devloper and this is my first job. I
    allocated for a j2ee project.
    I know basic java; and things like networking, jdbc,rmi,servlets.

    I want to know what are the basic requirements a programmer should have
    when involved in a j2ee project, does he require a good knowledge in
    sql ?

    Thankyou all,
    Sachin
     
    Sachin, Oct 16, 2006
    #1
    1. Advertising

  2. Sachin wrote:
    > I am a newly recruited software devloper and this is my first job. I
    > allocated for a j2ee project.
    > I know basic java; and things like networking, jdbc,rmi,servlets.
    >
    > I want to know what are the basic requirements a programmer should have
    > when involved in a j2ee project, does he require a good knowledge in
    > sql ?


    Knowledge about standard SQL should be part of any developers
    toolbox.

    The database specific stuff you can just lookup
    in a manual.

    Arne
     
    =?ISO-8859-1?Q?Arne_Vajh=F8j?=, Oct 16, 2006
    #2
    1. Advertising

  3. Sachin

    Andy Dingley Guest

    Sachin wrote:

    > I want to know what are the basic requirements a programmer should have
    > when involved in a j2ee project,


    I'm part of a typical J2EE team of around a dozen. We don't need
    everyone to know everything, and we only rarely need one or more people
    to know the obscure stuff. The core that everyone knows would include,
    I suggest:

    core Java
    Design patterns (read the Gang of Four)
    Eclipse / Subversion / Bugzilla
    Web coding (some HTML (we need more!), some HTTP, some CSS)
    Some basic XML
    A very good understanding indeed of JSP / Servlets / MVC and what "good
    design" looks between the two of them !!!!
    Refactoring (read the Martin Fowler book)
    Agile / XP development (read Kent Beck)

    We also have quite a few people using Struts, JSF, SOAP, Swing, JDBC.

    There are a few specialists with XML, XSLT, Ant, database modelling,
    UML and Java internationalisation


    > does he require a good knowledge in sql ?


    It's an unusual project that doesn't need this. Usually though you're
    working in an office with plenty of SQL specialists around. You'll only
    need to do the easy stuff all by yourself.
     
    Andy Dingley, Oct 17, 2006
    #3
  4. Sachin

    Tom Forsmo Guest

    Sachin wrote:
    > Hello All,
    > I am a newly recruited software devloper and this is my first job. I
    > allocated for a j2ee project.
    > I know basic java; and things like networking, jdbc,rmi,servlets.
    >
    > I want to know what are the basic requirements a programmer should have
    > when involved in a j2ee project, does he require a good knowledge in
    > sql ?


    It depend a bit on where your focus is, is it front end or back end etc.
    But generally I would say that general SQL is good, but you should also
    learn more about a specific database or two, so that you are not
    completely blank when people talk about specific db details, f.ex. in my
    experience mysql is increasingly being used, Oracle is also used quite a
    lot.

    Other things you should learn are OO design and principles, f.ex The
    Gang of Four Book, or if that is to heavy for you (it is for many) you
    could try the Patterns In Java or even Head First Design Patterns.
    Patterns and are things you have to learn by practising how to apply a
    pattern to a problem. I think a good grasp of real-life concurrency is
    an important part. That is, after you have read the chapter in the java
    book about it, you need to look for the kind of design problems people
    are discussing on the net or in articles. One thing is knowing the
    mechanics of it, the other thing is, understanding it and how it affects
    the efficiency and correctness of you program. If you don't understand
    that then you will be chasing bugs forever. There are some excellent
    papers on the net.

    Another thing you probably should start learning immediately is Web
    Services, or SOAP. It is rapidly replacing most other RPC methods,
    because its simple in design and system independent, sort of the HTTP
    equivalent to RPC. Web services is the principle of system integration
    for which SOAP is based on. Learning it will help you understand how to
    best make systems that communicate with each other in the most
    transparent way.

    You should also understand XML and learn to deal with xml data.

    You should also learn the basic tools, a build tool, some test tools
    (e.g. JUnit), source revision tools, a development environment (choose
    one that helps you automate things as much as possible, because it will
    help you save time by avoid bugs, typing errors, compiler errors, and
    time spent on debugging.)

    You should most likely learn some web stuff, HTML, JSP, Web Framework,
    JavaScript, Ajax, etc.

    A last advice, learn to KISS (Keep It Simple Stupid) and that 50% of
    programming is about designing, choosing the simplest solution and
    maintainance of code. It will save you many agonising hours in chasing
    bugs or spending time on maintenance when you could instead be creating
    new stuff.

    tom
     
    Tom Forsmo, Oct 17, 2006
    #4
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.

Share This Page