Software dev, tech, mind hacks and the occasional personal bit

Category: Book Reviews

“Norwegian Wood” by Haruki Murakami

Norwegian Wood is an excellent novel. I finished reading it at lunch today, and haven’t stopped thinking about it since. The novel is really subtle, and at the start, I wasn’t immediately interested. However, once I got into it, I couldn’t put it down. Toru, the narrator is so well developed in the novel that he seems almost like somebody I have met in real life. If you haven’t read it, don’t hesitate – start reading it right away! And don’t read any more of this post.

If you have read it, what do you think of the ending? I’ve read people suggesting that Toru committed suicide or similar, but I don’t believe that that is the case. For one thing, he’s got to live to 37 and catch a plane, as described at the start of the novel. I think the “dead centre” reference is due to Toru being dead centre of the “countless shapes of people walking by to nowhere”, rather than having died. I think the ending is happy. Or maybe I just want it to be. Here’s my interpretation. Toru is lost in the middle of nowhere. His old life was based around Naoko and Kizuki (plus Reiko as a link to them). They have all died or left. He is in the middle of nowhere. But Midori can rescue him from this. She is his anchor to reality and a new life. She will give his life direction and meaning – that’s why he calls out to her again. If anyone in the novel is a symbol of life, it is Midori, and by calling out to her, I can only understand that Toru has chosen to keep living and to pursue happiness. Midori’s silence is “the silence of all the misty rain in the world falling on all the new-mown lawns of the world”. That’s a positive image for me at least, pregnant with possibility.

If only I could read Japanese, perhaps I would understand better.

PS – Many thanks to my friend Jim for lending this most excellent book to me.

Book Review: UML Distilled

UML Distilled: A brief guide to the standard object modelling language
(3rd Edition)
by Martin Fowler

UML Distilled is good. It is written carefully and concisely and has been heavily revised to cover UML 2. It is a opinionated book – it presents Martin Fowler’s view of UML. This is a good thing. Fowler concentrates on the parts of UML that he has found widely used in the industry, and the most useful in his own work. Fowler is not bound by the UML specification, he also describes “non-normative” diagrams (ie, variations on UML which are not standard but widely used). Fowler often provides his own view on a particular diagram or component. For example, I’ve often wondered when to use aggregation rather than association in a class diagram. Fowler cleared this up for me:

“Aggregation is strictly meaningless; as a result, I recommend that you ignore it in your own diagrams. If you see it in other people’s diagrams, you’ll need to dig deeper to find out what they mean by it. Different authors and teams use it for very different purposes.”

UML Distilled starts with an introduction about UML’s history and aims, and then a rapid look at different development methodologies and where to fit UML into them.

The core of the book covers the following diagrams/specs:

Class Diagrams
Sequence Diagrams
Object Diagrams
Package Diagrams
Deployment Diagrams
Use Cases
State Machine Diagrams
Activity Diagrams
Communication Diagrams
Composite Structures
Component Diagrams
Collaborations
Interaction Overview Diagrams
Timing Diagrams

Class diagrams and sequence diagrams are covered in detail, the other diagrams more briefly. The book is quite short, but gives enough information on each topic to allow you to understand and draw the diagrams. At the end of each chapter, there is a helpful “where to find out more” section and a “when to use this type of diagram” section.

There is also an appendix at the end of the book on changes between various versions of UML.

The book is surprisingly easy to read. Fowler’s style is clear and friendly and examples are well chosen.

My only complaint is that perhaps the book could have been a little longer to allow a bit more detail on some of the diagram types. I would have liked to have read a little bit more on object diagrams in particular.

I’d recommend the book to anyone who wants a rapid and concise introduction to or revision of UML 2.

Rating: 9/10

Book Review: My Job Went to India, 52 Ways to Save Your Job

Full Title: My Job Went to India (And All I Got Was This Lousy Book), 52 Ways to Save your Job

Author: Chad Fowler of the Pragmatic Programmers

185 pages, Paperback

An interesting book written by Chad Fowler, who spent 1.5 years in India hiring and managing an outsourced team of developers. The book’s main focus is on how you can make yourself as, a developer, more valuable to your company / community so that your job is not outsourced. There are quite a lot of valuable and interesting ideas in the book for professional development, and “getting your name out there”. The book also gives the reader some idea of what development is like in India, some tips and the pluses and minuses of outsourcing.

The style of the book is conversational, and easy to read. I finished it in 2 days. I’d recommend it to developers wondering about outsourcing and looking for some tips on professional development.

Rating: 8/10

Page 4 of 4

Powered by WordPress & Theme by Anders Norén