Good post, #17. Also, there is no possible way for all the information in the "blueprint" for a human being to be contained in the DNA in each human cell. It would take many hundreds of gigabytes of data to actually store all the molecular and macro level structual design for a human being. For example, there are some brain cells in humans that connect to 200,000 other brain cells, while other brain cells connect to far fewer brain cells.
for (number_of_brain_cells) {
}
Meanwhile we have about 15 billion brain cells. Think of the amount of data required to store blueprints for all the cells themselves and then all the connections between the cells. And that's just the beginning...there's the bone structure, muscular strucure, cardiovascular system, etc. You get the idea. There's no possible way for all this information to be stored in the DNA in each cell in the human body and there would be no way to precisely replicate all that data millions of times every week in cell division.
A well designed program can do all of this. One does not need that many rules to create great complexity, especially when you start with such a versatile base class like a cell. This is the part of the ID debate that I love. In good Object Oriented design you build usefull tools that don’t really care who is using them or why. So the issue that apes, chimpanzees, and humans share some useful bits that do similar things points me to great design. Why remake when you can reuse. This is both efficient and elegant.
Example I have an ape class, a chimpanzee class and a human class all of them use the breath() method as a programmer why would I re-code the breath method for each and every type of creature that would be very poor design.
I can take this much deeper but it would require you to understand more programmer nerd speak and definitions than most people can handle or tolerate. Clearly I have let my nerd flag fly. I hope you find this helpful.