请问HN：团队是如何记住基础设施决策背后的原因的？
在我曾合作过的团队中，我们常常遇到这样的情况：系统中有些配置、服务或架构选择的原因无人知晓。文档过时，Slack 聊天记录杂乱无章，而做出这些决策的人往往已经离开。当系统出现故障时，我们不得不一次又一次地重新发现相同的背景信息。这是长久存在的系统中不可避免的现象吗？还是说经验丰富的团队有更好的方法来保留这些背景信息？
查看原文
On teams I’ve worked with, we often run into systems where nobody really knows why certain configs, services, or architectural choices exist. Docs are outdated, Slack history is messy, and the people who made the decision are often gone. When something breaks, we end up rediscovering the same context over and over.
Is this just inevitable on long-lived systems, or do experienced teams have a better way of preserving this kind of context?