[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-when-to-pair-zh-CN":3,"blog-related-when-to-pair-zh-CN":29,"blog-adjacent-when-to-pair-zh-CN":62},{"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":28},99,"when-to-pair","什么时候需要结对编程","结对很贵，两个人干一个人的活。所以只在特定的时候用。","\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>","","blue","佳益方圆团队","2026-06-13T11:10:00+08:00",1,false,[16,17,18],"团队文化","结对编程","协作",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":10,"kind":26,"sortOrder":27,"count":21},4,0,"team-culture","团队动态","公司活动、技术分享、团建与招聘文化，了解佳益方圆团队的日常。","users","article",30,{},[30,40,51],{"id":31,"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},89,"thirty-minute-weekly","每周三十分钟的技术分享会","不讲新技术，不讲行业趋势，只讲这周踩过的坑和解决方式。","2026-10-11T09:00:00+08:00",[16,37,38],"技术分享","成长",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":10,"kind":26,"sortOrder":27,"count":21},{"id":41,"slug":42,"title":43,"excerpt":44,"content":9,"cover":9,"tone":45,"author":11,"publishedAt":46,"updatedAt":46,"readingMinutes":13,"featured":14,"tags":47,"category":50},90,"what-code-review-is-for","代码评审是为了什么","评审不是找错，是让另一个人的脑子过一遍你的代码。","cyan","2026-09-29T10:13:00+08:00",[16,48,49],"代码评审","工程实践",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":10,"kind":26,"sortOrder":27,"count":21},{"id":52,"slug":53,"title":54,"excerpt":55,"content":9,"cover":9,"tone":56,"author":11,"publishedAt":57,"updatedAt":57,"readingMinutes":13,"featured":14,"tags":58,"category":61},91,"docs-start-with-templates","文档从模板开始","没人愿意写文档，多半是因为不知道从哪写起。一张模板能解决大半问题。","teal","2026-09-17T11:26:00+08:00",[16,59,60],"文档","知识管理",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":10,"kind":26,"sortOrder":27,"count":21},{"previous":63,"next":81},{"id":64,"slug":65,"title":66,"excerpt":67,"content":9,"cover":9,"tone":68,"author":11,"publishedAt":69,"updatedAt":69,"readingMinutes":13,"featured":14,"tags":70,"category":74},80,"database-pool-outage","上线故障复盘：一次数据库连接耗尽","系统在周一早上九点全面不可用，根因是一个没有被关闭的数据库连接。","slate","2026-06-15T11:10:00+08:00",[71,72,73],"复盘","故障","数据库",{"id":75,"parentId":21,"slug":76,"name":77,"description":78,"icon":79,"cover":9,"tone":10,"kind":26,"sortOrder":80,"count":21},3,"project-retrospective","项目复盘","从 0 到 1 的真实项目记录，完整呈现问题、方案、踩坑经验与最终结果。","clipboard-check",40,{"id":82,"slug":83,"title":84,"excerpt":85,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":86,"updatedAt":86,"readingMinutes":13,"featured":14,"tags":87,"category":91},118,"after-saas-retreat","SaaS 退潮之后，企业怎么选","订阅制热度回落，企业的采购逻辑回归务实：看总成本，看数据归属。","2026-06-11T11:10:00+08:00",[88,89,90],"行业观察","SaaS","采购",{"id":92,"parentId":21,"slug":93,"name":88,"description":94,"icon":95,"cover":9,"tone":10,"kind":26,"sortOrder":96,"count":21},5,"industry-watch","对互联网、软件与数字化行业趋势的深度分析，输出团队自己的判断。","globe",20]