[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-barcode-and-rfid-basics-zh-CN":3,"blog-adjacent-barcode-and-rfid-basics-zh-CN":29,"blog-related-barcode-and-rfid-basics-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},43,"barcode-and-rfid-basics","扫码与标签：仓储数字化的第一步","很多仓储项目的起点不是系统，而是把每一件货变成一个可扫描的编号。","\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>","","indigo","佳益方圆团队","2026-05-14T14:49:00+08:00",1,false,[16,17,18],"仓储","条码","制造业",{"id":13,"parentId":20,"slug":21,"name":22,"description":23,"icon":24,"cover":9,"tone":25,"kind":26,"sortOrder":27,"count":20},0,"engineering","技术专栏","架构设计、性能优化、AI 集成与跨端方案等一线技术实践，由研发团队持续分享。","cpu","blue","article",60,{},{"previous":30,"next":47},{"id":31,"slug":32,"title":33,"excerpt":34,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":35,"updatedAt":35,"readingMinutes":13,"featured":14,"tags":36,"category":40},22,"why-we-stay-in-lanzhou","我们为什么留在兰州","在小城市做软件公司，客户少、人才难招、信息落后半拍，但也有它独特的优势。","2026-05-16T13:36:00+08:00",[37,38,39],"创业","兰州","选择",{"id":41,"parentId":20,"slug":42,"name":43,"description":44,"icon":45,"cover":9,"tone":25,"kind":26,"sortOrder":46,"count":20},6,"founder-notes","创业手记","创始团队在经营、管理与产品上的思考，记录一家软件公司的成长过程。","pen-tool",10,{"id":48,"slug":49,"title":50,"excerpt":51,"content":9,"cover":9,"tone":52,"author":11,"publishedAt":53,"updatedAt":53,"readingMinutes":13,"featured":14,"tags":54,"category":58},63,"error-message-audience","错误提示应该写给谁看","“操作失败，请重试”是最没用的提示。用户需要知道发生了什么、能做什么。","cyan","2026-05-12T14:49:00+08:00",[55,56,57],"错误提示","体验","产品设计",{"id":59,"parentId":20,"slug":60,"name":61,"description":62,"icon":63,"cover":9,"tone":25,"kind":26,"sortOrder":64,"count":20},2,"product-thinking","产品思维","需求分析、用户体验与产品设计方法论，以及从业务问题到产品方案的思考过程。","lightbulb",50,[66,77,88],{"id":67,"slug":68,"title":69,"excerpt":70,"content":9,"cover":9,"tone":52,"author":11,"publishedAt":71,"updatedAt":71,"readingMinutes":13,"featured":14,"tags":72,"category":76},30,"integration-api-pitfalls","企业系统集成：接口对接最容易踩的五个坑","接口文档写得再全，真正对接时仍然会卡在字段约定、超时和重复推送这些细节上。","2026-10-17T09:00:00+08:00",[73,74,75],"系统集成","接口","工程实践",{"id":13,"parentId":20,"slug":21,"name":22,"description":23,"icon":24,"cover":9,"tone":25,"kind":26,"sortOrder":27,"count":20},{"id":13,"slug":78,"title":79,"excerpt":80,"content":9,"cover":9,"tone":52,"author":11,"publishedAt":81,"updatedAt":82,"readingMinutes":59,"featured":83,"tags":84,"category":87},"why-enterprise-systems-age","为什么企业系统会在三年后开始“老化”","系统上线时功能齐全，三年后却处处别扭。问题往往不在代码，而在交付时被忽略的那些变化。","2026-10-16T09:30:00+08:00","2026-10-18T15:58:14.648+08:00",true,[85,86],"系统演进","架构设计",{"id":13,"parentId":20,"slug":21,"name":22,"description":23,"icon":24,"cover":9,"tone":25,"kind":26,"sortOrder":27,"count":20},{"id":89,"slug":90,"title":91,"excerpt":92,"content":9,"cover":9,"tone":25,"author":11,"publishedAt":93,"updatedAt":93,"readingMinutes":13,"featured":14,"tags":94,"category":98},31,"idempotent-design-basics","幂等设计：重复提交不只是用户手抖","网络重试、消息重投、用户连点，都会让同一个请求到达多次。幂等应该设计在接口里。","2026-10-05T10:13:00+08:00",[95,96,97],"接口设计","幂等","可靠性",{"id":13,"parentId":20,"slug":21,"name":22,"description":23,"icon":24,"cover":9,"tone":25,"kind":26,"sortOrder":27,"count":20}]