3 posts tagged with "Story"

Reading back everything you said to an agent today sounds about as much fun as writing your own standup notes.

But if you don't, tomorrow it opens with "Hi, what project are you working on?" all over again.

Rather than re-explaining yourself every morning, let the work you finished land in a library you own, gather it once a day, and let the next agent pick up from there.

For the past year I've been moving between Claude Code, Codex and OpenCode, and I've written the same set of conventions three times: one copy in this agent's directory, one in that agent's config, one in my own head. Every time I thought that was finally settled. Then I'd open a different terminal and start explaining again.

Something else was going on at the same time. The work we actually finished together was scattered. Some of it in session logs, some in scratch files, some in a vendor's database, the copy I can read but can't take with me.

One of those looks like an efficiency problem and the other like an ownership problem. They're two ends of the same thing.

You work with agents all day, and when you stop, the chat box is the only thing that remembers.

When one entry is missing, the first thing that breaks is often not the monthly report. It is your trust in the ledger.

You know it is already inaccurate. The next time you open it, adding that one entry is not enough. Did you miss others before it? Did the same purchase appear once in each of two channels? Was the original expense reversed after a refund arrived? If any of those questions remains unanswered, continuing feels like adding numbers to a crooked table.

That is where many people stop. They still want a record of their spending, but they do not want to spend more time on a result they no longer trust.

I studied architecture. Then I switched careers and became a programmer. Later I left everything familiar behind and moved to Singapore, where I now work as a fullstack / DevOps engineer.