Replies

[ Truly, error correction is a hallmark of good coding and redundancy is often used for speedy recovery in vital systems. Cyclic redundancy checks are often used to assure error-free data streams. These of course require an intelligent designer. And notably, we observe similar solutions in biological systems. ]

As a manager of coders and other types of intelligent designers for many years.. I learned that proper planning looked for redundancy and variations of redundancy that is in all systems.. Intelligent System design is almost completely a matter of recognizing redundancy.. and dealing with it creatively.. Jealous management of things that happen over and over was very important when 50,000 bytes of Ram memory was a lot, much less than that was usually the rule..

I appreciated then, and do now that God does not make Bluebirds.. he made Bluebirds that make Bluebirds... The logic of that is incredibly creative and efficient.. The sub-routine of life.. There is a talent to recognizing redundancy.. and another different talent to dealing with it as "an asset".. not "a liability"..

Thank you so very much for sharing your insights!

Jealous management of things that happen over and over was very important when 50,000 bytes of Ram memory was a lot, much less than that was usually the rule..

Indeed. Subroutines are quite efficient - and I suspect we'd see a lot of subroutines in DNA encoding much earlier than we mortals discovered their efficiency in software programming.

Indeed - duplication of the organism. And even within a cell, the DNA strands are duplicated as if for a backup copy. Likewise both database and program required efficient backup systems - and the most vital control systems running in real time required duplicate systems so if one failed, the other could pick it up without breaking stride. Someone once told me that onboard airplane data processing was backed up 5 levels deep due to the risk.

And many think they were "innovators" to come up which such things in the 1960's. LOLOL!