The compiled code of the individual classes in my package structure are collected and bound to the target system platform for installation. My framework is written primarily in java , so the options for execution platform include pretty much any platform desired thanks to the ubiquity of the jvm runtime environment. The similarity between a cell of a given type and a package of classes is striking, both have a core set of instructions from which the behavior of the cell through its membrane is exhibited. In the cell , these instructions are the genes but in the application distribution they are simply the class files. In biology , molecular biologists are figuring out that several ideas that had long been believed to be true were simply wrong. The first to fall was the idea of 1:1 correspondence between genes and proteins. This mantra went on for years on the belief that the answer to protein synthesis had to be simple, well that was quite an arrogant and wrong idea. The use of the base nucleotides ensures that just the number of ways in which the molecules could combine to stable structures is far far beyond the number of grains of sand on Earth or on any other rocky body in the solar system. Proteins fold to define how they interact in the system , their folding is directly constrained by the cellular chemistry in their formative environments...so literally having the right substances available during the transcription and protein synthesis phases can modify the protein created. Genes encode for a complex set of polypeptides which can include more than one protein. Another idea that was thrown out is the idea that non coding regions in the DNA were labeled as "junk" , it turns out these regions play critical signaling and timing roles in the expression of enzymes and proteins. Just as sheet music filled with notes without timing spacing could never allow a pianist to make a rendering faithful to the composers design, so to does it seem that DNA genes (specified by the active promoter regions called CPG islands) have their expression modulated by the important interstitial "junk".
It turns out cells have adapted evolutionarily in some ways to produce different variants of a protein by expressing a single gene, ...worse(or better depending on your pov) it seems some proteins require a dance be played between multiple genes to express the proper variant. The complexities are legion. In recent years the power of the type agnostic stem cells which can differentiate into any required cell type has provided a direct analog to concepts in OO programming. When we look at the analogs in OO design , had we been so bold we might have predicted the biological truths that have been recently discovered. This is because in OO , the classes that we design that provide for instance creation of objects in memory in most OO languages have similar complex relationships. In java for example we have interfaces (signature without implementation), we have abstract base classes (abstract signatures and concrete implementations) , we have concrete classes (concrete implementations only) and by using multiple interfaces we can simulate multiple inheritance. The abilities mirror very closely what we have discovered about the biological analog in genes.
One might wonder why create such tools as interfaces and abstract base classes, the answer is that they can significantly save the developer on coding time by reducing redundancy and promoting code reuse when employed properly. If a particular function can be called by multiple objects or classes that needed it without having to duplicate the function in code in those different classes...the energy expenditure of the developer is less since he does less code, but more importantly the computer in loading the instructions associated with the running application , loads fewer bytes, and each byte takes time to load and costs processor and memory resources as well. Ultimately the design of methods to allow facile prototyping of classes by using interfaces to define their structures and force implementations in inheriting classes, or to use ABC's to perform a mix of abstract signature creation and concrete method implementation (my preferred tool) in a programming language are ones which bottom line , conserve energy.
They conserve the use of energy of the coding agent (you and me the programmers) and they conserve energy of the executing computer. (in terms of compute time and required execution memory) In biology , the same goal is at the heart of the designs , except it bubbles up from the intrinsic rules of physical chemistry that determine how biomolecules will prefer to combine or orient based on their shape. (bond structure) The search for conservation of energy is what allows proteins to fold into the shapes they have when a given sequence of nucleotides is combined in a conducive intra cellular environment. The same law guides the use of multiple genes to express multiple protein variants..if you can use 3 genes to synthesize 30 critical protein variants it is far more energy efficient than having 30 genes doing one each. The evolutionary likelihood of such genes arising and then being selected for beneficial use is vanishingly small than the chance of existing genes being co opted , existing chemistry conditions promoting the synthesis of variations of protein structure that have usefulness in the organism. In biology, the guiding hand was time and strict abeyance to the rules of chemistry that define molecular affinities, in computer engineering the guiding hand is a lazy programmer , who wants to do as much (of whatever functionality) with as little as he can and do it in the memory space provided with the processing speeds available...it only makes sense that the two goals , one blind the other directed would end up serving the same god...
The similarities continue on in the build process, where a cell with its complement of expressed genes determine how it behaves (muscle, skin, bone...etc.) in a deployed application, the class hierarchy determines how a family of classes may behave based on their common pun- DNA the base classes from which they may be inherited. In the running application instances of these classes are invoked, replicated, collected and destroyed and perform the same tasks for other objects. Improper management of these tasks can lead to the accrual of junk in the running memory, enough junk leads to memory overflow and application "death". Similarly, in living beings cellular junk, the remnants of aberrant protein processes not properly degraded by the organism can build and reduce the efficiency of cellular processes. Over time this junk build up is believed to be a cause of many diseases in particular it is suspected as a major cause of the aging disease which also leads to death. Scientists are rapidly making advances in being able to reduce intra cellular cell junk to ensure the transcription and synthesis stages are kept error free throughout the organisms life time. In software engineering we have it a bit easier, when our applications begin to act sluggishly we know if we analyze the object invocation patterns we can determine the causes of the junk and remove or prevent them using a profiler. If only we had a profiler for biological organisms...the day when this is so may not be that far off.
conservation of energy rules all...
Story on junk dna not being junk
Descriptive animation from transcription to protein synthesis
one gene one polypeptide
intracelluar junk may be a cause of death