提问 HN：团队如何记住基础设施决策的缘由？
4 分•作者: curious_sre•6 个月前
在我参与的团队中，我们经常会遇到这样的系统：没人真正知道某些配置、服务或架构选择存在的原因。文档过时，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?