[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-low-code-vs-custom-zh-CN":3,"blog-adjacent-low-code-vs-custom-zh-CN":29,"blog-related-low-code-vs-custom-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":28},112,"low-code-vs-custom","低代码与定制开发的边界","低代码不是万能的，也不是玩具。关键是知道哪些事该交给它，哪些不该。","\u003Cp>这两年低代码平台越来越多，客户也经常问：能不能全用低代码做。我们的回答是：能省不少事，但有明确的边界。下面是看到的几种典型情况。\u003C\u002Fp>\n\u003Ch2>适合低代码的场景\u003C\u002Fh2>\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-08-22T13:52:00+08:00",1,false,[16,17,18],"行业观察","低代码","技术选型",{"id":20,"parentId":21,"slug":22,"name":16,"description":23,"icon":24,"cover":9,"tone":25,"kind":26,"sortOrder":27,"count":21},5,0,"industry-watch","对互联网、软件与数字化行业趋势的深度分析，输出团队自己的判断。","globe","blue","article",20,{},{"previous":30,"next":48},{"id":31,"slug":32,"title":33,"excerpt":34,"content":9,"cover":9,"tone":35,"author":11,"publishedAt":36,"updatedAt":36,"readingMinutes":13,"featured":14,"tags":37,"category":41},93,"remote-work-boundaries","远程协作的边界","远程办公的难点不是沟通工具，而是把\"随时在线\"变成\"各有时段\"。","slate","2026-08-24T13:52:00+08:00",[38,39,40],"团队文化","远程办公","协作",{"id":42,"parentId":21,"slug":43,"name":44,"description":45,"icon":46,"cover":9,"tone":25,"kind":26,"sortOrder":47,"count":21},4,"team-culture","团队动态","公司活动、技术分享、团建与招聘文化，了解佳益方圆团队的日常。","users",30,{"id":49,"slug":50,"title":51,"excerpt":52,"content":9,"cover":9,"tone":35,"author":11,"publishedAt":53,"updatedAt":53,"readingMinutes":13,"featured":14,"tags":54,"category":58},14,"partnership-exit-clause","合伙人之间先说清退出机制","股权、分工和退出方式，最好在公司还小、关系还好的时候写清楚。","2026-08-20T13:52:00+08:00",[55,56,57],"创业","合伙人","股权",{"id":59,"parentId":21,"slug":60,"name":61,"description":62,"icon":63,"cover":9,"tone":25,"kind":26,"sortOrder":64,"count":21},6,"founder-notes","创业手记","创始团队在经营、管理与产品上的思考，记录一家软件公司的成长过程。","pen-tool",10,[66,76,86],{"id":67,"slug":68,"title":69,"excerpt":70,"content":9,"cover":9,"tone":35,"author":11,"publishedAt":71,"updatedAt":71,"readingMinutes":13,"featured":14,"tags":72,"category":75},108,"gansu-manufacturing-digitalization","甘肃制造业数字化的三个观察","跑了十几家本地制造企业之后，我们看到数字化不再是买软件，而是补基础。","2026-10-09T09:00:00+08:00",[16,73,74],"制造业","数字化",{"id":20,"parentId":21,"slug":22,"name":16,"description":23,"icon":24,"cover":9,"tone":25,"kind":26,"sortOrder":27,"count":21},{"id":77,"slug":78,"title":79,"excerpt":80,"content":9,"cover":9,"tone":25,"author":11,"publishedAt":81,"updatedAt":81,"readingMinutes":13,"featured":14,"tags":82,"category":85},109,"local-software-budget","本地软件预算的两个新趋势","预算总额没有明显增长，但花钱的方式变了：更少的一次性大项目，更多的持续性投入。","2026-09-27T10:13:00+08:00",[16,83,84],"预算","信息化",{"id":20,"parentId":21,"slug":22,"name":16,"description":23,"icon":24,"cover":9,"tone":25,"kind":26,"sortOrder":27,"count":21},{"id":42,"slug":87,"title":88,"excerpt":89,"content":9,"cover":9,"tone":90,"author":11,"publishedAt":91,"updatedAt":92,"readingMinutes":13,"featured":14,"tags":93,"category":96},"cross-border-first-90-days","品牌出海的前 90 天：独立站、支付与履约","有一个英文网站只是开始。真正决定出海成败的，是站点之外的支付、合规与交付体验。","cyan","2026-09-18T10:30:00+08:00","2026-10-18T15:58:14.692+08:00",[94,95],"品牌出海","跨境电商",{"id":20,"parentId":21,"slug":22,"name":16,"description":23,"icon":24,"cover":9,"tone":25,"kind":26,"sortOrder":27,"count":21}]