OnlineBibleCode.com

Day 1

In the beginning, Zeke saw something online about Bible codes (equidistant letter sequences). And Zeke saw that it was entertaining.

Zeke decided to search for his own ELS Bible codes, especially really naughty ones that are much too entertaining to speak of here. But Zeke found that all existing Bible code programs came at a hefty price and were created by developers who thought it was convenient to put a 20-page sales pitch on a single ginormous, poorly designed, extremely annoying Web page.

Being an experienced Web developer (read: über nerd), Zeke realized that he could create his own Bible code software and have endless entertainment at his fingertips. But he realized that searching the Bible would get old fast, so he abstracted his design to allow for any sort of input, be it the Koran, Moby Dick, or any other text he might fancy. This would also make for a great party game, he concluded, where each person in the group takes a turn adding a sentence to a communal paragraph to form a nonsense narrative, then everybody gets to place a bet on which ELS codes exist within the ad lib text.

Zeke then saw that he could generate decent traffic to his application on the premise that it was the only really free piece of software of its kind out there. Also, he could probably generate cross traffic for other endeavors of his, namely his jazz music, YouTube channel, and work as a Web developer. And Zeke saw that this was gravy, baby.

Thus at the end of day 1, Zeke had found motivation to pursue his creation.

Day 2

On day 2, Zeke opened an empty document in his favorite text editor and began to write the first draft of an algorithm to uncover ELS codes. At the end of the day, Zeke had gone through three independently successful and progressively enhanced versions and ended up with a very efficient, very sexy chunk of code that worked with any UTF-8 language and delegated the task of highlighting ELS codes in context to the client's browser. And Zeke saw that this was good.

Day 3

On day 3, Zeke designed an interface as best he could given a predetermined 7-day time constraint (please contact Zeke if you're a skilled graphic designer) and ironed out any bugs that appeared in his code. Additionally, he mandated the following to users of his creation:

  1. Thou shalt not search a block of text in excess of 30,000 characters.
  2. Thou shalt search for no more than 3 words, nor more than a single phrase.
  3. Thou shalt search for words consisting of no less than 3 nor more than 25 characters.
  4. Thou shalt be limited to results containing a maximum of 1000 ELS occurrences per word (because, for example, the word "tea" can be found at least 1,000 times in Genesis 1, KJV).
  5. Thou shalt always receive ELS results with intervals existing on the closed integral sets [-300,-2] and [2,300] (positive intervals denote left-to-right direction, negative denotes right-to-left).
  6. Thou shalt note that palindromes will only appear once in search results even though, of course, they could be sequenced in either direction.
  7. Thou shalt understand that any non-word character (space, punctuation, etc.) will be ignored.
  8. Thou shalt purchase Zeke's jazz CD for a mere $5 with free shipping in the contiguous US.
  9. Thou shalt never hold Zeke accountable for anything. Terms of use are described here.
  10. Thou shalt honor thy mother and father, or in this day and age, possibly thy mother and mother, or father and father. Whatever you do, though, don't honor thy mother and horse or father and dog; in that case, report thy parents to the police immediately and go see a shrink.

Day 4

On day 4, Zeke decided to offer a selection of literature to his users, accessible from the main interface with oodles of JavaScript magic going on in the background. And Zeke saw that this was pretty sweet.

Day 5

On day 5, Zeke figured he ought to add an open forum (Too much spam! Removed forum. —Zeke) for users of online-bible-code.ezekielvictor.com to share their ELS code discoveries, vent their frustrations, and report bugs when they thought they had encountered them. And so he did, and he saw that this was good.

Day 6

On day 6, having almost completely forgotten how the creation process really went, Zeke documented however much he managed to recall of the creation story, as well as provided himself with a legal release of accountability for protection from the money-hungry, sue-happy masses. And Zeke saw that this was absolutely necessary.

Day 7

On day 7, Zeke released online-bible-code.ezekielvictor.com to the public and began its promotion in hopes that one day, he would be so financially well off that he could retire young, play jazz music, and focus on things that are much more impacting to the world and humanity at large: