Ordinary Grace

Review of Ordinary Grace by William Kent Krueger
A huge best seller, with a first person child as the narrator, about a summer of sex, murder and coming of age. The parallels to ‘To Kill a Mockingbird’ are hard to miss.
Why do so many writers avoid first person? It becomes obvious too soon in this book. The main character, Frankie, cannot possibly know, be present or be privy to all of the events and conversations that happen. So a method of eavesdropping is conjured up. Frankie can listen to his parents talk through the vent from the kitchen to his bedroom, or he can listen to conversations in his fathers church office from the basement furnace vents that are disconnected.
When the next door neighbors, the Sweeny’s, talk to Frank’s father Nathan about sexual problems in their marriage, I wondered what was the point of this to the story? But it only set the stage for another eavesdropping that had tragic consequences.
Now, spoiler alert. I am going to give away the plot here.
I have two problems with this book. It is incredibly well written and the hooks to the story pulled me along as the author intended. Right from the start when there is some question as to how Bobby Cole died, we learn there are things beneath the surface here.
But my first issue is there were too many things I didn’t believe. When men try to commit suicide, they are almost always successful. Women, not so much. But Emil Brandt tried to commit suicide twice and failed. The police knew that Ariel Drum disappeared near the river but didn’t look for her body. Only Frankie happened to find it. Hard to believe. Emil had sex with Ariel, but only once? Lise was happy in the Mental Hospital? Karl confessed to Nathan he was gay? Doyle blew up a frog with a firecracker? That is something a mean kid would do. Morris happened to die. And Frankie’s infatuation with Edna Sweeney’s underwear or seeing Lise naked. I am not sure what they had to do with the story. I think every writer can assume that readers will suspend disbelief as they read a good book. And it is a good book. But I was jarred out of the story too often by things that didn’t quite ring true.

My second problem with the book is more thematic. I read this book as a book club selection expecting it was more mainstream fiction than the Crime / Who dunnit it is. I had no experience reading Krueger before but the book doesn’t start as I thought a crime book would. I was mistaken. So I had higher expectations. I expected characters I could feel for and that the main character or characters would grow and learn through the novel. There is not much of that. It is a fatalistic book. Nobody really acts, they are mostly acted upon. I want lead characters to engage, drive the action, and learn & grow through the novel. I didn’t get that.

Now there are lots of good things in the book. The look at a less than perfect marriage; Ruth is disappointed to be sure. The damage done to men in war; Most of the male characters had been in WWI, WWII or Korea and had all come out changed in some way. I wondered why there was no mention of the Vietnam war, which was just ramping up at that time. The concern that Frank or Jake might be drafted into that conflict as they come of age is not raised. Early understanding of Autistic people and our horrible treatment of Gay people in the early 60’s is noteworthy.

All in all , a good read, by an author who is trying to make the jump from Crime fiction to mainstream.


Danny Aldham

July 8, 2015

Perfect vs Process

Perfect vs Process

There is pressure to make sure everything we deliver is great. Polished, professional, reflecting the near perfect brand our businesses want presented into the market place. So as I work a certain project document through a second or third draft, I am torn whether or when I should share it; With the team, With my peers, With the customer.

I have worked in the Free and Open Source Software community where the mantra is ‘Release early and often.’ It creates a tight feedback loop and involves users and developers closely working together. I like the results and so am tempted to use the same strategy in development of business related projects.

But ‘the Business’ does not like to have anything coming out that is less than perfect. To put a proposal out that is half-baked at best is a quick way to sideline your career. But if that same proposal has not had feedback from the team that must implement it or from the end customer, it risks missing the mark. And I have seen far too many proposals miss the mark, by a country mile.

What is the happy medium here? When can we safely move away from Marketing material and dive into Solution development? When is the right time to set aside our ‘We know best’ attitude and begin real collaboration to develop real solutions?

It is hard. Usually we are being paid as professionals. At a professional rate. And we are expected to be the Experts. That is why we are here. How does a professional open up their process to allow teams and customers to influence the outcome?

The Project Management community has a concept called ‘Progressive Elaboration’ where the team continually work on details for tasks, deliverables and time-lines. The plan gets more elaborate as we go. But it means admitting up front we do not have all the answers. And to some cultures that is like fingernails on a chalk board.

I am sold on the iterative process of sharing documents and ideas as soon as possible. I have seen good results, so I will continue to do so. But I understand the wariness to the approach. I am certain some things need to be developed behind the scenes. They say if you ever see sausages being made you will never eat them again.

Danny Aldham


“The Cathedral and the Bazaar” . Eric Raymond

Rolling wave planning and Agile software development https://en.wikipedia.org/wiki/Rolling_Wave_planning