Currently, I’m reading Bruce Eckel’s book Thinking in Java, for the second time. About 2 1/2 years ago, I got a new job where I’d be a Java developer, despite the fact that I didn’t know Java. (I was hired for my web expertise under the assumption that I’d pick up the language.) Now that I’ve been at it with Java full time for about 30 months, it’s time for me to go back to the book to pick up all of the things that I glossed over the first time around. I’m hoping to pick up more about threads, I/O, inner classes, and collections. I’m also hoping to pick up lots of other syntatical tricks that were utterly lost on me when I first learned Java. I just skim the parts that I already know really well, and it’s going pretty fast. Hopefully at the end I’ll be a much better Java developer than I am now.
Back to basics
Currently, I’m reading Bruce Eckel’s book Thinking in Java, for the second time. About 2 1/2 years ago, I got a new job where I’d be a Java developer, despite the fact that I didn’t know Java. (I was hired for my web expertise under the assumption that I’d pick up the language.) Now that I’ve been at it with Java full time for about 30 months, it’s time for me to go back to the book to pick up all of the things that I glossed over the first time around. I’m hoping to pick up more about threads, I/O, inner classes, and collections. I’m also hoping to pick up lots of other syntatical tricks that were utterly lost on me when I first learned Java. I just skim the parts that I already know really well, and it’s going pretty fast. Hopefully at the end I’ll be a much better Java developer than I am now.
Commentary
Previous post
On the other hand …Next post
The ICC