Friday, November 21, 2008 9:49:45 PM
I read books when I commute. I have about 30 minutes of reading time, each way on the train to work, though sometimes I'm too tired to read. I'm also not a terribly fast reader, so about one to one-and-a-half months to read a book seems to be the pace I can go.
However, when it takes that long to get through a book, it is pretty likely that you will discover another book that you want to read. This way, I seem to have accumulated a backlog over the past six months, so now I'm noting them in this to-read list, starting with finishing the book I'm currently reading:
I'm about three quaters into this one. It's a book about building software that is production ready; ready to gracefully handle peak loads, ready to be debugged when the shit hits the fan, and just plain ready to be used. The author presents patterns and anti-patterns that will help make or break your systems in production, and he backs them up with anecdotes and real experiences. It's a technical book primarily targeted at developers of software normaly categorised as "enterprise," but anyone technically involved in the life of such software would stand to learn something from reading it.
Java Management Extensions
Because Release It! put so much emphasis on being able to monitor the health of your applications, and being able to do something when stuff goes avry, I thought JMX would be a really good technology to use for this sort of thing.
I'm not totally sure why I bought this book or what I'll learn from it, but I'm always interested in improving the basic skills of programming. Maybe I already know most of what it teaches, but then I might be able to go through it with quickended pace, and it's also nice to be reminded of the good habits every once in a while.
Real World Haskell
I am somehow drawn to Haskell as a language. The language presents a very different view on programming than what I am used to, and I think it has many strange and foreign concepts to teach me. I think Real World Haskell is that down-to-earth, lay-mans terms introductory text on Haskell I have been waiting for. I don't cope well with content that is too academic, and I think this book is on a level and pace that I can follow.
When I'm done thinking high and pure thoughts in Haskell, I'll be needing a language that I can use at work, and I think that Cloure is going to be that language. If you have been following the Clojure googlegroup like I have, you'll know that Rich Hickey, the guy who designed and implemented Clojure, is wicket smart and that Clojure is going to be pretty successful as a JVM language.