Helpful Score: 2
It was a very clinical read, which is to be expected when presenting a body of facts and evidence. Presented from a non-Christian writer's point of view. It was okay, but not riveting.
Helpful Score: 2
A lot of the dazzle of this book is gone once you realize that, if you can read Hebrew, the horizontal text is just plain text. So he's just playing find-a-word vertically (without vowels, so, for instance, DALLAS would be DLS), and then looks for words 'crossing' it - of course words cross it! It's plain text!
Looking at what I've written so far, breaking at every 32nd letter:
Alotofthedazzleofthisbookisgoneo
nceyourealizethatifyoucanreadHeb
rewthehorizontaltextisjustplaint
extSohesjustplayingfindawordvert
icallywithoutvowelssoforinstance
DALLASwouldbeDLSandthenlooksforw
Ordscrossingitofcoursewordscross
itItsplaintextLookingatwhatIvewr
ittensofar
Look! 'Die' crosses 'Dallas'! That 'proves' my text magically knew about the Kennedy assasination!
He does the same thing - he's very impressed that he found "Kennedy" crossing "president." What he found was "KND" crossing the Hebrew word for "chieftain" which he loosely translated as "president." And again, of course "chieftain" is in the text - it's plain text.
Add in to that that he rearranges these things constantly (look at every 20th letter. Nothing? Look at every 21st letter. Nothing? Look at every 22nd letter. etc.) Then he goes even farther than that, accepting diagonal words (and words at various slopes).
It's garbage, garbage, garbage, and has never predicted anything before the fact (which is, in fairness, included in the definition of predict).
Looking at what I've written so far, breaking at every 32nd letter:
Alotofthedazzleofthisbookisgoneo
nceyourealizethatifyoucanreadHeb
rewthehorizontaltextisjustplaint
extSohesjustplayingfindawordvert
icallywithoutvowelssoforinstance
DALLASwouldbeDLSandthenlooksforw
Ordscrossingitofcoursewordscross
itItsplaintextLookingatwhatIvewr
ittensofar
Look! 'Die' crosses 'Dallas'! That 'proves' my text magically knew about the Kennedy assasination!
He does the same thing - he's very impressed that he found "Kennedy" crossing "president." What he found was "KND" crossing the Hebrew word for "chieftain" which he loosely translated as "president." And again, of course "chieftain" is in the text - it's plain text.
Add in to that that he rearranges these things constantly (look at every 20th letter. Nothing? Look at every 21st letter. Nothing? Look at every 22nd letter. etc.) Then he goes even farther than that, accepting diagonal words (and words at various slopes).
It's garbage, garbage, garbage, and has never predicted anything before the fact (which is, in fairness, included in the definition of predict).
Helpful Score: 2
I thought it was a bunch of bull personally.
Helpful Score: 1
Interesting book. The author's claims are greatly compromised due to the fact that key experts he quotes in the book deny what he says. I might look at it out of curiosity, but it seems to have absolutely no legitimacy.
From the back cover: On September 1, 1994, I flew to Israel and met in Jerusalem with a close friend of Prime Minister Yitzahk Rabin, the poet Chaim Guri. I gave him a letter which he immediately gave to the Prime Minister.
"An Israeli mathematician has discovered a hidden code in the Bible that appears to reveal the details of events that took place thousands of years after the Bible was written," my letter to Rabin stated.
"The reason I'm telling you about this is that the only time your full name -- Yitzhak Rabin -- is encoded in the Bible, the words that 'assassin that will assassinate' cross your name."
On November 4, 1995, came the awful confirmation a shot in the back from a man who believed he was on a mission from God, the murder that was encoded in the Bible three thousand years ago.
"An Israeli mathematician has discovered a hidden code in the Bible that appears to reveal the details of events that took place thousands of years after the Bible was written," my letter to Rabin stated.
"The reason I'm telling you about this is that the only time your full name -- Yitzhak Rabin -- is encoded in the Bible, the words that 'assassin that will assassinate' cross your name."
On November 4, 1995, came the awful confirmation a shot in the back from a man who believed he was on a mission from God, the murder that was encoded in the Bible three thousand years ago.
Helpful Score: 1
This is a book written on supposed codes found in the Bible. It's interesting enough, but quite illogical. The code only shows up when you look at the Bible in Hebrew (because Hebrew letters are interchangeable with numbers). So, you would find anything in code in Hebrew, really.
I did like the book, for many facts that I didn't know, but in the long run, I don't believe it. If God wanted us to know about something, He would have just written it in the Bible, rather than hide it in a code that only some people would be able to find.
I did like the book, for many facts that I didn't know, but in the long run, I don't believe it. If God wanted us to know about something, He would have just written it in the Bible, rather than hide it in a code that only some people would be able to find.
One of the first code books I ever read. Very informative, very exciting to see the hand of God in his word. loved it.
Great Hardcover copy with dust jacket, dj has some wear on the edges. Great Read, great information about many modern day events, and the book of Revelations.
this book is an excellent look into the contraversial bible codes, however, I do not recommend reading the second book in the series-the bible code 2, it takes the codes into a different direction than the readers of this book would be expecting.
Very interesting stuff! Worth a read - pretty involved, but worth the read.
Easy to read and very, very interesting stuff.
interesting, complex topic
Author states that there is hidden computer code in the bible that can tell the future. But these revelations are more a warning then they are fact. We can change our future if we heed the bible code. The book was interesting though I found a lot of it repetitive. And of course he spends a lot of time on the end of the world and armageddon. According to the author and the bible code, the year 2006 could be a very bad year for the world.
