Summary of "The Risks of Having a BUM Experience" (September 2004 Digest)


BUM stands for Believing an Unintended Message. Visitors to many pro-code web sites, and readers of a number of pro-code books, face a very high risk of having a BUM experience. Why? Because the matrices presented are so sketchy you could come up with the same thing from the Jerusalem phone book.

The recipe is always the same. A code researcher looks for and finds a handful of short single Hebrew words as ELSs in a matrix, and touts it as proof that God encoded these “related” words. The biggest problem is that any code dabbler can look for and find short Hebrew words as ELSs in any scrambled pile of Hebrew letters.

A Sketchy Matrix
Several years ago CalTech Professor Barry Simon posted an example sketchy matrix of “codes” about Hanukah. His example was as impressive looking as most in published pro-code books and web sites. The problem was that he came up with it by looking in a Hebrew translation of Tolstoy’s novel, War & Peace. In other words, his matrix consisted entirely of ELSs that were not encoded.

A Wake-Up Call
This should have been a wake-up call to code researchers that they at least needed to come up with more extensive examples than the Hanukah matrix. At BCD, we have decided to take a more active role in trying to open people’s eyes to the foolishness of attaching any significance to sketchy matrices.

To reduce the risks of having a BUM experience with ELS matrices, it is vitally important that the matrix include ELSs that are highly improbable. To get that, one needs to find lengthy ELSs in decent Hebrew. If some of these are close to one another, that helps all the more.

One of our goals at BCD is to try to present clusters or matrices that are so extensive that code skeptics such as Simon or McKay would have to sweat blood for months or years, or even a few lifetimes, to come up with a comparable example from a non-encoded text. When we started this search a number of years ago, we did not believe we would succeed, thus further showing that Bible codes are bunk. We’ve been turned on our heads by some of the highly complex and very extensive clusters we have found after doing comparatively little work, as well as some sprawling matrices such as Shak has discovered. So we have had to admit that something about this phenomenon is real.

Assess the Risk
How can you quickly assess what the risk is of having a BUM experience? First, you throw out any ELS that is six or fewer letters long. Then for each remaining code, you count up how many letters each ELS has in excess of six. If your total score is less than 50, the risk is very high. And the lower the score, the greater the risk. This is the case with the most extensive examples in Drosnin's first book. Each of these only score 11 or 12 points.

In a previous article, Comparing Apples and Oranges, six BCD clusters each scored more than 200 points. The Ezekiel 37 cluster scores 1,044 points. The odds that such clusters are coincidental are virtually nil.


Full Article: The Risks of Having a BUM Experience



Enjoy finding your own Bible codes.
Bible code search software is available in our online store.



Subscribe Free!

By signing up to be a member of The Isaac Newton Bible Research Society, you will have access to more than fifteen years of research by our team of Bible code researchers.

Sign up to be a member today.





Now available, donate using PayPal ↓











Wisdom 365 provides daily readings of ALL of the Buddha’s proverbs, accompanied by similar proverbs of Solomon.

To read more about this groundbreaking book, click here, or click below to order from Amazon today!









| HOME | SUBSCRIBERS ONLY | OUR PURPOSE | FREE SAMPLES | CURRENT |
| FAQs | ABOUT BIBLE CODES | SUBSCRIBE | CONTACT |

Copyright © 2017 BibleCodeDigest.com