As I finish reading one book and look through the thousands of books in the house to choose the next one(s) to read, of late I’ve been looking for books I not only want to read but that I can discard (through sale, donation, or trashing) when I’m done. A couple of months ago I found one of those in Agatha Christie’s And Then There Were None. I wouldn’t have known where this book came from or how I obtained it had I not found in it a Christmas gift tag with my handwriting. I gave it to my sister some years ago, probably when we were teenagers. This particular printing was November 1964. It is a student copy, which suggests I bought it during my sister’s high school years.

I admit to this being my first Christie book to read. I’ve see a number of movies made from her books, but had until this never picked one up to read. That is now rectified, and the enjoyment I found from this volume guarantees I will read more of her writing.

Originally published in Christie’s native Great Britain in 1939 with a different title, a very vile title (that I won’t enter here) by today’s standards, it has sometimes been published in the USA with the title Ten Little Indians. Like Christie’s main writing, it’s a murder mystery. In this case, however, you don’t know if the murders are really murders, until the denouement.

Ten people are lured to an island off the southern coast of England named Indian Island. Ownership of the island is in question and the ten, as they are making their way there, have lots of questions about who owns it now. They are invited by a person they don’t know: U.N. Owen. Seven men and three women arrive on the island within a day or two of each other. Eight are guests, two are servants. All expect their host, Owen, to arrive soon. As they head towards the island, we get some backstory on several of them. For others, backstory comes out as the novel progresses.

In each guestroom is a poem, framed and hanging on the wall, titled “Ten Little Indians”. It’s a childhood diddy at least some of the guests recognize. On the table in the dining room are ten Indian figurines. The ten people meet for their first evening meal. After it the butler, following written instructions from Owen, who he’s never meant, puts on a phonograph record. It turns out to be a surprise, someone speaking (not music), who indicts each of the ten with a death they have caused in the past, saying that they would have to pay for it.

How each character pays for it comes out chapter by chapter. The first happens that night, as one of the guests dies of poisoning. Murder? Or suicide? The remaining nine speculate. An elderly judge who is a guest takes charge and “holds court,” trying to work the problem logically and find out what evidence they have. The guests all become suspicious of each other. Meanwhile, one of the Indian figurines disappears.

By the time Christie wrote this, standards for detective novels had changed in, say, the forty years since Doyle had given us Sherlock Holmes. Then, the means of solving the case wasn’t given in the writing. Since then, by Christie’s time it was expected. So in the novel should be the means for the reader to solve it, if you read closely.

I was close. As the ten, one by one, meet their untimely end, I came to the conclusion that one of the dead wasn’t dead but was really alive, but was only thought to be dead by the other guests/servants. I had a candidate, but it turned out I was wrong. I suspect, however, that if I read it over again, slowly, I would see that the right clues were there from the start. That’s probably impossible to do, given that I’ve read the Epilogue that explained it all. Re-reading it would be an interesting exercise.

I never will do it, though. The story and plot were good, the writing was good, it was an easy read, and I highly recommend it. But I have too many books in the house, too many I want to read, and thus have to be very picky about the ones I will re-read. No, this one will go to the get-rid-of pile as soon as I post this. Very glad I read it—actually I should say “we” read it, as my wife and I read it aloud together, the 183 pages plus some of the 32 page reader’s supplement in ten sittings—but it’s goodbye, ten little Indians. I hope another reader someday acquires you and derives the same pleasure from you that I did.

I know many of you have long ago read Pride and Prejudice by Jane Austen. Our son said he read it every year for a number of years. Well, both my wife and I had somehow not read it.

In early May the movie came on TV and we watched it. This was the 2005 version with Keira Knightly, Matthew Macfadyen, and Donald Sutherland. We found the story difficult to follow. Part of this was the English accents; part the overlapping talking by multiple characters in rapid-fire succession; part the sometimes low volume of the voices, such as when the Bennet girls were talking at balls. So, after watching the movie, we decided to read the book aloud in the evenings. We read from an older copy that has been in my family many years. Charles Westcott (“Uncle” Charlie), a good friend of my great-grand uncle David Sexton, gave it to my mother in 1934, according to the inscription. I don’t know if it originally had a dust jacket, but it doesn’t have one now.

