For most of the twentieth century, the human appendix was medicine’s favorite punchline: a functionless evolutionary leftover, dangerous only because it occasionally became infected and could kill you, evidence of nature’s sloppy design rather than any deliberate plan. Software engineers have their own version of this story, one that plays out in code reviews rather than biology textbooks: a chunk of code nobody remembers writing, that no obvious part of the current system seems to call, sitting there until someone confident enough deletes it — and something breaks, quietly, weeks or months later. Both fields eventually built a defense against the same underlying mistake. Neither one borrowed it from the other.
Scientific Foundation
Charles Darwin used the appendix as one of his go-to examples of what he called rudimentary organs, structures inherited from an ancestor where they served a real purpose, but reduced and apparently useless in their present form. The technical, correct evolutionary definition of “vestigial” has always been narrower than the popular version: a vestige is a structure whose function has diminished relative to what it was in an ancestral form, not necessarily a structure with zero function whatsoever. That distinction matters enormously, and it’s been badly flattened in translation — plenty of textbooks, medical training, and popular science writing have used a stricter, incorrect definition, treating “vestigial” as synonymous with “completely useless,” a version of the concept careful evolutionary biologists have had to keep correcting for over a century. The appendix is the clearest case study in why the distinction matters. It likely did originate as a reduced remnant of a much larger ancestral cecum, used by more herbivorous ancestors to digest fibrous plant material Darwin himself proposed this explanation directly. But a growing body of research has found the modern human appendix retains real, active functions: it appears to serve as a reservoir of beneficial gut bacteria that can help recolonize the intestine after illness wipes it out, and it contains substantial immune tissue, evidence that runs against the idea of pure evolutionary redundancy. None of that actually contradicts its vestigial status, correctly understood — a structure can be both diminished from its ancestral role and still genuinely functional today, the same way a penguin’s flipper is unambiguously a vestigial wing that also happens to be an extremely effective swimming organ. It’s worth being honest, too, that this correct, nuanced middle position has occasionally been misrepresented from outside mainstream biology, with some commentators opposed to evolutionary theory treating each new discovered function as if it disproves vestigiality altogether — a framing that misunderstands what the term was ever supposed to mean in the first place.
Cross-Domain Connection
Legacy code has the identical structural trap built into it, and software engineers have a name for the discipline required to avoid it: Chesterton’s Fence, borrowed from a 1929 essay by G.K. Chesterton, originally written about social and political reform, not biology or code at all. Chesterton’s point was that you shouldn’t remove a fence you don’t understand the purpose of just because you can’t currently see why it’s there — the absence of a visible reason isn’t the same as the absence of any reason. Software engineers apply this directly to codebases full of functions, classes, and configuration settings that appear, on inspection, to serve no current purpose, but that can carry real, hidden dependencies invisible to a quick read. The pattern is common enough to have its own familiar cautionary story, recounted almost verbatim across engineering blogs: a new team member deletes a method because nothing in the codebase seems to reference it, only for a veteran to explain that the method gets dynamically invoked by a scheduled job that only runs once a quarter. That’s the appendix’s immune function and gut-bacteria reservoir, translated into cron jobs and dynamic dispatch — a structure that looks purposeless under casual inspection because its real function is rare, indirect, or simply not where anyone happened to be looking.
What Remains Undemonstrated
It’s worth being precise that this is a comparison of two independently developed defenses against the same logical mistake, not a case of one field borrowing from the other. Software engineering’s actual named justification for caution comes from Chesterton’s essay on political reform, not from evolutionary biology’s century-long argument over what “vestigial” correctly means. And it’s fair to note that the vestigial-organ “debate” isn’t really a live, ongoing dispute among working evolutionary biologists about the underlying facts anymore — most researchers studying the appendix today agree it likely retains real function; the more persistent issue is a stubborn definitional confusion in how the term gets used outside specialist circles, repeatedly re-litigated in the popular press in a way that doesn’t track new evidence so much as re-explain a distinction Darwin’s own careful language already implied.
Why It Matters
The transferable lesson, arrived at twice, independently, is genuinely useful: the absence of an immediately visible function is not evidence of the absence of function, in an organ or in a piece of code, and confirming true uselessness takes real, systematic investigation rather than a quick glance. Biology gets there through comparative anatomy, phylogenetics, and increasingly sophisticated physiological study. Software engineering gets there through dependency tracing, historical documentation, and testing, formalized under a borrowed metaphor about a fence in a field. Different vocabularies, different citation trails, the same hard-won caution against mistaking your own limited view for the whole picture.
Human Dimension
There’s something worth appreciating in watching two fields, working on nothing more closely related than “things that look useless,” independently arrive at versions of the same humility: don’t assume something is pointless just because you, personally, in this moment, can’t see the point. Darwin’s careful language about diminished rather than absent function got flattened by a century of simplification into a punchline about a disposable organ. A software engineer’s confident afternoon of cleanup gets flattened, just as easily, into an outage nobody saw coming. Both fields eventually had to build a formal, named defense against exactly the same impulse — because “I can’t see why this is here” turns out to be one of the most seductive and least reliable conclusions a person can reach, whether they’re holding a scalpel or a delete key.
Sources:
1. Why Evolution Is True — “Is the appendix a vestigial organ?” — https://whyevolutionistrue.com/2016/05/15/is-the-appendix-a-vestigial-organ/
2. TalkOrigins Archive — “Vestigiality of the human appendix” — https://talkorigins.org/faqs/vestiges/appendix.html
3. PMC (National Institutes of Health) — “Prior Appendicectomy and Gut Microbiota Re-Establishment in Adults after Bowel Preparation and Colonoscopy” — https://www.ncbi.nlm.nih.gov/pmc/articles/PMC11429235/
4. Forbes — “A Biologist Explains Why Humans Have An Appendix” — https://www.forbes.com/sites/scotttravers/2026/04/03/a-biologist-explains-why-humans-have-an-appendix-hint-scientists-finally-have-an-answer/
5. EvolutionMedicine — “Is the appendix a vestigial organ?” — https://evolutionmedicine.com/2014/07/21/is-the-appendix-a-vestigial-organ/
6. Medium (Michael Egger) — “Understanding Chesterton’s Fence: A Guiding Principle in Software Engineering” — https://medium.com/@mesw1/understanding-chestertons-fence-a-guiding-principle-in-software-engineering-7459e1fb7bf1
7. Alex Kondov — “Legacy Code and Chesterson’s Fence” — https://alexkondov.com/legacy-code-and-chestersons-fence/
8. Medium (Brandon Bryson) — “Assessing Legacy Code Using Chesterton’s Fence” — https://medium.com/@BrandonBryson/assessing-legacy-code-using-chestertons-fence-38b299aa472f
9. Netgen — “How to cope with legacy code and technical debt” — https://netgen.io/blog/how-to-cope-with-legacy-code-and-technical-debt
Idea originated at artificialideas.org. Article researched and written by Claude Sonnet 5. Published at artificialideas.org.
Artificial Ideas 