I agree that the vehicle analogy is forced…but I know from experience that software is a better fit to a nested hierarchy.
Think of the development of Windows. It started with DOS (and technically before that CP/M). Originally, Widows was an awkward layer on top of DOS, and branched out into several concurrent variations that we would all rather forget. Then with Windows 95 (with the added bonus of “making everything you do being more fun”)…DOS was blended in and life got a little better.
Somewhere in there Windows NT branched off and the two kernels went along side by side. Windows 98 and Millennial edition were evolutionary dead ends. Windows 2000 brought a hybridization of the two lines again…then another devolution through Vista…an increase in function through Window 7 followed immediately by another dark time with Windows 8 and all the various attempts to regain evolutionary traction. Fitness increased again through Windows 10 and now is waning a bit again.
If it were possible to compare the binaries using a BLAST type tool you would find sections with identical sequence…you would see lots of homologous sections…you would see new features arrive and get persisted while others fade out and disappear…and you would likely find some junk bits that are no being called or used for anything just waiting for random mutation to stumble upon that killer new feature.
The images would be the easiest to pick out because of their correspondence with the output (protein coding regions), but the logic and control sections would be much harder to decipher and look, at least at first, like junk. Simple, but versatile code structures like loops, simple conditionals, parsing routines, and data validation code would appear all over from the early primitive versions to the latest and greatest, and even appear in viruses and other invaders.
I’m pretty sure no one at Microsoft is trying to trick us into thinking Windows evolved through a natural process, even though there are plenty of inherited traits, horizontal code transfers, and code drift.
It is not such a stretch to think that a designed information based system, especially something as intricate as life, could appear evolved to someone trying to reverse engineer it.