The book club
has been going now for a couple of weeks and I've been enjoying it. We're going through Ben and Martijn's "The Well Grounded Java Developer."
We've already covered Java 7s new features, the new I/O, dependency injection and concurrency. We still have bytecode, performance tuning, Scala, Groovy, Dependency Injection and more to look forward to.
Reading is a vital skill for any developer. Jerry Weinberg observed this before I was even born:
"Programming is, among other things, a kind of writing. One way to learn writing is to write, but in all other forms of writing, one also reads. We read examples - both good and bad - to facilitate learning."
When authors produce a good book they go through a painful process of distilling their hard-earned experience and placing it on the page. It's there for the taking. All you have to do is read it.
Yet finding time to read isn't so easy. There are so many other demands on our time. Technical texts are the last thing you want to read on the train home after a hard days work.
That's where the book club is so valuable. We all commit to a schedule and follow it, sharing our thoughts along the way. It gives us the motivation we need to keep going.
If you're still learning you have the opportunity to read along with experienced developers. They will be happy to help with anything you find difficult to understand.
The more people joining
in, the more useful it becomes.