[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-tech-sharing-day-en":3,"blog-related-tech-sharing-day-en":29,"blog-adjacent-tech-sharing-day-en":61},{"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},94,"tech-sharing-day","A Quarterly Tech Sharing Day","Thirty minutes a week is not always enough, so we take half a day, mute notifications and talk shop properly.","\u003Cp>Weekly shares capture daily lessons, but some topics need room: a full architecture refactor, a tooling comparison. This year we started a quarterly half-day sharing session with everyone attending and no client meetings that day.\u003C\u002Fp>\n\u003Ch2>How the day runs\u003C\u002Fh2>\n\u003Cp>Topics are voted by the team, usually three: one engineering practice, one deep project review, one open discussion.\u003C\u002Fp>\n\u003Cp>Each speaker gets forty minutes plus twenty for questions, and must prepare a working demo. Running code persuades better than slides.\u003C\u002Fp>\n\u003Cp>Notifications are muted for the day, with only the on-call phone handling production issues.\u003C\u002Fp>\n\u003Ch2>A lesson from the first one\u003C\u002Fh2>\n\u003Cp>We originally scheduled six topics from morning to evening; the last two had almost no audience.\u003C\u002Fp>\n\u003Cp>Three topics with a tea break in between is the right size, leaving room for informal exchange.\u003C\u002Fp>\n\u003Cp>Materials are archived in the knowledge base so absentees can catch up.\u003C\u002Fp>\n\u003Cp>A sharing day is an investment of team time, not an extra burden. Half a day of focus smooths months of collaboration.\u003C\u002Fp>","","blue","佳益方圆团队","2026-08-12T14:05:00+08:00",1,false,[16,17,18],"Team Culture","Knowledge Sharing","Organisation",{"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,39,50],{"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":38},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,17,37],"Growth",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":10,"kind":26,"sortOrder":27,"count":21},{"id":40,"slug":41,"title":42,"excerpt":43,"content":9,"cover":9,"tone":44,"author":11,"publishedAt":45,"updatedAt":45,"readingMinutes":13,"featured":14,"tags":46,"category":49},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,47,48],"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":51,"slug":52,"title":53,"excerpt":54,"content":9,"cover":9,"tone":55,"author":11,"publishedAt":56,"updatedAt":56,"readingMinutes":13,"featured":14,"tags":57,"category":60},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,58,59],"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},{"previous":62,"next":79},{"id":63,"slug":64,"title":65,"excerpt":66,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":67,"updatedAt":67,"readingMinutes":13,"featured":14,"tags":68,"category":72},75,"dashboard-adoption-retro","Retrospective: A Dashboard Nobody Opened","The dashboard looked great and leadership applauded. Three months later its open rate was close to zero.","2026-08-14T14:05:00+08:00",[69,70,71],"Retrospective","Dashboard","Retail",{"id":73,"parentId":21,"slug":74,"name":75,"description":76,"icon":77,"cover":9,"tone":10,"kind":26,"sortOrder":78,"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":80,"slug":81,"title":82,"excerpt":83,"content":9,"cover":9,"tone":84,"author":11,"publishedAt":85,"updatedAt":85,"readingMinutes":13,"featured":14,"tags":86,"category":90},113,"xinchuang-adapter-cost","The Real Cost of Xinchuang Adaptation","Migrating to domestic hardware and software costs more than the quote; half of it hides in details.","slate","2026-08-10T14:05:00+08:00",[87,88,89],"Industry Watch","Xinchuang","Migration",{"id":91,"parentId":21,"slug":92,"name":87,"description":93,"icon":94,"cover":9,"tone":10,"kind":26,"sortOrder":95,"count":21},5,"industry-watch","In-depth analysis of internet, software and digital industry trends with our own point of view.","globe",20]