Collecting the best books mentioned on hacker news, reddit and other places
In the talk "Clojure Concurrency" , Rich Hickey demands that everyone in the room read "Java Concurrency in Practice" . "It will scare the crap out of you."
Wow, that's actually kinda tough to answer. There's been a LOT of changes in the Java world in the last 10 years - as you might guess. And I mean both in terms of the language itself, and the tooling and ecosystem as far as libraries and frameworks, etc.
The answer also depends a bit on what exactly you want to do. If you're mainly interested in web apps, it's one thing, "big data" is another world altogether, mobile (Android) has its own ecosystem, etc.
All of that said, here are some thoughts:
Generics and the newer Collections related stuff is one area that changed a lot. There's online documentation at:
and a decent, if somewhat older, book is http://shop.oreilly.com/product/9780596527754.do
Then there's the newer concurrency stuff that came along in the Java 5 / Java 6 era. Fork/Join, Executors, etc. Java Concurrency In Practice should still be useful to you, even though it is, again, a little bit dated now.
To get started with the Java 8 stuff, a book like "Java 8 in Action" would be good.
Another good intro the Java 8 era stuff is
And to make it even harder, Java 9 just dropped, so there's even more new stuff. I just picked up this book myself, but haven't had a lot of time to dig into it yet.
For frameworks, Spring and Hibernate are both still popular and it wouldn't hurt to brush up on both of those. Spring Boot in particular has caught on for a lot of Java developers.
Also, Tomcat is still very popular for hosting java Web applications and services of various sorts. JBoss / Wildfly is still around, but JEE (as J2EE is now known) is not as popular as in the past (even though it has actually improved a LOT).
Play and Dropwizard are two more frameworks you might want to familiarize yourself with
In terms of tools, Eclipse is still popular, IntelliJ is probably the most popular Java IDE these days, and Netbeans seems to have faded from view a bit. Ant has fallen out of favour for builds, with most devs now using either Maven or Gradle. Read up on / play around with both of those and you'll be in good shape there.
Also, Java shops have also been affected by the overall move to "The Cloud" and you can't really ignore that either. If you haven't already, you'll probably want to familiarize yourself with AWS and the AWS SDK.
If you want to work/play in the "big data" space, you'll need some combination of Hadoop, Kafka, Spark, Hive, Storm, Flume, HBase, Impala, etc., etc., etc.
You could probably read this decade old book:
and it'd be a good start. It's in "boring" old Java, but it goes over a lot of the meat and potatoes concepts.
I have probebly not done much Java Concurrency. Sure you can simulate CSP with Blocking Queues but since you bind real threads you will run into tons of problems.
Why dont we ask Brian Goetz a Java Language Architect how "easy" it is, read his book  and then lets talk again how easy it is.
I think this list is missing some important parts of computer science.
Here are the books that our university uses for first-year students combined with books that I found to be useful:
Introduction to Programming (using Eiffel) 
Mathematics for Computer Science (or: Discrete Mathematics) 
Introduction to Datastructures and Algorithms 
Introduction to Digital Design 
Parallel Programming (using Java) 
Optional but highly recommended, you'll probably find it completely out of scope:
Real Analysis I 
Real Analysis II 
Introduction to Linear Algebra 
Introduction to Physics 
I found Java Concurrency in Practice to be a pretty solid read.
#1. "Java Concurrency in Practice" http://www.amazon.com/Java-Concurrency-Practice-Brian-Goetz/...
#2. ... hmm, that might be it.
I'm shocked that Java Concurrency in Practice isn't in the list:
I only know about that book because of Rich's mentions of it.
To be honest, I"m also a little surprised that the Pickaxe book is in the list. Not that Ruby isn't the bees knees; it just didn't strike me as being influential on Clojure.