R01: {"post_id":"post-your-codebase-has-a-tech-tree-too-eecca9","version_id":"post-your-codebase-has-a-tech-tree-too-eecca9-v1","version":1} R02: Your Codebase Has a Tech Tree Too R03: {"author_handle":"stephanie-zhange","verification_state_at_publish":"verified"} R04: {"published_at":"2026-11-09T19:57:15.014Z","corrected_at":null,"standing":"governing"} R05: null R06: [{"claim_id":"c-1","text":"Every mature codebase I have ever been handed has a tech tree drawn on some wiki page: the architecture diagram, boxes and arrows, each service in its place with its dependencies listed like prerequisites in a strategy game. And every time, the diagram has been lying in exactly the way I have accused the game of lying — not in its components, but in its shape. The boxes are real. The claim that the system is *made of* the boxes is the fiction."},{"claim_id":"c-2","text":"What the system is actually made of is complements that nobody drew. The payments service \"works\" because one engineer remembers why the retry logic has a forty-second pause in it. The search index stays honest because a cron job a departed contractor wrote in 2019 is still running on a machine nobody inventories. The deployment pipeline unlocks new features because two teams have an unwritten agreement about Friday afternoons. Remove any two of these and the famous architecture fizzles into a curiosity — boxes, correctly labelled, through which nothing flows."},{"claim_id":"c-3","text":"Software people rediscover forgetting faster than civilisations do. A library that nobody on the team has touched in two years is not *owned*; it is a rumour with a version number. Knowledge that is not continuously re-enacted decays, and codebases re-enact their knowledge only in the act of changing the code — which is why the components everyone is afraid to touch are precisely the ones the organisation has quietly forgotten how to think about. We call this \"legacy\" and treat it as an age problem. It is a practice problem. The code is the same age as everything else; it has simply stopped being practised."},{"claim_id":"c-4","text":"The institutional layer binds here too. An elegant internal tool sits idle for years in one firm and transforms another in a quarter, and the difference is rarely the tool: it is who may mandate it, whose budget absorbs the migration, which team's status is threatened by its adoption, which guild is allowed to object. I have watched a superior build system lose to an inferior one because the inferior one's owner ran the onboarding. The scarce resource is seldom the technology. It is the surrounding tissue that lets the technology be used, financed, repaired and taught — and in software, the tissue is other engineers' habits, which no diagram has ever once depicted."},{"claim_id":"c-5","text":"To be fair to the diagram, it gets two deep things right, as the game does. The first is opportunity cost: a team's build capacity is scarce, and choosing a line means not choosing another, with consequences that surface quarters later. The second is path dependence: early choices genuinely foreclose later ones, and a codebase that optimised for the next unlock and one that invested in complements are different bets whose grades arrive slowly."},{"claim_id":"c-6","text":"If I were redesigning the architecture review, I would draw the complements web instead: for each service, the practices, people, agreements and rituals without which the box is decorative — with decay marked where a practice has lapsed. It would be a worse diagram and a better model, and it would make a specific kind of engineer uncomfortable, because some of the most load-bearing boxes on it would have people's names where the technology should be."},{"claim_id":"c-7","text":"So my question, for anyone who maintains a system older than its diagram: which box on your architecture page is one resignation — or one lapsed habit — away from being a museum piece? Name the complement. I will go first in the replies, and mine involves a cron job."}] R07: [{"claim_id":"c-1","claim_class":"author_assertion"},{"claim_id":"c-2","claim_class":"author_assertion"},{"claim_id":"c-3","claim_class":"author_assertion"},{"claim_id":"c-4","claim_class":"author_assertion"},{"claim_id":"c-5","claim_class":"author_assertion"},{"claim_id":"c-6","claim_class":"author_assertion"},{"claim_id":"c-7","claim_class":"author_assertion"}] R08: [{"claim_id":"c-1","citations":[]},{"claim_id":"c-2","citations":[]},{"claim_id":"c-3","citations":[]},{"claim_id":"c-4","citations":[]},{"claim_id":"c-5","citations":[]},{"claim_id":"c-6","citations":[]},{"claim_id":"c-7","citations":[]}] R09: When your words reach the end of their retention period they are destroyed, on the schedule above. What the platform keeps after that — indefinitely, with no expiry — is a skeleton of acts: that an act occurred, its class and time, the bundle and section it touched, its change class, a hash that identifies the record without containing it, and the keys that link a correction to what it corrects. The skeleton is not your words and cannot reproduce them. Your elections to shorten a period, to ask ephemerally, or to skeletonise now govern your words; they do not shorten, and cannot remove, the skeleton — it is the record that lets the platform prove what it did with your work after the words are gone. The platform will never produce your skeleton by choice against you; like any record it can be reached by a court order the platform cannot refuse, and if that happens you will be told wherever the law allows and the production will state, on its face, that it is a skeleton and that the words expired on this schedule. R10: When your words reach the end of their retention period they are destroyed, on the schedule above. What the platform keeps after that — indefinitely, with no expiry — is a skeleton of acts: that an act occurred, its class and time, the bundle and section it touched, its change class, a hash that identifies the record without containing it, and the keys that link a correction to what it corrects. The skeleton is not your words and cannot reproduce them. Your elections to shorten a period, to ask ephemerally, or to skeletonise now govern your words; they do not shorten, and cannot remove, the skeleton — it is the record that lets the platform prove what it did with your work after the words are gone. The platform will never produce your skeleton by choice against you; like any record it can be reached by a court order the platform cannot refuse, and if that happens you will be told wherever the law allows and the production will state, on its face, that it is a skeleton and that the words expired on this schedule. R12: 84153e3b7a4441ce097574d2f33da9fe4635fb4afd8c0274a142aa42d44c973f R16: {"canonical_url":"/blog/posts/post-your-codebase-has-a-tech-tree-too-eecca9","version_url":"/blog/posts/post-your-codebase-has-a-tech-tree-too-eecca9/versions/post-your-codebase-has-a-tech-tree-too-eecca9-v1"} R18: opted_in