[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-error-message-audience-zh-CN":3,"blog-adjacent-error-message-audience-zh-CN":30,"blog-related-error-message-audience-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":29},63,"error-message-audience","错误提示应该写给谁看","“操作失败，请重试”是最没用的提示。用户需要知道发生了什么、能做什么。","\u003Cp>系统里最常见的错误提示是“操作失败”“系统异常”“请稍后重试”。这三句话有一个共同点：用户看完之后，处境没有任何变化。\u003C\u002Fp>\n\u003Ch2>提示要回答两个问题\u003C\u002Fh2>\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>","","cyan","佳益方圆团队","2026-05-12T14:49: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},2,0,"product-thinking","产品思维","需求分析、用户体验与产品设计方法论，以及从业务问题到产品方案的思考过程。","lightbulb","blue","article",50,{},{"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":13,"featured":14,"tags":38,"category":42},43,"barcode-and-rfid-basics","扫码与标签：仓储数字化的第一步","很多仓储项目的起点不是系统，而是把每一件货变成一个可扫描的编号。","indigo","2026-05-14T14:49:00+08:00",[39,40,41],"仓储","条码","制造业",{"id":13,"parentId":21,"slug":43,"name":44,"description":45,"icon":46,"cover":9,"tone":26,"kind":27,"sortOrder":47,"count":21},"engineering","技术专栏","架构设计、性能优化、AI 集成与跨端方案等一线技术实践，由研发团队持续分享。","cpu",60,{"id":49,"slug":50,"title":51,"excerpt":52,"content":9,"cover":9,"tone":36,"author":11,"publishedAt":53,"updatedAt":53,"readingMinutes":13,"featured":14,"tags":54,"category":58},83,"handover-without-docs","团队交接复盘：文档缺失的一个月","核心开发离职，接手的人花了一个月才敢改第一行代码。","2026-05-10T14:49:00+08:00",[55,56,57],"复盘","交接","团队",{"id":59,"parentId":21,"slug":60,"name":61,"description":62,"icon":63,"cover":9,"tone":26,"kind":27,"sortOrder":64,"count":21},3,"project-retrospective","项目复盘","从 0 到 1 的真实项目记录，完整呈现问题、方案、踩坑经验与最终结果。","clipboard-check",40,[66,76,85],{"id":28,"slug":67,"title":68,"excerpt":69,"content":9,"cover":9,"tone":36,"author":11,"publishedAt":70,"updatedAt":70,"readingMinutes":13,"featured":14,"tags":71,"category":75},"grading-requirement-confidence","需求的真实度分级","把需求当成事实来做，是项目延期最常见的原因。需求其实有可信度高低之分。","2026-10-15T09:00:00+08:00",[72,73,74],"需求","产品方法","风险管理",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"id":20,"slug":77,"title":78,"excerpt":79,"content":9,"cover":9,"tone":36,"author":11,"publishedAt":80,"updatedAt":81,"readingMinutes":20,"featured":14,"tags":82,"category":84},"vertical-product-rules","垂直行业产品的分水岭：把行业默认规则写进系统","垂直不是换一个行业名字。真正的门槛，是能否理解并承接那些从业者习以为常的默认规则。","2026-10-09T10:00:00+08:00","2026-10-18T15:58:14.661+08:00",[83,18],"行业产品",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"id":86,"slug":87,"title":88,"excerpt":89,"content":9,"cover":9,"tone":26,"author":11,"publishedAt":90,"updatedAt":90,"readingMinutes":13,"featured":14,"tags":91,"category":93},51,"mvp-boundary","MVP 的边界怎么划","最小可用不是功能最少，而是能完整跑通一条业务闭环。","2026-10-03T10:13:00+08:00",[92,73,72],"MVP",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21}]