[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-first-month-onboarding-en":3,"blog-related-first-month-onboarding-en":30,"blog-adjacent-first-month-onboarding-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":29},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.","\u003Cp>We have onboarded many people. The strongest shipped in week one; the slowest started after a month. Looking back, the difference tracked the onboarding plan far more than ability. Our process is much clearer than five years ago.\u003C\u002Fp>\n\u003Ch2>Week one\u003C\u002Fh2>\n\u003Cp>Day one has two tasks only: get every account and permission, and learn everyone's name and role.\u003C\u002Fp>\n\u003Cp>The first two days are for running the project: local environment, database, deploy scripts. Newcomers fix outdated docs directly, which beats making veterans rewrite them.\u003C\u002Fp>\n\u003Cp>Assign a mentor who explicitly welcomes questions every day, without limit.\u003C\u002Fp>\n\u003Ch2>Goals for the month\u003C\u002Fh2>\n\u003Cp>The first real task is small: a medium bug or a small component that ships within a week.\u003C\u002Fp>\n\u003Cp>Walk through each deploy and review together once; familiarity makes everything faster after.\u003C\u002Fp>\n\u003Cp>End the month with half an hour: where they got stuck, which docs confused them, where the mentor fell short.\u003C\u002Fp>\n\u003Cp>How fast newcomers settle reflects the team's organisational skill, not their own. Treat onboarding as a project and it pays back directly.\u003C\u002Fp>","","indigo","佳益方圆团队","2026-09-05T12:39:00+08:00",1,false,[16,17,18],"Team Culture","Onboarding","Mentoring",{"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,{},[31,41,52],{"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":40},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,38,39],"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":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},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,49,50],"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":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},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,60,61],"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},{"previous":64,"next":81},{"id":65,"slug":66,"title":67,"excerpt":68,"content":9,"cover":9,"tone":26,"author":11,"publishedAt":69,"updatedAt":69,"readingMinutes":13,"featured":14,"tags":70,"category":74},73,"miniapp-launch-retro","Retrospective: Launch Day Is Not the Finish Line","Users arrived on launch day and so did the problems. We now include post-launch operations in scope.","2026-09-07T12:39:00+08:00",[71,72,73],"Retrospective","Mini Program","Operations",{"id":75,"parentId":21,"slug":76,"name":77,"description":78,"icon":79,"cover":9,"tone":26,"kind":27,"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":90},5,"ai-assist-enterprise-software","AI in Enterprise Software: Start by Removing Repetitive Work","Enterprise scenarios do not need a chatty AI. They need an assistant that reliably shares repetitive work and whose results can be traced.","2026-09-04T09:30:00+08:00","2026-10-18T15:58:14.704+08:00",[89,50],"AI Applications",{"id":13,"parentId":21,"slug":91,"name":92,"description":93,"icon":94,"cover":9,"tone":26,"kind":27,"sortOrder":95,"count":21},"engineering","Engineering","Hands-on engineering practices in architecture, performance optimization, AI integration and cross-platform delivery from our R and D team.","cpu",60]