I don't quite get your analogy. Not to mention with DNA there are quite a good deal of error correction built in during the replication process. You can make gibberish, but the replication process can self correct (to a degree).. or the organism just doesn't live. As I say splicing DNA saves time because you know the trait you want exist at that location, you just cut that portion and put it in the target DNA and hope for the best. Usually you go through a few thousand tries before you get the splice to work correctly.
I would say if you want an easy to understand analogy: DNA splice is more like a .reg file in Windows, the creature is the Windows registry and the replication process is the parser. You can import a reg file about Photoshop, but if Photoshop is not installed on the machine, Windows will do weird things. DNA itself is not a report, it doesn't have any meaning.
Quote:
Originally Posted by DragonChi
About the copy and pasting thing, I've copy and pasted material into different revisions of reports, only to proof read it later and having the report make no sense unless revision is done. This doesn't happen with ATGC constructs? I suppose it's like comparing apples to oranges, the report writing and genetics metaphor.
|