Skip to content
Back/Claude Code

Memento-driven Development

View in Graph
Updated 2026-09-26
1 min read
155 words

Memento-driven Development

Memento-driven Development 是 Matt Pocock 对 AI 辅助编程开发方式的命名:像电影《记忆碎片》(Memento) 的主角一样,agent 每拍(session)都会"失忆",所以工程实践必须围绕"给下一个拍/agent 留下线索"来组织。

What it is

Matt Pocock 认为我们正在进入一种新的开发方式,值得一个名字(verging on worthy of a name)。Thorsten 提议叫 "memento-driven development"——像 Memento 里每 15 分钟失忆的主角,靠纹在身上的笔记和宝丽来照片生活。Matt 立刻认同:

Matt: "Memento. I love that. Memento driven development. That's really good."

Why it matters

这个命名把一堆零散实践(leitmotif、leading words、wayfinder、白班/夜班、Shift-right、烧掉代码重写)统一到一个心智模型下:每次失忆后的"重新定位成本"是 AI 编程的核心摩擦,好的 harness 就是高质量的宝丽来照片。

Key points

  • 每拍失忆是常态:agent session 之间无记忆,重新定位靠上下文工程
  • 线索质量决定 ramp 速度:与 harness-engineering/recursive-improvement-brain 的三条 Brain 规则互为印证
  • 命名统一散点实践:leading words(writing/leading-words-longform-motifs)、wayfinder(mental-models/wayfinder-project-map)、白班/夜班、Shift-right 都是 memento 的具体手段
  • 机制解释(第二来源):在 Pragmatic Engineer 访谈中,Matt 把命名升级为机制论断——"your code is the environment the agent operates in"。人类工程师可以靠记忆绕开烂代码库,agent 不能;为"失忆新员工"优化代码由此成为软件基本功的新约束,而不只是礼仪
  • 正式命名刚发生:概念处于早期,值得跟踪 Matt 后续是否展开成文章/演讲

Counterpoints & Gaps

  • 目前只是播客里的命名瞬间,无系统性方法论
  • 与既有的 context engineering、memory engineering 术语边界尚不清晰

How to apply

Sources

Synthesized from 4 sources

Evolution

1 event
  1. absorbed

    Derived from source material

    This page is currently synthesized from 4 sources.

    From AI Builders Digest 2026-09-21, Matt Pocock on The Pragmatic Engineer, 2026-09-21, 2026-09-20 Matt Pocock AI Skills Pragmatic EngineerTo Memento-driven Development
    Sources: raw/briefing/AI Builders Digest/2026-09-21.md · raw/social-triage/2026-09-20 Matt Pocock AI Skills Pragmatic Engineer.md · /Users/jean/Documents/Obsidian Vault/raw/briefing/AI Builders Digest/2026-09-21.md · /Users/jean/Documents/Obsidian Vault/raw/social-triage/2026-09-20 Matt Pocock AI Skills Pragmatic Engineer.md

Linked from