I have discussed this exact analogy with a couple colleagues from a CS background. If someone said the genome is the source code that's very wrong. The more accurate analogy is that your genome is a compiled, highly compressed executable file (more or less 200 MB in size?) Where the optimizer blindly reuses variables and memory locations for multiple routines that may or may not be related. It probably is quite similar to oracle's DB2 codebase, where all this shit is in C, and you change some variable here and hell breaks loose somewhere else. For the most part though, if you don't tinker with it, it runs like a well oiled machine because a blind watchmaker programmer (with great intuition but no CS organization fundamentals) has debugged and patched it for billions of years, patch on top of patch millions of times over.