[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-remote-work-boundaries-zh-CN":3,"blog-related-remote-work-boundaries-zh-CN":30,"blog-adjacent-remote-work-boundaries-zh-CN":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},93,"remote-work-boundaries","远程协作的边界","远程办公的难点不是沟通工具，而是把\"随时在线\"变成\"各有时段\"。","\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>","","slate","佳益方圆团队","2026-08-24T13:52: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,{},[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","每周三十分钟的技术分享会","不讲新技术，不讲行业趋势，只讲这周踩过的坑和解决方式。","2026-10-11T09:00:00+08:00",[16,38,39],"技术分享","成长",{"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","代码评审是为了什么","评审不是找错，是让另一个人的脑子过一遍你的代码。","cyan","2026-09-29T10:13:00+08:00",[16,49,50],"代码评审","工程实践",{"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","文档从模板开始","没人愿意写文档，多半是因为不知道从哪写起。一张模板能解决大半问题。","teal","2026-09-17T11:26:00+08:00",[16,60,61],"文档","知识管理",{"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},74,"multi-vendor-integration","系统集成项目复盘：三家供应商一台戏","多方协作的项目里，最贵的成本是等待和扯皮，而不是开发。","2026-08-26T13:52:00+08:00",[71,72,73],"复盘","集成","多方协作",{"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","项目复盘","从 0 到 1 的真实项目记录，完整呈现问题、方案、踩坑经验与最终结果。","clipboard-check",40,{"id":82,"slug":83,"title":84,"excerpt":85,"content":9,"cover":9,"tone":57,"author":11,"publishedAt":86,"updatedAt":86,"readingMinutes":13,"featured":14,"tags":87,"category":91},112,"low-code-vs-custom","低代码与定制开发的边界","低代码不是万能的，也不是玩具。关键是知道哪些事该交给它，哪些不该。","2026-08-22T13:52:00+08:00",[88,89,90],"行业观察","低代码","技术选型",{"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","对互联网、软件与数字化行业趋势的深度分析，输出团队自己的判断。","globe",20]