[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-remote-work-boundaries-en":3,"blog-related-remote-work-boundaries-en":30,"blog-adjacent-remote-work-boundaries-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},93,"remote-work-boundaries","Boundaries in Remote Work","The hard part of remote work is not the tools; it is turning always-online into defined hours.","\u003Cp>Some of our team lives in other cities, and we have worked hybrid for two years. At first people answered messages at ten at night until energy ran out. We set some agreements, and clearer boundaries made collaboration smoother.\u003C\u002Fp>\n\u003Ch2>Our agreements\u003C\u002Fh2>\n\u003Cp>Non-urgent messages expect no instant reply. Anything sent in the evening or on weekends is handled next working day by default.\u003C\u002Fp>\n\u003Cp>There is exactly one urgent channel: a phone call. Only for production impact, and the reason is explained the next day.\u003C\u002Fp>\n\u003Cp>Cameras are default-on in meetings but optional, without interrogation. Some people focus better in quiet.\u003C\u002Fp>\n\u003Cp>Decisions go into documents, not chat history. Asymmetric information is the real cost of remote work.\u003C\u002Fp>\n\u003Ch2>What changed\u003C\u002Fh2>\n\u003Cp>Replies got slightly slower and noticeably better, because people answer after thinking.\u003C\u002Fp>\n\u003Cp>Cross-timezone work no longer waits on anyone: documents lead and whoever is online acts first.\u003C\u002Fp>\n\u003Cp>Retention improved. People who can log off in peace stay longer.\u003C\u002Fp>\n\u003Cp>Remote work rests on trust and boundaries. Tools cannot solve boundaries; agreements can.\u003C\u002Fp>","","slate","佳益方圆团队","2026-08-24T13:52:00+08:00",1,false,[16,17,18],"Team Culture","Remote Work","Collaboration",{"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":80},{"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":73},74,"multi-vendor-integration","Retrospective: Three Vendors, One Project","In multi-party projects the most expensive cost is waiting and arguing, not development.","2026-08-26T13:52:00+08:00",[71,72,18],"Retrospective","Integration",{"id":74,"parentId":21,"slug":75,"name":76,"description":77,"icon":78,"cover":9,"tone":26,"kind":27,"sortOrder":79,"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":81,"slug":82,"title":83,"excerpt":84,"content":9,"cover":9,"tone":57,"author":11,"publishedAt":85,"updatedAt":85,"readingMinutes":13,"featured":14,"tags":86,"category":90},112,"low-code-vs-custom","Where Low-Code Ends and Custom Starts","Low-code is neither universal nor a toy. The key is knowing what to hand it and what not to.","2026-08-22T13:52:00+08:00",[87,88,89],"Industry Watch","Low-Code","Technology Choice",{"id":91,"parentId":21,"slug":92,"name":87,"description":93,"icon":94,"cover":9,"tone":26,"kind":27,"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]