HN 提问：功能上线后，你们是如何处理学到的知识的？
3 分•作者: gaggle_dk•4 个月前
在我编程的第二个十年即将到来之际，我越来越注意到我们经常会踩到同一个“雷”。一个改动导致了问题的发生，事后看来，我们其实早就掌握了可以避免它的信息，只是从未将其显现出来。又或者，我们上线了一个功能，却从未回头去检查它是否按照我们的预期被使用，于是我们继续基于同样的未经检验的假设开发更多功能。
这是否让你产生共鸣？我相当确定我们都会遇到这种情况，但我无法判断有多少人认为这是一种可以修复的模式，而不是工作的一部分。
* 当你完成一个功能或项目后，你所学到的东西最终去了哪里？是你脑子里，一个问题评论，一份文档或维基，一次回顾会议，还是其他地方？
* 当你开始一项新工作时，你会明确地引入过去的学习成果吗？比如复制、链接、引用、讨论？还是这一切都来自于共享的记忆？
* 你有没有一个例子，早点记住某件事本可以为你节省大量时间？发生了什么？
我试图弄清楚这是一种普遍的痛苦，还是仅仅我个人的困扰。非常欢迎分享你的“战争故事”。
查看原文
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.