posted on Jun, 4 2009 @ 03:15 AM
I'm a programmer, and I design/create systems for a living. Over time, my programs evolve and programs carry many of the same code among them.
I see the exact same thing in nature and reality.
If I created a program today called "monkey", and then tomorrow I created a program called "human", then you can bet that the 2 will carry alot of
the same code in them.
In the programming world, we have what are called dynamic link libraries. You have probably called them drivers, they are .dll files. But these
things are libraries of common code. Code which is so common that is used among a variety of programs. In order to save space and such, since the
code is used so much, we keep only 1 copy of that code. And then all the programs which use that library, add a "link" to the library in the
code, and then you have access to that library. One thing that is cool about libraries is you can update 1 library and update multiple programs at
the same time. IE: Graphics drivers are a commonly used example.
Now when calling this drivers and such in code, you pretty much get a configuration file. While the library itself may have thousands of lines of
code, we can generally work with that library in only a few lines of code. This ends up like being a "configuration" effect. Your program is
basically configuring the information up to be used with the library.
These libraries in the programming world reside in a different folder usually, aka another "dimension".
So when you look at DNA, what you are basically looking at is a configuration file that would work with other libraries somewhere else. Genetics is
really just the reverse engineering of this config files. If you open up a config file to a program, you make 1 little edit and it can have big
effects on appearance. Find a line in the config that changes a color, and the color of the app changes. Change the title, looks, function and so
forth with a little edit here and there. Change a gene in the DNA, same exact effect.
So, cells are just little self reproducing nanobots that read the DNA code in order to build the physical body. Change the DNA code, and the
nanobots change in what they do.
This doesn't mean that survival of the fittest and such doesn't happen. It does. But even with all these changes, the actual code itself isn't
change, only the configuration changes.
If anyone plays a game that allows addon's or interface changes, think of it like peoples interface. You can change the config around alot and get
things to look and function a bit differently. But the code behind it that runs it stays the same.
Afterall, a small change can have big effects. Take a look at size for example. Let's use a square to be simple. The size of that square is
just a change from 10 feet, to 100 feet. And from that minor and simple change, obviously the square has huge changes in the render/physical.
Many unique programs all unique based on the config, but all using the exact same code.
So when I look out in the universe I just see a program. And when you have a program, you have a programmer. Of course, looking for the programmer
in the program itself is about like trying to find Bill Gates in your OS.
[edit on 4-6-2009 by badmedia]