[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-tech-open-day-2026-en":3,"blog-adjacent-tech-open-day-2026-en":30,"blog-related-tech-open-day-2026-en":65},{"id":4,"slug":5,"title":6,"excerpt":7,"content":8,"cover":9,"tone":10,"author":11,"publishedAt":12,"updatedAt":13,"readingMinutes":14,"featured":15,"tags":16,"category":19,"seoSettings":29},9,"tech-open-day-2026","Tech Open Day: Explaining Architecture Decisions to Customers","We opened an internal architecture review to customers and explained every trade-off in language they could understand. It is part of building long-term trust.","\u003Cp>Technical reviews used to happen internally: architects present the solution, engineers raise questions, and conclusions are recorded. This year we tried something different — we opened an architecture review to customers and explained every trade-off in language they could understand.\u003C\u002Fp>\u003Ch2>What we covered\u003C\u002Fh2>\u003Cul>\u003Cli>Technology choice: why we chose a mature approach for this project instead of the newest technology;\u003C\u002Fli>\u003Cli>Data: which data must be real-time, which can be delayed, and where the cost difference comes from;\u003C\u002Fli>\u003Cli>Performance: how the system stays available for the first screen, concurrency and weak network scenarios.\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>The questions customers asked most\u003C\u002Fh2>\u003Cp>Unexpectedly, customers cared less about technical terms and more about three practical questions: can the system still be changed in three years, can the data be taken back, and who is responsible when something goes wrong. These are exactly the parts we weigh most in architecture design.\u003C\u002Fp>\u003Ch2>What comes next\u003C\u002Fh2>\u003Cp>We plan to turn the tech open day into a series, each session around one topic with customers invited to join the discussion. The value of technology ultimately returns to whether the business is better supported, and helping customers understand trade-offs is part of building long-term trust.\u003C\u002Fp>\u003Cblockquote>Explaining complexity clearly is itself an engineering capability.\u003C\u002Fblockquote>\u003Cp>Thank you to every customer who joined. The topic and date of the next open day will be announced on our website and blog.\u003C\u002Fp>","","teal","佳益方圆团队","2026-07-24T16:30:00+08:00","2026-10-18T15:58:14.758+08:00",1,false,[17,18],"Tech Open Day","Customer Communication",{"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,{},{"previous":31,"next":48},{"id":32,"slug":33,"title":34,"excerpt":35,"content":9,"cover":9,"tone":36,"author":11,"publishedAt":37,"updatedAt":37,"readingMinutes":14,"featured":15,"tags":38,"category":42},37,"excel-export-performance","Why Report Exports Are So Slow","Freezing the browser while exporting a hundred thousand rows is rarely a file-writing problem. It is about queries and memory.","indigo","2026-07-25T16:31:00+08:00",[39,40,41],"Reporting","Export","Performance",{"id":14,"parentId":21,"slug":43,"name":44,"description":45,"icon":46,"cover":9,"tone":26,"kind":27,"sortOrder":47,"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,{"id":49,"slug":50,"title":51,"excerpt":52,"content":9,"cover":9,"tone":36,"author":11,"publishedAt":53,"updatedAt":53,"readingMinutes":14,"featured":15,"tags":54,"category":58},57,"approval-flow-design","Approval Flows: Do Not Turn Organisational Problems Into Software Problems","Overlong approval chains usually reflect unclear authority, not poor workflow design.","2026-07-23T16:31:00+08:00",[55,56,57],"Approvals","Workflow","Product Design",{"id":59,"parentId":21,"slug":60,"name":61,"description":62,"icon":63,"cover":9,"tone":26,"kind":27,"sortOrder":64,"count":21},2,"product-thinking","Product Thinking","Requirement analysis, user experience and product design methods, plus the thinking from business problems to product solutions.","lightbulb",50,[66,77,88],{"id":67,"slug":68,"title":69,"excerpt":70,"content":9,"cover":9,"tone":26,"author":11,"publishedAt":71,"updatedAt":71,"readingMinutes":14,"featured":15,"tags":72,"category":76},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",[73,74,75],"Team Culture","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":78,"slug":79,"title":80,"excerpt":81,"content":9,"cover":9,"tone":82,"author":11,"publishedAt":83,"updatedAt":83,"readingMinutes":14,"featured":15,"tags":84,"category":87},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",[73,85,86],"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":89,"slug":90,"title":91,"excerpt":92,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":93,"updatedAt":93,"readingMinutes":14,"featured":15,"tags":94,"category":97},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.","2026-09-17T11:26:00+08:00",[73,95,96],"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}]