[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-thirty-minute-weekly-zh-CN":3,"blog-related-thirty-minute-weekly-zh-CN":29,"blog-adjacent-thirty-minute-weekly-zh-CN":63},{"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},89,"thirty-minute-weekly","每周三十分钟的技术分享会","不讲新技术，不讲行业趋势，只讲这周踩过的坑和解决方式。","\u003Cp>我们从三年前开始，每周五下午留三十分钟，由一个人讲一件这周工作中遇到的具体问题。没有 PPT 要求，没有考核，讲完大家一起讨论。这件事坚持下来，成了团队成长最快的机制。\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-10-11T09:00: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,41,52],{"id":31,"slug":32,"title":33,"excerpt":34,"content":9,"cover":9,"tone":35,"author":11,"publishedAt":36,"updatedAt":36,"readingMinutes":13,"featured":14,"tags":37,"category":40},90,"what-code-review-is-for","代码评审是为了什么","评审不是找错，是让另一个人的脑子过一遍你的代码。","cyan","2026-09-29T10:13:00+08:00",[16,38,39],"代码评审","工程实践",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":10,"kind":26,"sortOrder":27,"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},91,"docs-start-with-templates","文档从模板开始","没人愿意写文档，多半是因为不知道从哪写起。一张模板能解决大半问题。","teal","2026-09-17T11:26:00+08:00",[16,49,50],"文档","知识管理",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":10,"kind":26,"sortOrder":27,"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":62},92,"first-month-onboarding","新人第一个月怎么过","第一个月的目标不是产出，而是让新人知道遇到问题该找谁。","indigo","2026-09-05T12:39:00+08:00",[16,60,61],"入职","带新人",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":10,"kind":26,"sortOrder":27,"count":21},{"previous":64,"next":81},{"id":65,"slug":66,"title":67,"excerpt":68,"content":9,"cover":9,"tone":57,"author":11,"publishedAt":69,"updatedAt":69,"readingMinutes":13,"featured":14,"tags":70,"category":74},70,"gov-project-acceptance","政务项目复盘：验收为什么拖了半年","功能早已上线，验收却迟迟没有完成。问题往往不在系统，而在文档、流程和沟通节奏。","2026-10-13T09:00: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":57,"author":11,"publishedAt":86,"updatedAt":87,"readingMinutes":82,"featured":14,"tags":88,"category":91},2,"vertical-product-rules","垂直行业产品的分水岭：把行业默认规则写进系统","垂直不是换一个行业名字。真正的门槛，是能否理解并承接那些从业者习以为常的默认规则。","2026-10-09T10:00:00+08:00","2026-10-18T15:58:14.661+08:00",[89,90],"行业产品","产品设计",{"id":82,"parentId":21,"slug":92,"name":93,"description":94,"icon":95,"cover":9,"tone":10,"kind":26,"sortOrder":96,"count":21},"product-thinking","产品思维","需求分析、用户体验与产品设计方法论，以及从业务问题到产品方案的思考过程。","lightbulb",50]