VisionSet said:
Write alot of code. The syntax is the least of your problems. Writing
good
OO code takes time, is pretty much essential and is many times harder than
remembering syntax.
Don't mean to be discouraging, but if you keep writing code, the syntax
will
be 2nd nature.
It's like anything you have to do the thing to get good at it, books are
good, classes are better, the internet is a valuable resource, but you
have
to know when to take advantage of each, generally do a bit of all of them,
but above all write code! If possible get an expert to review it. (I'm
still
looking for that expert). comp.lang.java.* is a good resource though with
a
good bunch of people, I've learnt more good Java here than anywhere else.
I just want to agree with what Mike has said. The best way to get better at
programming is to WRITE PROGRAMS, not to read about it. There's nothing
wrong with reading programming books: you have to get the basic information
somewhere. But the way to progress is to _write code_.
If you were interested in being a football player but had only played a few
games, which approach do you think would make you a better football player:
A. reading lots of books about football strategy?
B. watching lots of football games on TV?
C. playing lots of football?
I think the answer is obviously "C". You might learn a few things from "A"
and "B" - but I think you're going to learn a lot more by playing than
reading books or watching other people play.
Programming is pretty much the same deal. Writing code - and compiling it
and testing it and debugging it - are where you really LEARN how to program
well.
If I were you, I'd find a project that interests you and then devote all the
time you can spare to it. For instance, if you're interested in the stock
market, write a program to track stocks and even buy them and sell them - or
at least make recommendation for what you should buy and sell. If you're
interested in music, write programs that will play your favourite music
files or organize those music files so that they are easily found when you
want to hear them. I find that working on an interesting project is one of
the things that makes me want to program; if I have to write a program about
something that doesn't interest me, it is harder to sustain my interest.
Memorizing syntax of statements is _not_ a very good use of your time, in my
opinion. While it might be handy sometimes to have everything memorized, I
feel that it is a better use of my limited brain cells to use them for the
creative and imaginative aspects of programming than to cram them full of
facts that I can easily find in a reference book or API.
Rhino