+972 52-548-6969
Not a book review: Applying Domain-Driven Design and Patterns
I got Applying Domain-Driven Design and Patterns two days ago, and I have been trying to read it ever since. If you followed my adventures with reading about databinding, you know that I can usually devour a book in a day or so.
At the moment, I am on page 30, and I am incredibly frustrated. The issue is with this book. I only need to touch it to feel this sudden craving ("Must Code. Must Code. Must Code!") to reach the computer and start working. I am reading about two pages and then I have to code.
The last time I had this feeling I was reading Working Effectively with Legacy Code and I wrote Rhino Mocks to shooth the ache to code. This is really scary, so far the only things he talks about are TDD and Refactoring, which are well known to me. But I can't keep the book in my hands too long.
Update: I am now somewhere in chapter two, and the issue is Domain Patterns. This time I had almost twenty minutes of reading time before I had to code something. I am now thinking about the reverse term to page turner to apply to the book, any suggestions?
Just to clarify: So far, I really like the book. I hold Jimmy personaly responsible for a major refactoring effort (which I just blogged about), which has made some very visible marks on the codebase I am currently working on. Very positive ones, I should add.
Here I was, peacefully reading about design patterns, eagerly waiting for the real meat to arrive, and suddenly I hit my head and exclaim: "I violated the Single Responsability Principal, that is what it is so hard to test!" It is rare that I get so excited about something that I has to put it down. But Applying DDD is one of those books. It is not a page turner, it is a code pusher. I read two pages I just have to apply those ideas immediately.
Like I said, I'm only in the beginning of the book, so it is not a review (I'm planning on posting that the moment I finish the book), but I already like what I read.
Comments
Comment preview