[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-useful-annual-review-zh-CN":3,"blog-adjacent-useful-annual-review-zh-CN":30,"blog-related-useful-annual-review-zh-CN":65},{"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},106,"useful-annual-review","一份有用的年度总结","年度总结不该是流水账，而应该回答一个问题：这一年你哪里变强了。","\u003Cp>看了很多年的年度总结，大多是项目列表：参与了哪些项目、获得了什么成绩。这样的总结对个人成长帮助有限。我们逐渐摸索出一个更有用的结构，每位同事按这个结构写。\u003C\u002Fp>\n\u003Ch2>总结的四个部分\u003C\u002Fh2>\n\u003Cp>做成了什么：不超过五件事，写清结果和影响，不是过程。\u003C\u002Fp>\n\u003Cp>学会了什么：技能、方法或视角上的具体变化，最好配一个例子。\u003C\u002Fp>\n\u003Cp>犯了哪些错：至少写一件，写清代价与改进。不写错误，说明还没开始反思。\u003C\u002Fp>\n\u003Cp>明年想成为什么样：具体到一个能力或角色，越具体越可执行。\u003C\u002Fp>\n\u003Ch2>主管怎么用这份总结\u003C\u002Fh2>\n\u003Cp>逐份阅读，面谈时围绕第三部分和第四部分讨论，而不是业绩数字。\u003C\u002Fp>\n\u003Cp>把共性诉求汇总到团队计划：比如多人提到想学架构，就安排对应的分享与项目机会。\u003C\u002Fp>\n\u003Cp>总结存档，明年写的时候先翻出上一年的，看兑现了多少。\u003C\u002Fp>\n\u003Cp>年度总结的价值不在回顾，而在决定接下来把时间投给什么。写的时候诚实一点，它就值得花那几个小时。\u003C\u002Fp>","","teal","佳益方圆团队","2026-03-21T10:41:00+08:00",1,false,[16,17,18],"团队文化","年度总结","成长",{"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","团队动态","公司活动、技术分享、团建与招聘文化，了解佳益方圆团队的日常。","users","blue","article",30,{},{"previous":31,"next":49},{"id":32,"slug":33,"title":34,"excerpt":35,"content":9,"cover":9,"tone":36,"author":11,"publishedAt":37,"updatedAt":37,"readingMinutes":13,"featured":14,"tags":38,"category":42},87,"multilingual-site-retro","多语言站点复盘：翻译不是复制粘贴","英文站上线后，海外客户反馈看不懂，问题不在语言，而在内容直接照搬。","indigo","2026-03-23T10:41:00+08:00",[39,40,41],"复盘","多语言","外贸",{"id":43,"parentId":21,"slug":44,"name":45,"description":46,"icon":47,"cover":9,"tone":26,"kind":27,"sortOrder":48,"count":21},3,"project-retrospective","项目复盘","从 0 到 1 的真实项目记录，完整呈现问题、方案、踩坑经验与最终结果。","clipboard-check",40,{"id":50,"slug":51,"title":52,"excerpt":53,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":54,"updatedAt":54,"readingMinutes":13,"featured":14,"tags":55,"category":59},125,"edtech-procurement","教育采购的观察：需求方说不出需求","学校采购软件，最大的难题不是预算，而是把真实需求讲清楚。","2026-03-19T10:41:00+08:00",[56,57,58],"行业观察","教育","采购",{"id":60,"parentId":21,"slug":61,"name":56,"description":62,"icon":63,"cover":9,"tone":26,"kind":27,"sortOrder":64,"count":21},5,"industry-watch","对互联网、软件与数字化行业趋势的深度分析，输出团队自己的判断。","globe",20,[66,75,86],{"id":67,"slug":68,"title":69,"excerpt":70,"content":9,"cover":9,"tone":26,"author":11,"publishedAt":71,"updatedAt":71,"readingMinutes":13,"featured":14,"tags":72,"category":74},89,"thirty-minute-weekly","每周三十分钟的技术分享会","不讲新技术，不讲行业趋势，只讲这周踩过的坑和解决方式。","2026-10-11T09:00:00+08:00",[16,73,18],"技术分享",{"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","代码评审是为了什么","评审不是找错，是让另一个人的脑子过一遍你的代码。","cyan","2026-09-29T10:13:00+08:00",[16,83,84],"代码评审","工程实践",{"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":10,"author":11,"publishedAt":91,"updatedAt":91,"readingMinutes":13,"featured":14,"tags":92,"category":95},91,"docs-start-with-templates","文档从模板开始","没人愿意写文档，多半是因为不知道从哪写起。一张模板能解决大半问题。","2026-09-17T11:26:00+08:00",[16,93,94],"文档","知识管理",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21}]