X hits on this document

Word document

Blue Helmets to Jerusalem - page 58 / 95





58 / 95

mother's womb...fearfully and wonderfully made...in your book all my parts were written down before any of them came into being..." in my own paraphrase from the Bible, Psalm 139, verses 13-18.

While I was growing up, clothing labels were sewn somewhere inside a garment. If you had a label showing, a friend was quick to point it out. Designer jeans were the first to make acceptable the practice of sewing manufacturers' labels onto the outside. Similarly, when I look into a human face, the love and intelligence I see there is, to me, a reflection of the face of God. It is his designer's label, sewn into our designer genes.

Displayed on the wall of my office is a colorful chart titled "Human Genome Landmarks" and subtitled "Selected Traits and Disorders Mapped to Chromosomes." The chart cost me nothing, since it was available for the asking from a government web site: www.ornl.gov/hgmis/posters. The letters HGMIS in that URL stand for Human Genome Management Information System, a division of the federal government's Oak Ridge National Laboratory (www.ornl.gov).

The poster lists countless human traits such as skin color and hair texture, and many more ailments or diseases such as diabetes and sickle-cell anemia, along with the location of the genetic code that determines those traits or hereditary susceptibility to those disorders. For example, some time long ago a mutation caused an A to be replaced with a T in a someone's genetic code, in the portion of their DNA coded for hemoglobin, and this caused them to pass on to their offspring sickle-cell anemia as a hereditary disease.

Disease resulting from accidental mutations makes sense. But upward evolution from ocean slime to human beings is a ridiculous proposition, when the code that would have to be written is taken into consideration. Something similar to random spontaneous mutations takes place in computers when disk media ages or when some stray electrical current, or some other unknown element, causes code to be "corrupted." Corrupted code can result in a computer program behaving strangely—such as displaying incorrect numerical values on screen—

or even breaking down completely and failing to function. But corrupted code never results in new and improved programs. Corruption in the computer code can cause Windows 98 to crash, but such spontaneous changes can not cause Windows 98 to become Windows XP.

Similarly, as Dr. Lee Spetner points out in his book Not by Chance! - Shattering the Modern Theory of Evolution (The Judaica Press, 1998), mutations have never been shown to add new code to the genome. This should not be surprising, because the chances of code that actually works being written by accident becomes less and less likely the longer the code. While the chances of picking a winning three-digit lottery number are one in a thousand, a six-digit number lowers those odds to one in a million. Add three more digits, and the odds become one in a billion. At twelve digits, the odds fall to one in a trillion. Yet, a web designer may use a hundred characters to write a single line of JavaScript code, and thousands of lines of code to write a simple computer program. And his most complex interactive website looks like a kindergarten child's project next to the genetic code of a simple insect.

No wonder that new and improved software never pops into being through accidental corruption of code! Imagine, then, the odds against new DNA code being added to the genome by accident. Considering that there are billions of DNA subunits in the human genome, the chances are astronomically impossible. The 'millions of mutations over millions of years' that evolutionists point to don't even come close to making the chance origin of life believable, never mind the evolution of intelligent humans.

Sometimes a computer programmer will sit down to create a website or a computer application and will start from scratch, opening a text editor or word processor and writing code. But, more often than not, he will start by grabbing an existing file and will use this as a template to aid in creating the new one. To add the different functionality needed in the new version, he will look through his collection of code saved over the years, and copy various snippets and paste them into the new file in appropriate spots.

This is, according to my layman's understanding,

Document info
Document views173
Page views173
Page last viewedThu Oct 27 06:02:57 UTC 2016