Popular @
Forum Controls
Spotlight Features
The Rich Engineering Heritage Behind Dependency Injection
Andrew McVeigh takes us on a tour of the rich heritage behind dependency injection, what it represents, and tells us why its here to stay.
NetBeans 6: Matisse Updates
NetBeans 6 delivers great updates to the Matisse GUI builder. Spend a few minutes with Roman Strobl and get an expert briefing on what's new and what has changed. (sponsored)
Introduction to Groovy Part 3
In this, the third and final installation of Andres' Introduction to Groovy series, you learn about how Groovy handles variable numbers of arguments, named parameters, currying, and more about Groovy operators. Including, some new operators.
Easier Custom Components with Swing Fuse
Swing Fuse (actually just Fuse), is a framework designed to make it easier to create your own custom desktop components. In this article, Daniel Spiewak shows you how to get started and provides sample source code you can download.
Benchmark Analysis: Guice vs Spring
Willam Louth shows how he uses JXInsight Probes to investigate probable performance issues with code bases that he is not familiar with. He also highlights possible pitfalls in creating a benchmark, as well as in the analysis of results.
Five books every Java developer must own
URL: Panasonic Youth
At 9:15 PM on Feb 6, 2006, Rick Ross wrote:
Fresh Jobs for Developers Post a job opportunity
I hope this becomes an interesting list. It might give newcomers to Java a good perspective on which books to invest in. I thought it was noteworthy that Rob's list included a recommendation to get at least one non-Java book in there, too!
97 replies so far (
Post your own)
Re: Five books every Java developer must own
I think the list is excellent.The only problem is that after reading Practical Common Lisp, one might begin to realize that the modern languages, Java and C#, are not nearly as capable as the supposedly antique LISP.
The only other book I would recommend is the Art of the Meta Object Protocol. Also a LISP book but that is merely happenstance.
Happy reading.
-jh
Re: Five books every Java developer must own
you forget one'The Hitchhiker's Guide to the Galaxy' DA (not for Java 5, too)
Re: Five books every Java developer must own
Head First Design Patterns - FreemanAbout Face 2.0 - Alan Cooper
Thinking in Java - Bruce Eckel
Peopleware - Tom DeMarco
Tog on Design - Bruce Tognazzini
Re: Five books every Java developer must own
Head First Design Patterns - Elisabeth Freeman, Eric Freeman, Bert Bates, and Kathy SierraPragmatic Programmer - Andrew Hunt and David Thomas
Code Complete - Steve McConnell
Don't Make Me Think - Steve Krug
Applying UML and Patterns - Larman
Just my $0.02 worth
http://www.fuzzylizard.com
Re: Five books every Java developer must own
> The only problem is that after reading Practical> Common Lisp, one might begin to realize that the
> modern languages, Java and C#, are not nearly as
> capable as the supposedly antique LISP.
I second that .... as an APL & J programmer.
:)
My favorites
This is a list of books (that aren`t related to any specific technology) I think every enterprise-Java programmer should read.Patterns of Enterpise Application Architecture:
http://www.amazon.com/gp/product/0321127420
It gives you a good understanding how Enterprise applications can be structured.
Domain Driven Design:
http://www.amazon.com/gp/product/0321125215
It shows you how important your domain model is and how it can be structured.
Effective Java:
http://www.amazon.com/gp/product/0201310058
A single book contains a lot of very practical information every java programmer should know.
The GoF book:
http://www.amazon.com/gp/product/0201633612/
I don`t take a programmer that doesn`t know patterns serious.
Concurrent Programming in Java.
http://www.amazon.com/gp/product/0201310090
Well.. I guess most developers don`t deal with concurrency issues (apart from a db transaction) on a daily basis. But I think every programmer should understand concurrency issues.
And ofcource:
Expert One-on-One J2EE Design and Development
http://www.amazon.com/gp/product/0764543857
I felt lost in the J2EE world until I found this book.
Re: Five books every Java developer must own
> The only problem is that after reading Practical> Common Lisp, one might begin to realize that the
> modern languages, Java and C#, are not nearly as
> capable as the supposedly antique LISP.
I picked up Practical Common Lisp a few months ago and I'm so glad I did. You gain a certain perspective when learning LISP that you really cannot get from other languages.
And to me that is the whole point of learning a language such as LISP. Programmers that only have an understanding of Java will not fully appreciate the strengths and weaknesses of the language. They will also think that Java is the best solution for all problems encountered when there may be a better (faster, cheaper, etc.) ways to solve the problem at hand.
Learning to use the right tool for the job is the most vital skill any programmer can learn.
Re: Five books every Java developer must own
> modern languages, Java and C#, are not nearly as capable as the supposedly antique LISP.Hmmm, good thing the world has room for vastly differening opinions. 12 years ago I entered grad school for a masters in computer engineering. After my first and only LISP class, I quit. Yuck! Maybe it was the teacher, but I left the class hoping to never encounter Lisp again. I'm not someone who thinks that Java is the solution for every problem...but for the life of me I couldn't figure out what problem Lisp was supposed to solve.
Re: Five books every Java developer must own
Another vote for "Head First Design Patterns" - is excellent - it didn't put me to sleep like GoF.LISP
> > modern languages, Java and C#, are not nearly as> capable as the supposedly antique LISP.
>
> Hmmm, good thing the world has room for vastly
> differening opinions. 12 years ago I entered grad
> school for a masters in computer engineering. After
> my first and only LISP class, I quit. Yuck! Maybe
> it was the teacher, but I left the class hoping to
> never encounter Lisp again. I'm not someone who
> thinks that Java is the solution for every
> problem...but for the life of me I couldn't figure
> out what problem Lisp was supposed to solve.
I had several undergrad and grad courses in LISP long ago. I tend to think that there's a bit of a "mirage" thing going on here. People tend to think if LISP as being so powerful because it appears at first that it would be less powerful. You occasionally hit a problem that has such an elegant solution in LISP (being able to *see* that solution yourself is another matter), that you tend to start thinking "LISP can do anything".
Re: Five books every Java developer must own
> Another vote for "Head First Design Patterns" - is> excellent - it didn't put me to sleep like GoF.
"Design Patterns" is good for:
a) Supplying names for the common sense stuff you already do.
b) Looking good on your bookshelf.
c) Required reading for any interview
d) A required entry on any "must have" programming book list
e) All of the above
Re: Five books every Java developer must own
Yep, I debated putting the Head First book on there instead of the GoF book. I went with the GoF book as "essential" before the HF only because it is the classic that kick started the patterns movement and is referred to everywhere. I own the HF book and love it, and would be quick to tell anyone struggling with the GoF book to get it to help their comprehension.www.ajaxian.com
Re: Five books every Java developer must own
I've picked up _Code Complete_ multiple times at the book store and been very close to buying it. McConnel sounds like a smart, pragmatic guy, from his interview on IT Conversations. I'll have to get it on my next amazon run.Agree 100% on _Dont Make Me Think_ - I would have this on a top five for anyone doing web design or usability.
www.ajaxian.com
Re: Five books every Java developer must own
> Another vote for "Head First Design Patterns" - is> excellent - it didn't put me to sleep like GoF.
I agree...GoF is a very important book, but Head First Design Patterns is funny while being very informative. A lot great examples and a good balance of design patterns and fundemental OO design.