I’m glad we read it.  Reading aloud is slower than reading silently. It took us twenty sittings over a month and a half to complete it. While the language is somewhat archaic, it is a classic that everyone should read. It has become a cultural icon. While I had heard of the title for years without thinking much about it, my attention was first drawn to it by the mentions in the movie You’ve Got Mail. Of course, I didn’t really understand what the Hanks and Ryan characters said about it. Next time I see that movie, I should understand it better.

I don’t think there’s much point in my digging deeply into this classic, analyze the writing, or critique the plot and character development. Pride and Prejudice is much loved by millions. It has stood the test of time, and will be read and loved for at least another century. I hope to read it again sometime in the future. And to see the movie again. We watched it a second time right after reading the book. We were able to follow the plot, but I would really like to understand more of the dialog. Darn those British accents. Darn those silly little girls who all talk at once in hushed giggles. I fear I’ll never be able to understand it all.

This particular book is a keeper. It’s not exactly a collectable, as it’s a little too new, and it looks to have been somewhat of a mass-market hardback. But, it’s in excellent condition. To misquote Harry Potter, the binding is not fragile. It goes back on the shelf, this time next to Sense and Sensibility for easier future findability. I need to re-read that one some day.

Having finished reading another book aloud (which I haven’t reviewed yet, but will), I suggested to Lynda that we next read Bible Code II. I did this because we had read Bible Code 1 years ago, the sequel was sitting next to it, and I thought we could read the second and put both out for sale or donation. She agreed, and we read it.

The author, Michael Drosnin, has taken the computer work of Israeli mathematician Dr. Eliyahu Rips and written popular books about a hidden code in the Hebrew version of the Bible. The first book dealt with codes in the Torah, the first five books of the Old Testament, also called the books of Moses. The second book extends into the entire Old Testament. In the first book, Drosnin explained that the Hebrew text of the Torah as settled. No one disputed the exact arrangement of letters and words. However, as he explained in BC:2, that isn’t the case with the rest of the Old Testament. Some Hebrew text is disputed.

How does the code in the Bible work? You skip letters on a fixed pattern and see what results. Skip every other letter. Do the letters then brought together form a word? No? Skip two consecutive letters, putting every third letter together instead of every other. Maybe those, somewhere in the continuous string of letters that make up the O.T., form words of phrases. Sometimes you look for the words forwards in the text, sometimes backwards, sometimes diagonally.

With hundred of thousands of words and even more letters, you have an almost infinite number of possible skip patterns, you have many, many places to look for encoded words. Isaac Newton was convinced such a code and spent years trying to find it. Dr. Rips, however, had computers. He figured out how to put the skip pattern in a table, then search the table for recognizable words. He found many such words, words that seemed to predict world events long after the Bible was written. In Bible Code 1 Drosnin described the process. In Bible Code II he expanded on it. As a control, they tried the same thing with other books of a similar lengths, and learned that these books did not form words or phrases in similar skip patterns in any meaningful way.

The conclusion: The Hebrew Old Testament contains a code that predicts future events. Who wrote the code? To the secular Drosnin that is unknown. To the devout Dr. Rips it had to be God.

The problem is that most events found in the code are found after the event happened. G.W. Bush is elected president? Break out your computer, search for “Bush” with an infinite number of skip patterns and you’ll find it. A few times, however, an event was found before it happened. The code seemed to predict the assassination of Israeli Prime Minister Yitzhak Rabin in 1995, and was found in 1994 and communicated to Rabin. The assassination happened—in 1995.

In the Bible Code 2, published in 2002, six years after the first book, the main premise is that a nuclear holocaust was going to happen; it would start in Jerusalem and result in annihilation of the Israelis and the Palestinians. Like other coded events, it was tied to a year, in this case 2006.

