Thursday, January 22, 2015

January Read

Title: Silkworm
Author: Galbraith, Robert (J.K. Rowling)
Call Number: F/Mystery
Book Description (from amazon.com):
            When novelist Owen Quine goes missing, his wife calls in private detective Cormoran Strike. At first, Mrs. Quine just thinks her husband has gone off by himself for a few days-as he has done before-and she wants Strike to find him and bring him home.
But as Strike investigates, it becomes clear that there is more to Quine's disappearance than his wife realizes. The novelist has just completed a manuscript featuring poisonous pen-portraits of almost everyone he knows. If the novel were to be published, it would ruin lives-meaning that there are a lot of people who might want him silenced. 
When Quine is found brutally murdered under bizarre circumstances, it becomes a race against time to understand the motivation of a ruthless killer, a killer unlike any Strike has encountered before... A compulsively readable crime novel with twists at every turn, THE SILKWORM is the second in the highly acclaimed series featuring Cormoran Strike and his determined young assistant, Robin Ellacott.
My Read:
            This is the second book of the Cormoran Strike series by Robert Galbraith, aka, J.K. Rowling. After reading the chapter one and the very last chapter I got a weird feeling that I was reading something combined with characters of Inspector Columbo and Perry Mason. It’s a strong connection I made from just reading the two chapters plus the first book. Why Columbo? It’s the way the suspects presented in the book: the sequences of interviews and interactions between the questionable personnel and the shrewd private detective. Why Perry Mason? It’s the untold and intangible relationship between the private detective and his sidekick assistant. To me, the most beautiful element between two beings is usually the silent and covert flow. This quiet element is buried in the words. I can’t wait to have another taste of the Cormoran Strike’s masterpiece at work.



No comments:

Post a Comment