[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-knowledge-base-habit-zh-CN":3,"blog-related-knowledge-base-habit-zh-CN":30,"blog-adjacent-knowledge-base-habit-zh-CN":61},{"id":4,"slug":5,"title":6,"excerpt":7,"content":8,"cover":9,"tone":10,"author":11,"publishedAt":12,"updatedAt":12,"readingMinutes":13,"featured":14,"tags":15,"category":19,"seoSettings":29},98,"knowledge-base-habit","知识库是团队的习惯","知识库不是建好就有人用，而是每次遇到问题都先想到它，才算真的存在。","\u003Cp>我们买过好几个知识管理工具，前两个都荒废了，打开率一路下滑。现在这个用了三年还在活跃，区别不在工具，而在几个具体的习惯。\u003C\u002Fp>\n\u003Ch2>让写变得自然\u003C\u002Fh2>\n\u003Cp>搜不到答案时，解决问题的第一件事是建一篇文档，先写结论，再补细节。\u003C\u002Fp>\n\u003Cp>文档允许粗糙。一条命令、一段排查记录都可以，不要求文采。\u003C\u002Fp>\n\u003Cp>每次会议结束，主持人在五分钟内把决定和待办写进对应页面，不留到以后。\u003C\u002Fp>\n\u003Ch2>让读变得可靠\u003C\u002Fh2>\n\u003Cp>文档要有责任人。页面上直接显示最后更新人和日期，超过一年未更新的内容标记为待核实。\u003C\u002Fp>\n\u003Cp>讨论区不收决策。决策必须落到文档，聊天记录只作参考。\u003C\u002Fp>\n\u003Cp>新人入职的任务之一，就是把过时文档改对，改完在群里说一声。\u003C\u002Fp>\n\u003Cp>知识库的生命周期由使用频率决定。每个问题先从知识库开始找，它才配叫知识库。\u003C\u002Fp>","","slate","佳益方圆团队","2026-06-25T10:57:00+08:00",1,false,[16,17,18],"团队文化","知识管理","文档",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},4,0,"team-culture","团队动态","公司活动、技术分享、团建与招聘文化，了解佳益方圆团队的日常。","users","blue","article",30,{},[31,41,52],{"id":32,"slug":33,"title":34,"excerpt":35,"content":9,"cover":9,"tone":26,"author":11,"publishedAt":36,"updatedAt":36,"readingMinutes":13,"featured":14,"tags":37,"category":40},89,"thirty-minute-weekly","每周三十分钟的技术分享会","不讲新技术，不讲行业趋势，只讲这周踩过的坑和解决方式。","2026-10-11T09:00:00+08:00",[16,38,39],"技术分享","成长",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"id":42,"slug":43,"title":44,"excerpt":45,"content":9,"cover":9,"tone":46,"author":11,"publishedAt":47,"updatedAt":47,"readingMinutes":13,"featured":14,"tags":48,"category":51},90,"what-code-review-is-for","代码评审是为了什么","评审不是找错，是让另一个人的脑子过一遍你的代码。","cyan","2026-09-29T10:13:00+08:00",[16,49,50],"代码评审","工程实践",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"id":53,"slug":54,"title":55,"excerpt":56,"content":9,"cover":9,"tone":57,"author":11,"publishedAt":58,"updatedAt":58,"readingMinutes":13,"featured":14,"tags":59,"category":60},91,"docs-start-with-templates","文档从模板开始","没人愿意写文档，多半是因为不知道从哪写起。一张模板能解决大半问题。","teal","2026-09-17T11:26:00+08:00",[16,18,17],{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"previous":62,"next":80},{"id":63,"slug":64,"title":65,"excerpt":66,"content":9,"cover":9,"tone":67,"author":11,"publishedAt":68,"updatedAt":68,"readingMinutes":13,"featured":14,"tags":69,"category":73},79,"acceptance-dispute-retro","验收扯皮复盘：标准不清的代价","系统做完了，客户说“不是我们想要的”。所有争议最后都回到同一句话：当初没说清楚。","indigo","2026-06-27T10:57:00+08:00",[70,71,72],"复盘","验收","需求管理",{"id":74,"parentId":21,"slug":75,"name":76,"description":77,"icon":78,"cover":9,"tone":26,"kind":27,"sortOrder":79,"count":21},3,"project-retrospective","项目复盘","从 0 到 1 的真实项目记录，完整呈现问题、方案、踩坑经验与最终结果。","clipboard-check",40,{"id":81,"slug":82,"title":83,"excerpt":84,"content":9,"cover":9,"tone":57,"author":11,"publishedAt":85,"updatedAt":85,"readingMinutes":13,"featured":14,"tags":86,"category":90},117,"supply-chain-gap","供应链里的数字断层","每个企业都有自己的系统，连起来却处处是断点。","2026-06-23T10:57:00+08:00",[87,88,89],"行业观察","供应链","数字化",{"id":91,"parentId":21,"slug":92,"name":87,"description":93,"icon":94,"cover":9,"tone":26,"kind":27,"sortOrder":95,"count":21},5,"industry-watch","对互联网、软件与数字化行业趋势的深度分析，输出团队自己的判断。","globe",20]