- Save 10% on selected children’s books, compliments of Amazon Family Promotion exclusive for Prime members .
The Bible Code Paperback – 15 Dec 1997
- Choose from over 13,000 locations across the UK
- Prime members get unlimited deliveries at no additional cost
- Find your preferred location and add it to your address book
- Dispatch to this address when you check out
Special offers and product promotions
Frequently bought together
Customers who bought this item also bought
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
If you are a seller for this product, would you like to suggest updates through seller support?
A new book says Rabin's murder was predicted, and there are dreadful things to
come. Should we fear?
Explosive....No wonder the book is causing a sensation.
"Los Angeles Times"
A certifiable phenomenon. The text abounds with stunning predictions.
"Los Angeles Times" A certifiable phenomenon. The text abounds with stunning predictions.
"Time" A new book says Rabin's murder was predicted, and there are dreadful things to come. Should we fear?
"Newsweek" Explosive....No wonder the book is causing a sensation.
Newsweek Explosive....No wonder the book is causing a sensation.
Los Angeles Times A certifiable phenomenon. The text abounds with stunning predictions.
Time A new book says Rabin's murder was predicted, and there are dreadful things to come. Should we fear? -- Dieser Text bezieht sich auf eine vergriffene oder nicht verfügbare Ausgabe dieses Titels.
The original THE BIBLE CODE - a phenomenal bestseller across the worldSee all Product description
What other items do customers buy after viewing this item?
Top customer reviews
The "evidence" sounds pretty good at first. Drosnin constantly repeats the fact that the Bible Code predicted the assassination of Israel's Prime Minister Rabin, the collision of the comet Shoemaker-Levy into Jupiter, the start of the first Gulf War, etc., all to the very day. Tell me more, you think to yourself. This is where Drosnin starts to slip, however. He spends most of his time talking about Armageddon, specifically how Jerusalem will be destroyed by a nuclear bomb. He was certainly right in naming terrorist acquisition of weapons of mass destruction to be the greatest threat to the modern world, but prophesying trouble in the Middle East doesn't exactly require a Karnak. He predicts that then-Prime Minister Netanyahu will be assassinated and that Israel will be attacked in 1996. This book was published in 1997, completed after 1996 came and went. Suddenly we find Drosnin discovering that the word "delayed" just so happens to turn up alongside all of those dire predictions of his. He actually expresses the opinion that a delay in Netanyahu's visit to Jordan prevented the Armageddon he had predicted. The Bible Code, he now decides, must include eventualities, things that may come to pass, things that we can prevent from coming to pass. This back pedaling hurts his credibility quite a bit in my eyes.
In summary, I can't argue the mathematical validity of The Bible Code in any way, shape, or form, but Drosnin's arguments fail to convince me that he is right about this subject. He can barely find anything in his code until that "thing" has already happened, and it seems to me that finding a few related words after the fact on a sheet full of letters is no difficult feat. I do know that there is one definite error in the book, as Drosnin (and the Bible Code) shows that FDR declared war on Japan on December 7, 1941, when war was not declared until the following day, December 8. As for the predictions he did make about the future, he doesn't exactly go out on a limb. There will be strife in the Middle East and a series of earthquakes in Japan. These things happen every year, so these are hardly convincing prophetic tests of his code. I can't say The Bible Code does not exist the way Drosnin says it does, but it will take a whole lot more evidence to ever convince me of such a fact.
1. Bear in mind that in finding the code, the Torah is placed on the computer-equivalent of a cylinder which can be expanded or contracted until a match is found. With every letter added to the horizontal length of the lines, a whole new set of words becomes possible vertically and diagonally (they remain the same horizontally). The reference to the ten commandments being computer-generated is found in a segment only ten letters wide, whereas some words have letters spaced chapters apart-which can be juxtaposed only by expanding the cylinder to a thousand letters or more in width.
2. The hardest part to find is a person's name, but given that the name can be read in any direction, with any number of equidistant spaces between the letters, and that the computer can adjust the line length, and that any possible variation of spelling is allowed, and that abbreviations, initials, and nicknames are allowed, the wonder would be if any name could not be found (see p. 27). Drosnin generally finds the name vertically by expanding or contracting the line length, then looks for the words around it.
3. The Hebrew used is "unvocalized," it does not use vowel pointings, but Drosnin uses the letters aleph, ayin, waw, and yod as semi-vowels where convenient. These semi-vowels can be used to approximate a number of vowels (yod might represent IH, EE, EYE, EH, EI, for example). Thus, exact spelling is not essential-"sounds similar" is close enough. If none of these semi-vowels occur, the word is simply read without vowels. (For example, President Clinton's name is spelled Q L Y N T W N. "President" is N S Y A which means "leader" or "ruler" and is in fact the Hebrew word for "president" today, though it could also be seen as "Nazi." "Hitler" is found as H Y T L R, and "Nazi" as N A DZ Y. "Shakespeare" occurs as Sh Q S P Y R, "Macbeth" as M Q B T, and "Hamlet" as HMLT. Note the cavelier attitude toward vowels.)
4. In giving the computer names to search for, every possible spelling is used, whether or not the spelling has ever been used. This increases the likelihood of a match. Also, usually the words used are Hebrew, but sometimes they are English (names).
5. Without vowel points, a three letter Hebrew root may have many meanings, thus perhaps quintupling the likelihood of a match. For example, the Hebrew root 'Ayin-Lamed-He, "'LH," with one set of vowels, can mean to ascend or break or excel or fall or offer (and many more), or with different vowels it means "holocaust" or "burnt offering"; or with yet other vowels it means a branch or leaf, or with other vowels it means occasion, or, with other vowels, iniquity. But Drosnin translates words in whatever way seems convenient for the meaning he wants to find.
6. Many modern Hebrew words are based on old words with ancient but related meanings. This makes it easier to find 'modern' words in the ancient text, even though when written, the words did not have the modern meanings. For example, the word for missile.
7. Hebrew has letters which represent different sounds but might be transliterated in English by the same letter. For example, he and heth might both be represented by an H, but the latter has a gutteral CH sound. Kaph and Qoph might be written as K, Q, or C. Taw and teth might both be written as a T. Samech, sin, shin, and zayin all might be seen as S sounds. These are not used interchangeably in Hebrew, nor do scholars who transliterate Hebrew in books and articles use them interchangeably, but they are in the Bible Code, whenever convenient. This increases the chance of a match.
8. The letter field is not made up of random letter, but made up of Hebrew words without vowels. This increases the chance of a horizontal match in Hebrew, of course, even if one rearranges the letters. That is to say, on any page, whatever the line length, there will be many Hebrew words already there, read right to left. Read left to right, some of these words have other meanings. If one begins with the second letter in a word rather than the first letter, one may get yet more words.
9. The dates are based on a letter / number code in which each letter represents a number. As the Torah is all letters, this also makes a match more likely. Also, modern Hebrew dates often leave off the millennium number (1891 would be written, in Hebrew letters, 891). Thus, Drosnin's finding of dates such as "2013" could as well be 1013 or 3013. He never explains this to his readers.
10. Most "pages" have a thousand or more letters to choose from, nearly every three of which constitute a Hebrew word root, in any direction. The chance of finding something somewhat significant on a page with a name on it is quite high. If nothing is found, perhaps the computer might find the name elsewhere.