<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Mafan — Writing</title><link>https://www.dengmengmian.com/en/writing</link><atom:link href="https://www.dengmengmian.com/en/rss.xml" rel="self" type="application/rss+xml"/><description>Exploring how individuals build software, work with AI agents, and design durable systems for work and life.</description><language>en</language><generator>Mafan Lab / ForgeKit</generator><copyright>© 2026 Mafan</copyright><lastBuildDate>Thu, 27 Aug 2026 14:23:08 GMT</lastBuildDate><item><title>Traditional Tests Pass, but How to Prove the Agent Is Actually Better</title><link>https://www.dengmengmian.com/en/writing/proving-agent-improvement-beyond-traditional-tests</link><guid isPermaLink="true">https://www.dengmengmian.com/en/writing/proving-agent-improvement-beyond-traditional-tests</guid><pubDate>Fri, 21 Aug 2026 05:59:06 GMT</pubDate><dc:creator>Mafan</dc:creator><description>Traditional tests only prove the code isn&apos;t broken; they can&apos;t evaluate whether the Agent has truly improved. Eval is needed: run a fixed task set with unified scoring rules repeatedly, comparing success rate, cost, time, and regressions. The two systems complement each other; before release, pass traditional tests first, then run Eval, to avoid optimizing by feel.</description><category>Agent开发</category><category>AI评测Eval</category><category>大模型应用开发</category></item><item><title>I Built a Coding Agent and Realized Calling the Model Is Just the Beginning</title><link>https://www.dengmengmian.com/en/writing/building-coding-agent-just-beginning</link><guid isPermaLink="true">https://www.dengmengmian.com/en/writing/building-coding-agent-just-beginning</guid><pubDate>Fri, 21 Aug 2026 05:56:25 GMT</pubDate><dc:creator>Mafan</dc:creator><description>Building a coding agent taught me that calling the model is just the beginning. In long tasks, state management, tool logging, observability, and failure recovery are key. Chat is just the entry point; the system must act like a runtime to keep progressing and validating results. Reliability often matters more than a one-off impressive answer.</description><category>效率提升</category><category>产品思维</category><category>AI编程</category></item><item><title>ChatGPT and Codex Merge, Protocol Changes Again</title><link>https://www.dengmengmian.com/en/writing/chatgpt-codex-merger-terms-update</link><guid isPermaLink="true">https://www.dengmengmian.com/en/writing/chatgpt-codex-merger-terms-update</guid><pubDate>Fri, 21 Aug 2026 05:54:15 GMT</pubDate><dc:creator>Mafan</dc:creator><description>After ChatGPT and Codex merged, the protocol changed again: tool definitions moved into additional_tools, and third-party models that don&apos;t receive tools may fake calls. The author&apos;s local gateway AgentGate has adapted, restoring tools and forwarding upstream; the merged desktop client can still point to localhost to call DeepSeek and other models.</description><category>本地网关</category><category>协议转换</category><category>AI编程</category></item><item><title>Sharing a Small Tool I Use Myself (Self-Made)</title><link>https://www.dengmengmian.com/en/writing/my-self-made-tool</link><guid isPermaLink="true">https://www.dengmengmian.com/en/writing/my-self-made-tool</guid><pubDate>Fri, 21 Aug 2026 05:51:22 GMT</pubDate><dc:creator>Mafan</dc:creator><description>ReviewGate is an open-source MIT-licensed pre-merge filtering tool that screens for high-risk issues from perspectives like security, performance, logic, and AI Smell, categorizing them as block or warn. It prefers to fail rather than give a false green light. It supports --fix, CI integration, and false-positive sharing, and is read-only by default. It&apos;s recommended to observe first, then gradually enable.</description><category>需求验证</category><category>AI编程</category></item><item><title>After Middle Age, Fitness Is Not Just for the Body, but Also for Preserving Time for Solitude and Thinking</title><link>https://www.dengmengmian.com/en/writing/midlife-fitness-solitude-thinking-time</link><guid isPermaLink="true">https://www.dengmengmian.com/en/writing/midlife-fitness-solitude-thinking-time</guid><pubDate>Fri, 21 Aug 2026 05:47:43 GMT</pubDate><dc:creator>Mafan</dc:creator><description>After middle age, the meaning of fitness goes beyond physical exercise; it becomes a deliberate way to carve out uninterrupted personal time. It allows one to temporarily step away from work, family, and fragmented information, restoring attention and order, and reclaiming quiet space for independent thought. This ability to &apos;return to oneself&apos; is more important than mere physical management.</description><category>一人做事</category><category>节奏感</category></item><item><title>Working alone, it&apos;s easy to overestimate execution and underestimate direction and pace</title><link>https://www.dengmengmian.com/en/writing/overestimating-execution-underestimating-direction-and-rhythm</link><guid isPermaLink="true">https://www.dengmengmian.com/en/writing/overestimating-execution-underestimating-direction-and-rhythm</guid><pubDate>Tue, 28 Jul 2026 16:25:31 GMT</pubDate><dc:creator>Mafan</dc:creator><description>When working alone, it&apos;s easy to overestimate execution and underestimate direction and pace. Execution is visible, but if the direction is wrong or the pace is chaotic, the harder you work, the further you may drift from key results. What truly matters is constantly judging the main line, stage priorities, and what&apos;s most important, avoiding being busy but not making real progress. A sense of direction and pace matter more than sheer effort for steady long-term progress.</description><category>执行力</category><category>方向感</category><category>节奏感</category></item><item><title>I Like Codex, but It Can&apos;t Use DeepSeek, So I Built a Local Gateway</title><link>https://www.dengmengmian.com/en/writing/i-like-codex-but-it-cant-use-deepseek-so-i-made-a-local-gateway</link><guid isPermaLink="true">https://www.dengmengmian.com/en/writing/i-like-codex-but-it-cant-use-deepseek-so-i-made-a-local-gateway</guid><pubDate>Tue, 28 Jul 2026 16:25:31 GMT</pubDate><dc:creator>Mafan</dc:creator><description>The author likes Codex but wants to use DeepSeek, and finds the protocols incompatible. So they developed a local gateway called AgentGate. This tool converts Codex&apos;s Responses API requests into DeepSeek&apos;s Chat Completions format, and further implements intelligent routing: text-only tasks automatically go to DeepSeek, while multimodal tasks with images switch to KimiCoding. This solves the fragmentation of tool and model protocols in AI coding, letting users focus on development.</description><category>本地网关</category><category>协议转换</category><category>AI编程</category></item><item><title>Why Many Projects Become Unprofitable: It’s Not Slow Development—It’s Scope Creep</title><link>https://www.dengmengmian.com/en/writing/why-projects-fail-not-due-to-slow-development-but-scope-creep</link><guid isPermaLink="true">https://www.dengmengmian.com/en/writing/why-projects-fail-not-due-to-slow-development-but-scope-creep</guid><pubDate>Tue, 28 Jul 2026 16:25:31 GMT</pubDate><dc:creator>Mafan</dc:creator><description>Project unprofitability is often attributed to slow development, but the more critical factor is scope creep. Slow development affects efficiency, while scope creep undermines the profit structure. Small requirements accumulate, causing scope creep, distorted quotes, and gradually eroded profits. Holding the line on boundaries is more important than improving efficiency: clarify what&apos;s not included, designate decision-makers, watch out for accumulating small changes, and define clear acceptance criteria.</description><category>边界失控</category><category>项目利润</category><category>需求蔓延</category></item><item><title>How Do I Decide Whether a Task Is Worth Delegating to AI?</title><link>https://www.dengmengmian.com/en/writing/how-to-decide-if-a-task-is-worth-delegating-to-ai</link><guid isPermaLink="true">https://www.dengmengmian.com/en/writing/how-to-decide-if-a-task-is-worth-delegating-to-ai</guid><pubDate>Tue, 28 Jul 2026 16:25:30 GMT</pubDate><dc:creator>Mafan</dc:creator><description>Deciding whether to delegate a work task to AI hinges on distinguishing between &quot;can delegate&quot; and &quot;should delegate.&quot; The author proposes five criteria: tasks with high repetition but low judgment density are suitable for AI; tasks that would weaken your understanding of the problem require caution; tasks with high error costs should not be delegated; tasks that allow quick verification and correction are suitable; and tasks that require a stance rather than mere output should be done yourself. The core is </description><category>AI工作边界</category><category>效率与失控</category><category>判断标准</category></item><item><title>5 Things I Consider When Deciding Whether a Feature Is Worth Building</title><link>https://www.dengmengmian.com/en/writing/5-things-to-evaluate-a-requirement</link><guid isPermaLink="true">https://www.dengmengmian.com/en/writing/5-things-to-evaluate-a-requirement</guid><pubDate>Tue, 28 Jul 2026 16:25:30 GMT</pubDate><dc:creator>Mafan</dc:creator><description>This article shares five core principles for judging whether a feature is worth building: confirming the problem truly exists rather than being imagined, assessing whether the pain point is strong enough, distinguishing whether the feature drives results or merely fills a sense of completeness, determining whether the timing is right, and whether the feature can bring verifiable changes after completion. It emphasizes that product success lies not in feature accumulation but in precise filtering and priorit</description><category>需求判断</category><category>产品优先级</category><category>痛点分析</category></item><item><title>In the AI Era, the Hardest Part of Working Alone Isn&apos;t Development—It&apos;s Continuously Doing the Right Things</title><link>https://www.dengmengmian.com/en/writing/ai-era-hardest-part-is-not-development-but-persisting-in-doing-the-right-things</link><guid isPermaLink="true">https://www.dengmengmian.com/en/writing/ai-era-hardest-part-is-not-development-but-persisting-in-doing-the-right-things</guid><pubDate>Tue, 28 Jul 2026 16:25:30 GMT</pubDate><dc:creator>Mafan</dc:creator><description>AI lowers the barrier for individual development, but the real challenge for solo workers is continuously doing the right things: choosing direction, managing pace, making trade-offs, and maintaining persistence. AI makes &apos;being able to do&apos; easier, but makes &apos;what to do&apos; more critical, easily leading to scattered focus on things that seem right but aren&apos;t key.</description><category>一人做事</category><category>方向选择</category><category>AI门槛</category></item><item><title>When Taking on a Project, the First Thing I Confirm Is Not the Technical Solution, but the Requirement Boundaries</title><link>https://www.dengmengmian.com/en/writing/confirming-requirements-boundaries-before-technical-solutions</link><guid isPermaLink="true">https://www.dengmengmian.com/en/writing/confirming-requirements-boundaries-before-technical-solutions</guid><pubDate>Tue, 28 Jul 2026 16:25:30 GMT</pubDate><dc:creator>Mafan</dc:creator><description>When taking on a project, confirm the requirement boundaries before the technical solution. The boundaries determine what the project does, what it doesn&apos;t do, who has the final say, how changes are handled, and what delivery is based on. Unclear boundaries can cause the project to be dragged down by scattered requirements, losing control of profit and pace. Confirming the core goal, defining the scope, specifying the decision-maker, agreeing on change rules, and delivery standards are prerequisites for pro</description><category>需求边界</category><category>项目失控</category><category>变更管理</category></item><item><title>AI Is Rewriting My Workflow, but Not Every Step Is Worth Handing Over to It</title><link>https://www.dengmengmian.com/en/writing/ai-rewriting-workflow-not-every-step-worth-it</link><guid isPermaLink="true">https://www.dengmengmian.com/en/writing/ai-rewriting-workflow-not-every-step-worth-it</guid><pubDate>Tue, 28 Jul 2026 16:25:30 GMT</pubDate><dc:creator>Mafan</dc:creator><description>AI is changing my workflow, but not every step is suitable for it. I&apos;ve learned to first judge which tasks are worth AI&apos;s involvement, such as drafts, information organization, and repetitive work, while key decisions, final structure, and business understanding still require my personal control. This division of labor improves efficiency but avoids blind reliance leading to loss of control.</description><category>AI工作流</category><category>效率提升</category><category>人机协作</category></item><item><title>When I Build Products, the First Thing I Cut Isn&apos;t Features—It&apos;s Illusions</title><link>https://www.dengmengmian.com/en/writing/cutting-illusions-not-features-in-product-development</link><guid isPermaLink="true">https://www.dengmengmian.com/en/writing/cutting-illusions-not-features-in-product-development</guid><pubDate>Tue, 28 Jul 2026 16:25:30 GMT</pubDate><dc:creator>Mafan</dc:creator><description>In the past, when building products, I always preferred to add features. Later, I gradually realized that many products don&apos;t die because they can&apos;t be built, but because they think too much. In the early stages of a product, what should be cut first is often not pages or flows, but those unverified illusions that are already taken for granted.</description><category>产品思维</category><category>需求验证</category><category>创业反思</category></item></channel></rss>