[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-thirty-minute-weekly-en":3,"blog-related-thirty-minute-weekly-en":29,"blog-adjacent-thirty-minute-weekly-en":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","The Thirty-Minute Weekly Share","No new technology, no industry trends. Just the pitfalls of the week and how they were solved.","\u003Cp>Three years ago we started reserving thirty minutes on Friday afternoons for one person to present a concrete problem from that week's work. No slides required, no scoring, followed by open discussion. It has become the fastest-growing mechanism in our team.\u003C\u002Fp>\n\u003Ch2>Only three rules\u003C\u002Fh2>\n\u003Cp>Present only firsthand experience, not articles you read. Secondhand stories lack detail; the value lies in the review.\u003C\u002Fp>\n\u003Cp>Answer three questions: what happened, why, and how to avoid it next time. Twenty minutes to present, ten to discuss.\u003C\u002Fp>\n\u003Cp>Nothing needs to be profound. A talk about a naming misunderstanding can be as useful as one about architecture.\u003C\u002Fp>\n\u003Ch2>What changed\u003C\u002Fh2>\n\u003Cp>The same mistakes repeat far less often. One person's pitfall becomes everyone's knowledge.\u003C\u002Fp>\n\u003Cp>Newcomers speak up. Thirty minutes is low pressure, and the first talk makes later communication easier.\u003C\u002Fp>\n\u003Cp>Material accumulates. Many blog posts and internal documents started as a weekly share.\u003C\u002Fp>\n\u003Cp>Teams grow through frequent, low-friction steps rather than a single big training. Thirty minutes goes further than expected.\u003C\u002Fp>","","blue","佳益方圆团队","2026-10-11T09:00:00+08:00",1,false,[16,17,18],"Team Culture","Knowledge Sharing","Growth",{"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","Team and Culture","Company events, tech sharing, team building and hiring culture that show the daily life of the Jiayifangyuan team.","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","What Code Review Is Really For","Review is not fault-finding. It is letting another mind walk through your code.","cyan","2026-09-29T10:13:00+08:00",[16,38,39],"Code Review","Engineering Practice",{"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","Documents Start With Templates","People avoid writing docs mostly because they do not know where to start. A template solves most of it.","teal","2026-09-17T11:26:00+08:00",[16,49,50],"Documentation","Knowledge Management",{"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","The Newcomer's First Month","The goal of month one is not output; it is knowing who to ask when stuck.","indigo","2026-09-05T12:39:00+08:00",[16,60,61],"Onboarding","Mentoring",{"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","Retrospective: Why Acceptance Took Half a Year","The system was live for months while acceptance stalled. The causes were documents, process and communication, not software.","2026-10-13T09:00:00+08:00",[71,72,73],"Retrospective","Government","Acceptance",{"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","Project Retrospectives","Real project records from zero to one, covering problems, solutions, lessons learned and final outcomes.","clipboard-check",40,{"id":82,"slug":83,"title":84,"excerpt":85,"content":9,"cover":9,"tone":57,"author":11,"publishedAt":86,"updatedAt":87,"readingMinutes":13,"featured":14,"tags":88,"category":91},2,"vertical-product-rules","The Watershed for Vertical Products: Writing Industry Defaults into the System","Vertical is not a new industry label on a generic product. The real barrier is understanding and carrying the default rules that practitioners take for granted.","2026-10-09T10:00:00+08:00","2026-10-18T15:58:14.661+08:00",[89,90],"Industry Products","Product Design",{"id":82,"parentId":21,"slug":92,"name":93,"description":94,"icon":95,"cover":9,"tone":10,"kind":26,"sortOrder":96,"count":21},"product-thinking","Product Thinking","Requirement analysis, user experience and product design methods, plus the thinking from business problems to product solutions.","lightbulb",50]