Recommended additions to bookshelf

[Nik]

After doing for a while I turned back to reading how it *should* be done
. Recently I have read (or re-read)

Evans: Domain-Driven Design
Richardson: POJOs in Action
McConnel: Code Complete, 2nd ed.
GoF: Design Patterns: *snip*
Alur: Core J2EE patterns

Any recommended additions to that list? Any good Agile/Test-driven Development books you can recommend?

[karldmoore]

A friend recently recommended "Java Persistence with Hibernate" and "JUnit Recipes". I don't have either so I'm interested in having a read.

[tatvamasi]

I would add couple more if I may

Pragmatic programmer
Refactoring

[karldmoore]

How could I forget Refactoring! Effective Java is another general one. Could we get away without mentioning J2EE Design and Development and J2EE without EJB .

[Lyserg]

Analysis Pattern
Refactoring to Patterns

[JimmyK]

Agile Software Development, Principles, Patterns, and Practices (Prentice Hall - Robert C. Martin)
Groovy in Action (Manning)
The definitive guide to Grails (Apress)
Practices of an Agile Developer (Pragmatic Bookshelf)

I'm also looking forward to 'The definitive Antlr reference' for building DSL's. Another book that's recommended on Amazon when you're interested in compiler/interpreter/DSL design: 'Programming Language Processors in Java: Compilers and Interpreters'. I haven't read it yet but it seems highly recommended. I think DSL's will become more important in the future.

[JimmyK]

I think multi-threading might become more and important, especially with the arrival of muti-core processors. So if you want a nice and very readable introduction to the topic I can recommend the following book:
Java Concurrency in Practice (Goetz)

BTW: I read the first 150 pages of the 'Programming Language Processors in Java' book I mentioned before and I must say: it's a 'superb' book on Compiler/Interpreter design if you need some introductory material to a complex topic like this!!

[Nik]

Thanks for the tips, I started with the Martin: Agile Software Development and will probably go Fowler: Refactoring after that.

Of course, I can't get everything I read to stick in my brain before implementing some of it but hopefully I will get some more insight in topics that I can look up later when I run into them and remember reading about them...

I think I will leave CFGs and push-down automatas for someone else, I had enough of them in CS-classes :-)

[karldmoore]

Thanks for the tips, I started with the Martin: Agile Software Development and will probably go Fowler: Refactoring after that.

Can't comment on the first, but Refactoring is a great book. Lots of people already follow practices in there already but I found it really useful. I wish people would stop hacking code and calling it refactoring however . It's a cowboy way of pretending to do something properly, "yeah I'm just refactoring some code" vs "I'm hacking away completely blind because I haven't got a clue what I'm doing".

Of course, I can't get everything I read to stick in my brain before implementing some of it but hopefully I will get some more insight in topics that I can look up later when I run into them and remember reading about them...

I think I will leave CFGs and push-down automatas for someone else, I had enough of them in CS-classes :-)

That's the biggest problem I have, lots of things go in but I'm sure something else gets wiped out .

[tatvamasi]

Before picking up any of these books about technical details of software, I would recommend you go through pragmatic programmer and start following it like mantra, after that every book you read would make way way way too much sense.