[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-what-code-review-is-for-en":3,"blog-related-what-code-review-is-for-en":30,"blog-adjacent-what-code-review-is-for-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},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.","\u003Cp>In our early days review meant nitpicking: bad names here, shorter code there. People submitted nervously, and review became adversarial. Only after we changed the focus did it start working.\u003C\u002Fp>\n\u003Ch2>Ask the right questions first\u003C\u002Fh2>\n\u003Cp>Does this code solve the actual problem? A misread requirement matters far more than style.\u003C\u002Fp>\n\u003Cp>Are the edges covered? Nulls, concurrency, permissions, retries are where production incidents come from.\u003C\u002Fp>\n\u003Cp>Can the next person understand it? Six-months-later you counts as the next person.\u003C\u002Fp>\n\u003Ch2>What review should not be\u003C\u002Fh2>\n\u003Cp>Debating indentation and brackets. Formatting belongs to tools, not people.\u003C\u002Fp>\n\u003Cp>Demanding the author rewrite it in the reviewer's style. If it is correct and readable, stylistic differences can stay.\u003C\u002Fp>\n\u003Cp>Attacking competence in public comments. Be strict about code, respectful to people.\u003C\u002Fp>\n\u003Cp>The goal of review is not code the reviewer likes, but code that stands up in someone else's eyes.\u003C\u002Fp>","","cyan","佳益方圆团队","2026-09-29T10:13:00+08:00",1,false,[16,17,18],"Team Culture","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},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},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":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},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":26,"kind":27,"sortOrder":28,"count":21},{"previous":64,"next":81},{"id":65,"slug":66,"title":67,"excerpt":68,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":69,"updatedAt":69,"readingMinutes":13,"featured":14,"tags":70,"category":74},71,"mes-integration-retro","Retrospective: Integrating ERP With MES","The hard part of integration is not the interface, but getting two departments to agree on what a field means.","2026-10-01T10:13:00+08:00",[71,72,73],"Retrospective","Manufacturing","Integration",{"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":26,"author":11,"publishedAt":86,"updatedAt":86,"readingMinutes":13,"featured":14,"tags":87,"category":91},109,"local-software-budget","Two New Trends in Local Software Budgets","Totals are flat, but the way money is spent has changed: fewer big one-off projects, more sustained investment.","2026-09-27T10:13:00+08:00",[88,89,90],"Industry Watch","Budget","IT Strategy",{"id":92,"parentId":21,"slug":93,"name":88,"description":94,"icon":95,"cover":9,"tone":26,"kind":27,"sortOrder":96,"count":21},5,"industry-watch","In-depth analysis of internet, software and digital industry trends with our own point of view.","globe",20]