[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-docs-for-future-self-zh-CN":3,"blog-related-docs-for-future-self-zh-CN":30,"blog-adjacent-docs-for-future-self-zh-CN":59},{"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},66,"docs-for-future-self","产品文档写给未来的自己","文档不是交付物，而是团队的记忆。没人看的文档，通常是因为写错了对象。","\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>","","indigo","佳益方圆团队","2026-04-06T09:28: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},2,0,"product-thinking","产品思维","需求分析、用户体验与产品设计方法论，以及从业务问题到产品方案的思考过程。","lightbulb","blue","article",50,{},[31,40,50],{"id":28,"slug":32,"title":33,"excerpt":34,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":35,"updatedAt":35,"readingMinutes":13,"featured":14,"tags":36,"category":39},"grading-requirement-confidence","需求的真实度分级","把需求当成事实来做，是项目延期最常见的原因。需求其实有可信度高低之分。","2026-10-15T09:00:00+08:00",[37,18,38],"需求","风险管理",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"id":20,"slug":41,"title":42,"excerpt":43,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":44,"updatedAt":45,"readingMinutes":20,"featured":14,"tags":46,"category":49},"vertical-product-rules","垂直行业产品的分水岭：把行业默认规则写进系统","垂直不是换一个行业名字。真正的门槛，是能否理解并承接那些从业者习以为常的默认规则。","2026-10-09T10:00:00+08:00","2026-10-18T15:58:14.661+08:00",[47,48],"行业产品","产品设计",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"id":51,"slug":52,"title":53,"excerpt":54,"content":9,"cover":9,"tone":26,"author":11,"publishedAt":55,"updatedAt":55,"readingMinutes":13,"featured":14,"tags":56,"category":58},51,"mvp-boundary","MVP 的边界怎么划","最小可用不是功能最少，而是能完整跑通一条业务闭环。","2026-10-03T10:13:00+08:00",[57,18,37],"MVP",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"previous":60,"next":76},{"id":61,"slug":62,"title":63,"excerpt":64,"content":9,"cover":9,"tone":26,"author":11,"publishedAt":65,"updatedAt":65,"readingMinutes":13,"featured":14,"tags":66,"category":70},46,"api-rate-limiting","接口限流：先保护自己再谈体验","限流不是为了拦用户，而是为了让系统在异常流量下还能服务大多数人。","2026-04-08T09:28:00+08:00",[67,68,69],"接口","稳定性","运维",{"id":13,"parentId":21,"slug":71,"name":72,"description":73,"icon":74,"cover":9,"tone":26,"kind":27,"sortOrder":75,"count":21},"engineering","技术专栏","架构设计、性能优化、AI 集成与跨端方案等一线技术实践，由研发团队持续分享。","cpu",60,{"id":77,"slug":78,"title":79,"excerpt":80,"content":9,"cover":9,"tone":81,"author":11,"publishedAt":82,"updatedAt":82,"readingMinutes":13,"featured":14,"tags":83,"category":87},86,"peak-traffic-preparation","大促保障复盘：活动前夜的扩容","活动页面做了压力测试，但真正被打挂的是登录接口和优惠券服务。","teal","2026-04-04T09:28:00+08:00",[84,85,86],"复盘","大促","性能",{"id":88,"parentId":21,"slug":89,"name":90,"description":91,"icon":92,"cover":9,"tone":26,"kind":27,"sortOrder":93,"count":21},3,"project-retrospective","项目复盘","从 0 到 1 的真实项目记录，完整呈现问题、方案、踩坑经验与最终结果。","clipboard-check",40]