问HN：在你发布一个功能后，你所学到的知识会发生什么？
即将进入我编程的第二个十年，我不断注意到我们常常踩到同一个钉子上。一次变更导致了某些问题，而回过头来看，我们其实早就有信息可以防止这种情况，只是从未将其提取出来。或者我们发布了一个功能，却从未回头检查它是否按照我们预期的方式被使用，因此我们在同样未经验证的假设上不断推出更多功能。
这是否引起了你的共鸣？我相当确定我们都经历过这种情况，但我无法判断有多少人将其视为一个可以修复的模式，而不是工作的一部分。
- 当你完成一个功能或项目后，你所学到的东西到底去了哪里？是留在你的脑海里、写在问题评论中、文档或维基上、回顾会议中，还是其他地方？
- 当你开始新的工作时，你是否会明确地引入过去的经验教训，比如复制、链接、引用或讨论它？还是完全依赖于共同的记忆？
- 有没有一个例子，回想起早些时候的某些事情本可以为你节省真正的时间？发生了什么？
我在试图弄清楚这是否是一个共同的痛点，还是仅仅是我一个人的感受。欢迎分享你的经历。
查看原文
Closing in on my second decade of programming, and I keep noticing how often we step on the same rake. A change breaks something, and in hindsight we already had the information to prevent it, we just never surfaced it. Or we ship a feature and never circle back to check whether it's used the way we intended, so we keep shipping more on the same untested assumptions.<p>Does this resonate? I'm fairly sure we all hit this, but I can't tell how many people see it as a fixable pattern versus just part of the job.<p>- After you finish a feature or project, where does what you learned actually go? Is it your head, an issue comment, a doc or wiki, a retro, somewhere else?<p>- When you start something new, do you explicitly pull in past learnings, like copy, link, reference, discuss it? Or is it all from shared memory?<p>- Got an example where remembering something earlier would have saved you real time? What happened?<p>Trying to work out whether this is a shared pain or just mine. War stories very welcome.