Yes, 2006. Fourteen years ago. A major part of the book was a warning that we must somehow prevent this from happening. In 2002 world conditions looked awful. Iran was angling to get the bomb. The Palestinians were in the midst of the second Intifada and Israel was aggressively resisting. The 9/11 attacks were fresh on everyone’s mind. We seemed to be in the age of terrorism in a new way.

Yet, no nuclear holocaust occurred in 2006, of in 2007, or in 2008, or any year since.

Is the Bible code real? I have no idea and have no way of judging if Rips and Drosnin are doing something valuable of are engaged in a well-meaning smoke-and-mirrors error. I do know that Drosnin’s work receives lots of criticism.

Should you buy the book and use your valuable time reading it? Probably not. It’s somewhat boring and quite repetitive. It’s actually a quick read since much of the book is diagrams of the code, in Hebrew with English translations. I intend to do a little investigation from my reading chair and see what these gentlemen have said in the intervening years. And see what others are saying about the Bible code and its validity. If there is a Bible Code III, however, I for sure won’t be reading it.

If you want to look at this further, Wikipedia has an excellent article on the Bible code.

I’m a little behind on my book reviews. Catching up by starting with the last one I finished.

Before our recent trip to Mexico I was looking for a paperback to take with me to read in airports, on planes, and at night in hotels. I decided to look in a box of books in the garage that was waiting to be donated and found this, Holy War for the Promised Land by David Dolan. I’m pretty sure I never read this, and don’t think I bought it anywhere. How it came in our possession, and why it was in a donation box unread is anyone’s guess. It had a book marker in it, a random piece of paper that doesn’t match anything we have in the house. A minor mystery.

It’s an excellent book. Published in 1991 (so written probably in 1990), it covered the Holy Land situation as it was at that time. Obviously, close to 30 years of history has occurred since then and the book could easily be updated.

Dolan is a Christian who lived in Israel for many years, mostly as a correspondent, leading up to and including the years of the Palestinian Intifada. He starts chapters with an experience he lived through, then shifts to the issues of the broader conflict. He goes back to the times of the Patriarchs, of dispersing of the Jews on two occasions, of Christianity spreading through the Middle East, followed by the rise of Islam.

It goes on from there to the Crusades, the Ottoman conquest, and into the 20th Century. The migration of Jews to the Holy Land, the conflicts with the Arabs, the role of Britain, the creation of Israel by the United Nations, and the subsequent conflicts are all covered. He did a good job, I believe, in approaching the conflict from both sides. The Arab/Moslem hatred for Israel and Jews, the strong measures Israel took to guarantee its security, the dashed hopes for peace, and the intransigence of both sides are all covered.

I naturally sympathize with the Jews, believing Israel has a right to exist with secure borders. It’s hard to see that happening when a people who are 20 times as numerous and have 100 times as much land have vowed to wipe them off the face of the earth and say so every day. I’m fairly sure Dolan believes more or less the same. Though the plight of the Palestinians can’t be ignored. Their condition is described in the book, though no real solution is proposed. That’s okay. As a hard news correspondent, Dolan reports the news, he doesn’t editorialize.

I found the book very readable. It served its purpose. I read large amounts of it in airports and on planes. Not so much in hotels, as the efforts of touring made reading less enticing. I completed the 254 pages in eleven sittings, most of it while traveling.

It wasn’t that long ago that I read a similar book, Jews, God and History and reviewed it on this blog. The subject matter is different, as Dolan’s book focuses only on Israel and adjacent lands, not on wherever Jews lived in the world. So it’s hard to say one is better than the other. Dolan’s book was more easily read.

Is it worth your finding a copy and reading it? Probably not, mainly because so much more has happened since. As to what becomes of it, it’s an easy choice. It’s going back into the donation box. Too many books in the house, gotta get rid of some. I’m quite happy I read it, but don’t see me ever needing it again.