<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>架构 · 创业 · 成长</title><link>https://irudder.me/</link><description>记录真实踩过的坑与做过的取舍：架构、AI 落地、创业与职业成长。写给同样在路上的技术人。</description><language>zh-cn</language><copyright>© 2016-2026 记忆研究</copyright><managingEditor>irudder@126.com (diunilaomei)</managingEditor><webMaster>irudder@126.com (diunilaomei)</webMaster><lastBuildDate>Tue, 22 Sep 2026 09:39:18 +0000</lastBuildDate><atom:link href="https://irudder.me/index.xml" rel="self" type="application/rss+xml"/><item><title>AI 工具换得快：怎么持续用到「最新最好」而不是「最新最吵」</title><link>https://irudder.me/tools/stay-current-ai-tools/</link><pubDate>Wed, 02 Sep 2026 00:00:00 +0000</pubDate><author>irudder@126.com (diunilaomei)</author><guid isPermaLink="true">https://irudder.me/tools/stay-current-ai-tools/</guid><description>没有常青的 AI 工具榜单——教你看懂「新工具到底值不值得换」的三个信号、一套跟随节奏，和本栏目的时效承诺。</description><category>AI工具</category><category>工具更新</category><category>方法论</category><category>效率</category></item><item><title>从 POC 到生产：AI 项目的边界验收清单</title><link>https://irudder.me/growth/boundary-acceptance/</link><pubDate>Wed, 02 Sep 2026 00:00:00 +0000</pubDate><author>irudder@126.com (diunilaomei)</author><guid isPermaLink="true">https://irudder.me/growth/boundary-acceptance/</guid><description>AI 项目放生产的最后一道关：把前九章的承诺、度量、幻觉、降级、组织全部收成一张验收清单。逐条过线才能上线。</description><category>AI架构</category><category>验收清单</category><category>方法论</category><category>上线</category></item><item><title>把边界写进组织：角色、评审与流程</title><link>https://irudder.me/growth/boundary-org/</link><pubDate>Wed, 02 Sep 2026 00:00:00 +0000</pubDate><author>irudder@126.com (diunilaomei)</author><guid isPermaLink="true">https://irudder.me/growth/boundary-org/</guid><description>边界没有负责人就是口号。讲 AI 项目里谁为边界负责、变更怎么评审、事故怎么复盘——把方法论沉淀成组织机制。</description><category>AI治理</category><category>组织</category><category>流程</category><category>方法论</category></item><item><title>模型换代与回归：边界不随升级漂移</title><link>https://irudder.me/growth/upgrade-regression/</link><pubDate>Wed, 02 Sep 2026 00:00:00 +0000</pubDate><author>irudder@126.com (diunilaomei)</author><guid isPermaLink="true">https://irudder.me/growth/upgrade-regression/</guid><description>换模型、改提示词、动检索，每一次变更都可能让边界悄悄漂移。讲一套「先回归、再灰度、后锁定」的升级纪律。</description><category>AI架构</category><category>模型升级</category><category>回归测试</category><category>方法论</category></item><item><title>降级与人工接管：AI 失效时系统怎么表现</title><link>https://irudder.me/growth/degradation-handoff/</link><pubDate>Wed, 02 Sep 2026 00:00:00 +0000</pubDate><author>irudder@126.com (diunilaomei)</author><guid isPermaLink="true">https://irudder.me/growth/degradation-handoff/</guid><description>AI 一定会失效：超时、答错、被滥用、供应商故障。边界体系要求系统在 AI 不行时依然体面——讲降级链与人工接管的设计。</description><category>AI架构</category><category>降级</category><category>稳定性</category><category>方法论</category></item><item><title>AI 全链路追踪：每一步都看得见、可回放</title><link>https://irudder.me/growth/tracing-e2e/</link><pubDate>Wed, 02 Sep 2026 00:00:00 +0000</pubDate><author>irudder@126.com (diunilaomei)</author><guid isPermaLink="true">https://irudder.me/growth/tracing-e2e/</guid><description>AI 系统的「做了什么」必须有据可查：从请求、检索、工具到模型输出整条链路可回放。讲 trace 记什么、怎么排错、回放用来做什么。</description><category>AI架构</category><category>链路追踪</category><category>可观测性</category><category>方法论</category></item><item><title>幻觉的系统化治理：防、拦、兜三层</title><link>https://irudder.me/growth/hallucination-governance/</link><pubDate>Wed, 02 Sep 2026 00:00:00 +0000</pubDate><author>irudder@126.com (diunilaomei)</author><guid isPermaLink="true">https://irudder.me/growth/hallucination-governance/</guid><description>幻觉是概率事件，不是能修好的 bug。把它当系统性风险治理：输入层防、生成层拦、输出层兜，三层配合才压得住。</description><category>幻觉</category><category>AI架构</category><category>方法论</category><category>质量</category></item><item><title>效果度量：证明「做了什么、有什么效果」</title><link>https://irudder.me/growth/effect-measurement/</link><pubDate>Tue, 01 Sep 2026 00:00:00 +0000</pubDate><author>irudder@126.com (diunilaomei)</author><guid isPermaLink="true">https://irudder.me/growth/effect-measurement/</guid><description>没有度量的 AI 功能，边界就是口号。讲评测集怎么建、四类指标怎么定、基线怎么设——把「做了什么」变成数据。</description><category>AI架构</category><category>效果度量</category><category>评测</category><category>方法论</category></item><item><title>任务分流：什么交给 AI、什么必须代码或人工</title><link>https://irudder.me/growth/task-routing-boundary/</link><pubDate>Mon, 31 Aug 2026 00:00:00 +0000</pubDate><author>irudder@126.com (diunilaomei)</author><guid isPermaLink="true">https://irudder.me/growth/task-routing-boundary/</guid><description>AI 不是万能处理器，代码规则也不是。用可靠性、容错、责任三个维度给任务分类，回答「这个任务该谁干」。</description><category>AI架构</category><category>任务分流</category><category>方法论</category></item><item><title>把 AI 能力翻译成系统承诺：能力声明表</title><link>https://irudder.me/growth/capability-statement/</link><pubDate>Sun, 30 Aug 2026 00:00:00 +0000</pubDate><author>irudder@126.com (diunilaomei)</author><guid isPermaLink="true">https://irudder.me/growth/capability-statement/</guid><description>AI 功能上线前写一张能力声明表：承诺什么、不承诺什么、失败率目标、怎么验证。它让「边界」从口号变成可评审的文档。</description><category>AI架构</category><category>能力声明</category><category>方法论</category><category>项目管理</category></item><item><title>AI 能做什么、不能做什么：能力边界总纲</title><link>https://irudder.me/growth/ai-capability-boundary/</link><pubDate>Fri, 28 Aug 2026 00:00:00 +0000</pubDate><author>irudder@126.com (diunilaomei)</author><guid isPermaLink="true">https://irudder.me/growth/ai-capability-boundary/</guid><description>AI 应用出问题的根源，九成不是模型不够强，是预期错位。先把能力按可靠性分层，建立边界管理的第一课。</description><category>AI架构</category><category>能力边界</category><category>方法论</category><category>预期管理</category></item><item><title>2026 年中 Agent 框架怎么选：先分层，再谈选型</title><link>https://irudder.me/ai/agent-framework-selection-2026/</link><pubDate>Thu, 27 Aug 2026 00:00:00 +0000</pubDate><author>irudder@126.com (diunilaomei)</author><guid isPermaLink="true">https://irudder.me/ai/agent-framework-selection-2026/</guid><description>大厂 Agent SDK 扎堆发布，选型先别比参数，先用「分层心智模型」框定自己的场景：Runtime / SDK / 编排 / 平台，附决策树与 POC 验收清单。</description><category>Agent实战</category><category>技术选型</category><category>行业剖析</category></item><item><title>设计作图场景：配图、改图、批量出素材怎么用 AI</title><link>https://irudder.me/tools/ai-design-image/</link><pubDate>Wed, 26 Aug 2026 00:00:00 +0000</pubDate><author>irudder@126.com (diunilaomei)</author><guid isPermaLink="true">https://irudder.me/tools/ai-design-image/</guid><description>非设计师要配图、运营要批量素材、技术人要做示意图——AI 作图按「要办的事」分档选工具，附图库与版权的坑。</description><category>AI作图</category><category>设计</category><category>运营</category><category>工具工作流</category></item><item><title>端侧小模型：什么时候真的该把 AI 放到设备上</title><link>https://irudder.me/ai/edge-models-2026/</link><pubDate>Mon, 24 Aug 2026 00:00:00 +0000</pubDate><author>irudder@126.com (diunilaomei)</author><guid isPermaLink="true">https://irudder.me/ai/edge-models-2026/</guid><description>手机、PC、穿戴都在吹 NPU 和端侧大模型。端侧解决隐私、离线与延迟，但能力与迭代是硬伤。给出任务分流的判断方法。</description><category>端侧</category><category>LLM</category><category>AI架构</category><category>成本</category></item><item><title>调研搜索场景：AI 搜索与深度研究怎么用、怎么防吹牛</title><link>https://irudder.me/tools/ai-research-search/</link><pubDate>Sun, 23 Aug 2026 00:00:00 +0000</pubDate><author>irudder@126.com (diunilaomei)</author><guid isPermaLink="true">https://irudder.me/tools/ai-research-search/</guid><description>查资料从「翻 30 个网页」变成「问一个能联网回答的助手」。AI 搜索与深度研究类工具的区别、适用场景，以及最重要的可信度核查。</description><category>AI搜索</category><category>调研</category><category>效率</category><category>工具工作流</category></item><item><title>2026 我留在手边的开源效率工具清单</title><link>https://irudder.me/tools/open-source-efficiency-2026/</link><pubDate>Sat, 22 Aug 2026 00:00:00 +0000</pubDate><author>irudder@126.com (diunilaomei)</author><guid isPermaLink="true">https://irudder.me/tools/open-source-efficiency-2026/</guid><description>自托管与开源在 2026 年重回效率工具的主流叙事。这篇列我实际在用、且愿意推荐的开源效率工具，每条讲清为什么留。</description><category>开源</category><category>工具清单</category><category>效率</category><category>自托管</category></item><item><title>会议纪要场景：开完会，跟进项自动出来</title><link>https://irudder.me/tools/ai-meeting-notes/</link><pubDate>Thu, 20 Aug 2026 00:00:00 +0000</pubDate><author>irudder@126.com (diunilaomei)</author><guid isPermaLink="true">https://irudder.me/tools/ai-meeting-notes/</guid><description>从录音转写到纪要整理，会议场景的 AI 已经相当成熟。讲工具怎么选、纪要模板怎么定、保密会议怎么办。</description><category>AI办公</category><category>会议纪要</category><category>效率</category><category>工具工作流</category></item><item><title>AI 编程助手进研发团队：2026 现状、收益与可落地的引入方法论</title><link>https://irudder.me/ai/ai-coding-assistants-in-rd/</link><pubDate>Wed, 19 Aug 2026 00:00:00 +0000</pubDate><author>irudder@126.com (diunilaomei)</author><guid isPermaLink="true">https://irudder.me/ai/ai-coding-assistants-in-rd/</guid><description>开发者 AI 工具采用率已达八成上下，但「引入 AI 编程助手」和「引入得对」是两件事。给出可落地的四阶段引入方法论与度量基线。</description><category>行业剖析</category><category>AI编程</category><category>研发效能</category><category>AI商业化</category></item><item><title>读资料场景：长文档、论文、外文怎么用 AI 提效</title><link>https://irudder.me/tools/ai-reading-assistant/</link><pubDate>Tue, 18 Aug 2026 00:00:00 +0000</pubDate><author>irudder@126.com (diunilaomei)</author><guid isPermaLink="true">https://irudder.me/tools/ai-reading-assistant/</guid><description>面对读不完的长文档与论文：从「先通读」改成「先提问」。给文档问答、外文翻译、文献管理三类工具的搭配工作流。</description><category>AI办公</category><category>阅读</category><category>论文</category><category>工具工作流</category></item><item><title>2026 AI 效率工具实测：留下三样，卸载一屏</title><link>https://irudder.me/tools/ai-tools-review-2026/</link><pubDate>Mon, 17 Aug 2026 00:00:00 +0000</pubDate><author>irudder@126.com (diunilaomei)</author><guid isPermaLink="true">https://irudder.me/tools/ai-tools-review-2026/</guid><description>AI 效率工具装了一屏，三个月后留下的只有三样。分享我的筛选标准与实测方法——帮你省下试错时间。</description><category>AI办公</category><category>工具测评</category><category>效率</category><category>测评方法</category></item><item><title>办事前先选工具：AI 工具场景速查矩阵</title><link>https://irudder.me/tools/ai-tools-scenario-matrix/</link><pubDate>Sun, 16 Aug 2026 00:00:00 +0000</pubDate><author>irudder@126.com (diunilaomei)</author><guid isPermaLink="true">https://irudder.me/tools/ai-tools-scenario-matrix/</guid><description>别从工具出发，从「要办的事」出发。这张场景速查矩阵帮你 30 秒定位：这个场景该用哪类 AI 工具，深读该看哪篇。</description><category>AI办公</category><category>工具清单</category><category>场景方法</category><category>选型</category></item><item><title>LLM 应用安全：提示注入不是段子，是生产事故</title><link>https://irudder.me/ai/llm-application-security/</link><pubDate>Wed, 12 Aug 2026 00:00:00 +0000</pubDate><author>irudder@126.com (diunilaomei)</author><guid isPermaLink="true">https://irudder.me/ai/llm-application-security/</guid><description>提示注入、工具越权、上下文数据外泄——LLM 应用的攻击面比传统 Web 大得多。给出攻击面地图与分层防护清单。</description><category>AI架构</category><category>LLM</category><category>安全</category><category>应用场景</category></item><item><title>脱敏案例：老单体服务化的 9 个月——拆什么、不拆什么</title><link>https://irudder.me/projects/case-monolith-to-services/</link><pubDate>Sat, 08 Aug 2026 00:00:00 +0000</pubDate><author>irudder@126.com (diunilaomei)</author><guid isPermaLink="true">https://irudder.me/projects/case-monolith-to-services/</guid><description>一份脱敏的演进案例：一个跑了 6 年的老单体，怎么在业务不停的前提下拆成服务。重点是拆的次序与「先加边界后加网络」。</description><category>项目案例</category><category>架构实战</category><category>微服务</category><category>演进</category></item><item><title>AI 辅助写作工作流：人写骨架和观点，AI 当编辑</title><link>https://irudder.me/tools/ai-writing-workflow/</link><pubDate>Wed, 05 Aug 2026 00:00:00 +0000</pubDate><author>irudder@126.com (diunilaomei)</author><guid isPermaLink="true">https://irudder.me/tools/ai-writing-workflow/</guid><description>写作最难的不是措辞是判断。这篇讲博客/报告/方案怎么用 AI 提效而不失主见：人负责什么、AI 负责什么、坑在哪。</description><category>AI办公</category><category>写作</category><category>工作流</category><category>效率</category></item><item><title>AI 应用分层架构参考蓝图：用开源组件拼出能上线的骨架</title><link>https://irudder.me/ai/ai-app-reference-architecture/</link><pubDate>Mon, 03 Aug 2026 00:00:00 +0000</pubDate><author>irudder@126.com (diunilaomei)</author><guid isPermaLink="true">https://irudder.me/ai/ai-app-reference-architecture/</guid><description>不管你做客服、知识库、陪伴还是游戏，AI 应用的生产骨架大致是同一张图。把每层用什么开源组件、什么时候该用托管 API 讲清楚。</description><category>AI架构</category><category>技术方案</category><category>开源</category></item><item><title>从 RAG 到 Agentic RAG：检索架构在演进，边界也在变</title><link>https://irudder.me/ai/agentic-rag-evolution/</link><pubDate>Sat, 01 Aug 2026 00:00:00 +0000</pubDate><author>irudder@126.com (diunilaomei)</author><guid isPermaLink="true">https://irudder.me/ai/agentic-rag-evolution/</guid><description>单次检索 → 混合检索 → 多跳/查询改写 → 自主规划检索。RAG 在往 Agent 化演进，但每一层演进都加成本与不确定性，这篇讲怎么选。</description><category>RAG</category><category>Agent实战</category><category>AI架构</category><category>技术选型</category></item><item><title>用 AI 做 PPT 的工作流：结构自己做，排版交给机器</title><link>https://irudder.me/tools/ai-ppt-workflow/</link><pubDate>Wed, 29 Jul 2026 00:00:00 +0000</pubDate><author>irudder@126.com (diunilaomei)</author><guid isPermaLink="true">https://irudder.me/tools/ai-ppt-workflow/</guid><description>全自动生成 PPT 是陷阱：结构是思想，排版才是体力。分享大纲→内容→排版三段式工作流，附开源幻灯片方案。</description><category>AI办公</category><category>PPT</category><category>写作</category><category>工作流</category></item><item><title>技术方案：虚拟陪伴类应用的开源落地（记忆·一致性·安全）</title><link>https://irudder.me/ai/virtual-companion/</link><pubDate>Tue, 28 Jul 2026 00:00:00 +0000</pubDate><author>irudder@126.com (diunilaomei)</author><guid isPermaLink="true">https://irudder.me/ai/virtual-companion/</guid><description>虚拟陪伴是留存最强也最难做的 AI 场景：角色一致性、长短期记忆、多模态表达、安全与合规。给一套开源技术栈方案。</description><category>技术方案</category><category>应用场景</category><category>Agent实战</category><category>开源</category></item><item><title>SaaS 怎么嵌 AI：先算三笔账，再谈增量价值</title><link>https://irudder.me/ai/ai-saas-embed-accounting/</link><pubDate>Tue, 21 Jul 2026 00:00:00 +0000</pubDate><author>irudder@126.com (diunilaomei)</author><guid isPermaLink="true">https://irudder.me/ai/ai-saas-embed-accounting/</guid><description>身边做 SaaS 的朋友今年几乎都被问过「你们有没有 AI 功能」。这篇不讲功能怎么加，讲决策前要算清楚的三笔账。</description><category>行业剖析</category><category>AI商业化</category><category>SaaS</category><category>成本</category></item><item><title>用 Obsidian 三年：笔记体系是长出来的，不是设计出来的</title><link>https://irudder.me/tools/obsidian-notes-review/</link><pubDate>Wed, 15 Jul 2026 00:00:00 +0000</pubDate><author>irudder@126.com (diunilaomei)</author><guid isPermaLink="true">https://irudder.me/tools/obsidian-notes-review/</guid><description>从收藏夹到 Obsidian 三年的真实过程：踩过「过度设计」和「插件病」的坑，最后留下的是一套极简结构。工具部分见工具总览。</description><category>知识管理</category><category>工具</category><category>效率</category><category>复盘</category></item></channel></rss>