Title: The Memory Keeper’s Daughter
Author: Kim Edwards
This is a 400 page book and fairly long for my reading standards. So I had my doubts about completing it right when I started reading the book. But I survived and hence this review!
The story extends over a 25-year period starting in the mid-sixties. Pregnant wife has twins. The second child is born is born with down syndrome. Husband is the Doc who delivers the baby. He gives the baby away because of his traumatic experience with his own sister, who also had the down syndrome. He tells his wife that the baby died. The wife never gets to see the supposedly dead baby! This is a weak point in the story. One could argue that the rest makes no sense because of this or just let it be and give the rest of the book a chance. I chose the later and found it to be more than worth my while.
A very touching story. The author does a phenomenal job of capturing the story from the perspective of different characters involved. In other words, its not a story told from one character’s perspective. The Doc who lives with the secret, the wife who lives through the pain of losing her child, the woman who brings up the child, each of these characters are explored in great depth and story told at various stages from the perspective of each of these characters.
The writing does tend to get overly descriptive. In the early part of the book I found this to be a bit of a drag but as I progressed through the story, I actually enjoyed the detailed descriptions particularly the parts where the story is very moving and emotional. If the author had been more focused on just the story and gone a little easy on the somewhat excruciating descriptive details the story could well have been told in half the number of pages. Nevertheless, I enjoyed the book.
If you are the emotional type, this is a must read. If you are the impatient “cut the crap, tell me the story, damn it” type, then this one is definitely not for you. This book is a bestseller, btw.
The Aussies thrashed India, not surprisingly. For the first time in a long time, I checked the score only a couple of times while the match was in progress. I never thought India stood a chance. The Aussies in their current form are simply too good for the Indians. The India team on the other hand has way too many problems and simply does not have the skill or the depth to really challenge the Aussies. Oh well…
Upgraded to the new Firefox 2.0. My bookmarks vanished. Then I uninstalled and re-installed it and magically the bookmarks re-appeared.
Didn’t find any dramatic changes in the new version. Good news is that it hasn’t crashed so far. I noticed that when you have multiple tabbed pages open it doesn’t prompt the you when you “kill” the browser window. I thought it previously used to prompt before exiting?
The user experience is far superior to IE 7.0 in my opinion.
After restricting SA, Pak crashed to defeat on a lively pitch. Younis Khan played a pretty iressponsible shot. None of the others appeared to threaten either. Pak is out of the series after all the off the field action (which is bound to start again!). I thought Boucher deserved the MoM award. His batting was crucial and he took a brilliant catch behind the stumps. Had he failed with the bat I doubt SA would have had a decent score to defend.
A side note on Younis Khan — his English is pretty bad! Inzy seems like an authority on English compared to this guy. How does he communicate with Woolmer??
Its great to see pitches that help bowlers. This ICC championship has been a low scoring affair with bowlers dominating for the most part. Wonder what’s in store for India against a 5-pronged Aussie pace attack!
India put up an insufficient score and was severely handicapped by two of its main bowlers (RP, Pathan) failing miserably.
- Firstly, its a shame that India went into this tournament without Sreesanth. The sooner Pathan is replaced the better. His bowling is an embarrassment. Defending a small total, India’s opening bowler starts off with 20+ runs in the first two overs! His batting is unlikely to survive the Aussie attack and his bowling has been consistently unpredictable. Its best to drop him for the next match at a minimum.
- The other selection mystery is the preference for Raina ahead of Kaif or Mongia.
- As for Viru, the man badly deserves to be dropped. It’s hard to understand why the likes of Shastri continue to praise him to the skies. His success in ODI ever since the last world cup has been dismal. When the likes of Hayden can be dropped its hard to understand why the Indian selectors persist with Viru for so long.
- The other descision that backfired was the one to drop Powar. He has been in good form and has a decent record in ODIs lately. The wet ball theory for dropping him was a huge mis-calculation. With a small total to defend, his wicket taking abilities could have made a huge difference.
Given the strength of the Aussie team, India chances are probably over with this defeat to the WI. In any case, there appear to be way too many issues with the team starting with the selection. If the Indian think tank wakes up and smells the coffee, they should bring in Powar, Mongia and Kaif in place of RP, Pathan, and Raina. Unfortunately, there is no Uthappa or Gambhir in the 14 to replace Viru.
I am surprised as to why Watson is being asked to open the Aussie batting. Mike Hussey has proven to be a great ODI bat and is clearly wasted down the order. Watson hasn’t really clicked as the opener. Moreover, Watson has been opening the bowling. Isn’t that an overkill?
For all those predicting Silicon Valley’s demise while its clones in India and China rise, here is an interesting article from the NYT. There is no question that the bulk of the new Web 2.0 action is happening in the Silicon Valley among other cutting edge technologies.