[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-reading-club-two-years-en":3,"blog-adjacent-reading-club-two-years-en":30,"blog-related-reading-club-two-years-en":64},{"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},103,"reading-club-two-years","Two Years of a Reading Club","One technical book a month, twenty-four in two years. The biggest takeaway was not in the books.","\u003Cp>Two years ago the team started a reading club: one technical or management book a month, each person reads part, and we talk for an hour at month's end. It nearly died several times; we adjusted and it survives.\u003C\u002Fp>\n\u003Ch2>How it survived\u003C\u002Fh2>\n\u003Cp>Everyone reads one chapter only. Requiring whole books means most people stall in week two.\u003C\u002Fp>\n\u003Cp>Shares are not summaries. Each person brings one useful idea tied to a project example.\u003C\u002Fp>\n\u003Cp>Book choice is loose: technical, management, industry reports, anything, but never a mandatory title.\u003C\u002Fp>\n\u003Ch2>The real gains\u003C\u002Fh2>\n\u003Cp>A shared vocabulary. Discussing designs, people cite the same concepts and communication gets cheaper.\u003C\u002Fp>\n\u003Cp>Sustained input. Daily work converges on one track; the club forces a monthly step outside.\u003C\u002Fp>\n\u003Cp>Discovering interests. Someone pivoted after one book and later led our work in that area.\u003C\u002Fp>\n\u003Cp>The club is not knowledge transfer but a monthly reason to sit down and think together. That reason is worth more than the books.\u003C\u002Fp>","","slate","佳益方圆团队","2026-04-26T15:02:00+08:00",1,false,[16,17,18],"Team Culture","Reading Club","Learning",{"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","Team and Culture","Company events, tech sharing, team building and hiring culture that show the daily life of the Jiayifangyuan team.","users","blue","article",30,{},{"previous":31,"next":48},{"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":41},84,"outsourcing-visibility","Retrospective: Visibility Beats Promises in Outsourcing","The vendor said nearly done every week, until a week before delivery revealed half the work was missing.","2026-04-28T15:02:00+08:00",[38,39,40],"Retrospective","Outsourcing","Delivery",{"id":42,"parentId":21,"slug":43,"name":44,"description":45,"icon":46,"cover":9,"tone":26,"kind":27,"sortOrder":47,"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":49,"slug":50,"title":51,"excerpt":52,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":53,"updatedAt":53,"readingMinutes":13,"featured":14,"tags":54,"category":58},122,"digital-budget-planning","Digital Budgeting Without Waste","Misallocated budgets waste even the best systems. Some allocation lessons from practice.","2026-04-24T15:02:00+08:00",[55,56,57],"Industry Watch","Budget","Digitalisation",{"id":59,"parentId":21,"slug":60,"name":55,"description":61,"icon":62,"cover":9,"tone":26,"kind":27,"sortOrder":63,"count":21},5,"industry-watch","In-depth analysis of internet, software and digital industry trends with our own point of view.","globe",20,[65,75,86],{"id":66,"slug":67,"title":68,"excerpt":69,"content":9,"cover":9,"tone":26,"author":11,"publishedAt":70,"updatedAt":70,"readingMinutes":13,"featured":14,"tags":71,"category":74},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.","2026-10-11T09:00:00+08:00",[16,72,73],"Knowledge Sharing","Growth",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"id":76,"slug":77,"title":78,"excerpt":79,"content":9,"cover":9,"tone":80,"author":11,"publishedAt":81,"updatedAt":81,"readingMinutes":13,"featured":14,"tags":82,"category":85},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,83,84],"Code Review","Engineering Practice",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"id":87,"slug":88,"title":89,"excerpt":90,"content":9,"cover":9,"tone":91,"author":11,"publishedAt":92,"updatedAt":92,"readingMinutes":13,"featured":14,"tags":93,"category":96},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,94,95],"Documentation","Knowledge Management",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21}]