Skip to main content

Tamar by Mal Peet

This one's been sitting on my TBR shelf for awhile now, waiting for me to work my way around to the right mood. When I finally did, I was sucked in by the first line.
In the end, it was her grandfather, William Hyde, who gave the unborn child her name. He was serious about names; he'd had several himself.
One day, out of the blue, William Hyde asks his son to name his daughter Tamar. He explains that when he was a Dutch resistance fighter working for the British during WWII, their code names were taken from rivers in England. His son assumes it was his father's code name and agrees to name her Tamar.

After this brief introduction, the story jumps back in time to follow two young Dutch secret agents, code names Dart and Tamar. The two friends parachute into the occupied Netherlands in the dead of night. Tamar is charged with organizing the fragmented resistance efforts. Dart is his wireless operator. When they arrive, Tamar finds he is based out of the farm where a young woman named Marijke lives. It turns out the two met and fell in love a year ago but never thought they'd see each other again after Tamar was sent back to England. As they rekindle their romance amid the terror and starvation gripping the country, Dart is not so lucky. Based out of an insane asylum, he poses as a doctor, making trip after treacherous trip into town to relay encrypted messages and receive directions from headquarters in England. The events that overtake these two friends combine to create a web of deception and anger that reaches out to cover three generations.

This story is bleak. The focus is on the horrors of war and what they do to the men and women involved, the indelible mark left on their lives long after the guns are silenced and the violence is over. In the WWII chapters, the writing is coolly objective. It is impossible not to sympathize with Dart and Tamar and Marijke, though it is difficult to really feel like you know them. The war obscures everything. However, their story is broken up periodically by excerpts from the future. A future in which William Hyde dies suddenly, leaving a box of strange items to his granddaughter Tamar. Tamar's father disappeared years ago, her grandmother is in a home for the elderly, and her mother knows next to nothing about the family history. With the help of her quirky "cousin" (but not really) Yoyo, Tamar sets out on a journey to the river that shares her name to discover why and what her grandfather left her. These chapters are told in first person and come across a bit warmer than the rest of the tale. They show up more frequently as the novel comes closer to its conclusion and, I admit, I would have liked a few more of these present-day chapters throughout the book. Nevertheless, it is a harrowing and fascinating read. I wanted to understand the characters and their motives. I wanted Tamar to understand. In the end, Mal Peet leaves it up to the reader to determine which of them deserves forgiveness and which of them achieve peace.

Links
Bookgoddess Review
The Guardian Review
New York Times Review

Comments

You Might Also Like

Interview with April Lindner + Jane Giveaway!

I'm very excited about today's interviewee. As you know, I had been looking forward to the publication of Jane for months when a review copy happened in my lap and I let out a gasp of joy. Being a modernized retelling of Jane Eyre with a rock star-ized Mr. Rochester named Nico and a cover that hits every last one of my aesthetic buttons, it was sort of made to order for this reader. Needless to say, it more than lived up to my not inconsiderable expectations and I have been recommending it on a pretty much daily basis to family, friends, co-workers, neighbors . . . you get the picture. It's now just under a month until the book is out and, in anticipation of the release, I invited  April Lindner over to dish about all things Jane. She kindly accepted. Please welcome April! First things first: The Cover. I am in deep smit with that cover. Did you have any input and what was your reaction upon seeing it for the first time? I adore the cover too, and was blown away the...

Ballad Giveaway!

I think it's time for a giveaway, don't you? Thanks to the generous people at Flux , I have one copy of Ballad by Maggie Stiefvater to give away to one lucky commenter! I'm very excited about this giveaway because I thought it was such a great read and an excellent companion novel to Lament . You can find my review of both books here and here , as well as an interview I did with Maggie last month. I've posted Maggie's awesome book trailer here before, but here it is again because it's totally worth a second viewing. Maggie has since put together a playlist for Ballad , which you can also check out here . The rules for the contest are simple. To enter please leave a comment telling me your favorite ballad or love song. One extra entry if you become a follower, two for current followers. Make sure to leave me a way to contact you. The giveaway is open to U.S. and Canada residents only and closes on October 1st-- Ballad ' s official release date!

Terms of Endearment

Have you ever been reading a book, moving along quite nicely, and then-- bam --a character whips out a particular term of endearment that just yanks you right out of the story? It happened to me recently, and I'm sad to say I couldn't recover. I did try. But she just kept using that term and I . . . I had to get the hell out of Dodge. Buh-bye, story. Don't let the door hit you on the way out. I'm not saying this is the norm (thank goodness). I can put up with a certain amount of treacly back and forth when it comes to the exchange of terms of endearment, especially if they fit the characters, their background, culture, the tenor of their relationship, etc. And the history of these terms  at home and from around the world is often fascinating (at times hilarious). But there comes a point where I can't see past the cheese and/or weird anymore and I do not want to be with these people any longer . Shallow? Perhaps. But it's a very individual thing, isn't it?...