请问HN：你是如何找到旧代码决策背后的“原因”的？
好奇团队在实际操作中是如何处理这个问题的。<p>当你在修改现有代码时，需要了解某个决策背后的原因：<p>你首先会查看哪里？<p>你有多频繁找不到明确的答案？<p>当原作者不在时，你会怎么做？<p>最近我遇到这个问题的频率越来越高——翻阅拉取请求、Slack 讨论串和半成品文档，只为了拼凑出上下文。我在想，这在各个团队中究竟有多普遍。
查看原文
Curious how teams actually handle this in practice.<p>When you’re modifying existing code and need to understand why a decision was made:<p>Where do you look first?<p>How often do you fail to find a clear answer?<p>What do you do when the original author is gone?<p>I’ve been running into this more often lately --digging through PRs, Slack threads, and half-written docs just to piece together context, and I’m wondering how common this really is across teams.