那一天,AI 教会了我一件关于我自己系统的事
一份文档本身什么都不产出,却约束着之后产出的一切,它该放在哪里?常用的标准——变化的快慢——不够用。取而代之的是一个按作用划分的标准:这份文件是在产出结果、保存知识、描述当前状态,还是在约束未来的行动?这个标准适用于架构未曾预想的任何对象。
一份文档本身什么都不产出,却约束着之后产出的一切,它该放在哪里?常用的标准——变化的快慢——不够用。取而代之的是一个按作用划分的标准:这份文件是在产出结果、保存知识、描述当前状态,还是在约束未来的行动?这个标准适用于架构未曾预想的任何对象。
花了几个月搭建的方法,会不会早已以别的名字存在于别处?查证的做法可以归结为几步:把想法拆解成机制,检索功能而不是词汇,走出本学科和英语世界,并事先规定一项新发现必须改变什么才算数。每一轮检索,可以宣称为原创的部分都在缩小,而方法本身的定位反而更清楚了。
借助 AI 快速产出,最后会挤掉用来思考的时间。这里给出一套具体的做法来守住它:一个有限的卡片核心,靠间隔重复保持鲜活,再摊在桌上,拿新想法与自己的信念对照检验。读完你会知道:什么样的想法才配进卡组,复习的节奏怎么定,以及第一步从哪里开始。
不必依赖某处一台开着的 Mac,也能用 Contexte 工作。整套方案只有三块:ChatGPT 负责推理,项目指令定义引擎,Google Sheets 负责记忆。实际效果是:在展会上边走边口述一段对话,持久化,摄入,然后在离场前问系统还有哪些问题没问。
一个大客户卡住了你的单子:他要求数据放在自己的 Azure 里,用他的 IAM、他的密钥、他的 LLM 合同。本文给出一套筛选这类要求的框架:哪些真正承载你的价值,哪些只是让产品买得进来,以及客户的控制权和你推动产品演进的能力之间,边界该划在哪里。
Five days later, you rarely find the one paragraph that mattered in a long ChatGPT conversation. This is the story of how I got a precise fragment out of the flow on demand, using nothing but a custom instruction and a Google Sheets outbox — a blocked API, a workaround that failed, then a solution that went from 50 seconds to two, with a systematic check after every write.
Your best article ideas die between the moment they turn up and the moment you sit down to write. Here is the setup that catches them while they are still warm: the voice to empty your head without putting anything in order, a session source to keep the raw material raw, AI to surface the gaps in ten seconds rather than in two days.
Every new format feels like starting over: you reopen the last document, copy, rephrase, and two versions slowly drift apart. The cause isn't a missing tool, it's treating a deliverable as your source of truth. How to install a reusable layer between your sources and your documents, and what AI gains from it.
You can feel that a piece of writing or a decision isn't right yet, without being able to say why. That's where AI earns its place: it turns a vague unease into concrete handles — a blind spot, a shaky assumption, an objection you never dealt with. Which questions get you pushback rather than output, and why this makes human judgement more important, not less.
Your team rebuilds the same product model for every question, every bug, every tender. Here is how to write it down once: several dozen objects, a few hundred rules, under six hours. And above all how to know you have finished — the three stopping criteria that look like proof of completeness and prove nothing, plus the one that holds.
Hiring a PO to hold the backlog and sit between the business and the developers? You are optimising a circuit that is already obsolete. This piece takes apart the split between the people who do the thinking about the product and the people who execute it: why it degrades quality, why a backlog cannot support a profession, and why AI removes the last excuse for living with it.
AI raises the capacity to build, not the capacity to decide. Developers move up towards product; PMs move down towards building. The shift blurs roles without dissolving responsibilities. A full pass over what AI makes ordinary in product management, what stays hard, and a catalogue of emerging roles with the real risk attached to each.
Four days building a real product with Claude Code — 180 commits, starting from nothing. What it shows: the speed that goes to your head, the traps the AI creates on its own, what tests change when you haven't written the code yourself, and how far a PM can go without stepping outside their remit. A field report, not a doctrine.
Producing code faster is worth nothing if nobody understands what got built. AI automates precisely the tasks that used to train junior developers, and an error that lands too late no longer teaches anything once the system has grown too big to analyse. A few concrete anchors for staying in control: clear contracts between APIs, tests tied to the functional need, rebuildability as a quality bar rather than raw delivery speed.
Your documents never say everything. The fine-grained understanding of what happens on the ground stays in the PM's head. Session sources open a channel for pouring that informal knowledge into an AI Context — a hallway remark, a nuance picked up from a customer, a tension just starting to show — and turn dozens of micro-signals into notes, assumptions and better-framed decisions.
Your tools file information away neatly, but they never build up what that information teaches you. This piece explains why the future of the information system is not a better AI-assisted form, but a shift towards `Contexts`: portable, governed units of memory that connect sources, decisions and reasoning instead of merely storing them.
Do you lose half an hour in a test environment just to answer a product question on Slack? That hidden cost disappears once AI can query the source code, the real truth about how the product behaves. Answers grounded in evidence — functions, tests, commits — rather than in documentation that has fallen behind. Provided the code speaks the language of the business.
Do you lose the thread the moment you reopen a conversation with an AI about something that has been running for weeks? This article lifts the lid on a structured memory system: the difference between the goal and the attention of the moment, the directives, the offline queue, the three memories (log, synthesis, checkpoints) and the cycle of a session. Enough to see how an AI can genuinely remember a mission.