AI doesn’t make the underlying work better. It doesn’t make my judgment sharper, my code cleaner, or my decisions more correct. What it changes is the friction around the work.

This post is about which parts of the daily loop AI handles well, which parts still need human judgment, and what changes when the friction drops enough for the loop to run every day.

The loop, in plain terms

Most working engineers run some version of a daily loop. The pieces have different names in different places, but the shape is roughly:

1. Capture — what did I do? What did I notice? What’s still open?
2. Plan — what am I doing tomorrow? What’s the priority order?
3. Execute — the actual work. Code. Reviews. Conversations.
4. Report — what did I do this week, and how do I tell the relevant audiences?

The middle of that loop — the actual work — is where the value lives. The other three are supporting infrastructure. They’re how the value becomes legible to your future self, your team, and your stakeholders.

The thing AI has changed for me, more than anything else, is making those supporting steps cheap enough to do daily. Not better-done — just easier to start.

Where AI is unambiguously good

Three jobs in the loop where I now reliably hand work to the agent without second-guessing.

Structuring loose input

If I dump a stream-of-consciousness paragraph at the agent — “today I worked on the auth thing, also looked at the deploy issue, talked to the client about the rate-limit feature, started exploring whether we even need rate limiting at the gateway” — the agent turns it into a structured journal entry without losing anything. Three categories: what I did, what I noticed, what’s open. Bullet form. Concrete enough to be searchable later.

I could do that conversion myself. It would take ten minutes. The agent does it in fifteen seconds. The difference isn’t that the agent’s structuring is better than mine — it’s that I’ll do it, because the cost dropped from ten minutes to fifteen seconds.

The same applies to taking a chat-thread context file and pulling out the three things relevant to my work. Or taking a long pull-request description and summarizing what changed. Structuring loose input is the easiest case for AI assistance and the one I lean on most.

Reformatting for different audiences

I used to write the same week’s worth of work three different ways: one version for my manager, one for the team channel, one for my own self-assessment. Each version emphasized different things. Each one took twenty minutes. Two of those twenty-minute blocks were essentially the same content rephrased — and yet I had to do all three because the audiences want different things.

The agent does that reformatting cleanly. One source — the journal entries — multiple outputs. Manager report leads with outcomes and risks. Team report leads with what’s in flight and where help is needed. Self-assessment leads with patterns and friction. Same week, three lenses.

Searching the archive

Six months of journal entries is a lot of plain text to grep through manually. “When did I first try X? What did I conclude about Y? Did I ever resolve the thing with Z?” These are questions a human can answer with twenty minutes of clicking around or thirty seconds of asking the agent.

The agent is reading the entries faster than I can and matching against the question. That speedup is the difference between “I’ll look that up later” and “I’ll look that up now.” The archive becomes interactive, which is the only reason an archive is worth keeping in the first place.

Lowering the cadence threshold

The fourth thing AI does well is the meta-effect of the first three: it lowers the cadence threshold of the entire loop.

Before, capture was a five-to-ten-minute task. I’d do it some days. Plan was fifteen minutes. I’d do it some weeks. Report was an hour or two. I’d do it under deadline.

Now, capture is two minutes — I dump the day’s notes, the agent structures them. Plan is three minutes — the agent reads the last few entries, suggests priorities, I edit. Report is five minutes — same source, three lenses, click to send.

The wall-clock cost dropped enough that the entire loop moves daily instead of weekly, and weekly instead of monthly. The compounded benefit is that decisions, problems, and patterns are now visible while they’re still actionable. A pattern I’d have noticed six months later, I now notice within a week.

That’s the structural change. It isn’t about doing the same work faster. It’s about being able to do the work at the right cadence — which I couldn’t, before.

Where AI is unambiguously not yet good

Three jobs in the same loop where I do not hand work to the agent. These are still mine.

Deciding what matters

The agent is good at structuring what I tell it I did. It is bad at deciding which thing I did matters most. That decision depends on context the agent doesn’t have — what my manager will care about next quarter, which problem on the team is politically charged, which technical debt is about to bite us, which conversation in the hallway shifted my read of a project.

I’ve tried letting the agent prioritize. The result is plausible-but-wrong prioritization. The bullets are real; the ranking is generic. The same thing happens in manager reports: the draft can be polished and still highlight the wrong two things, hedge the wrong problem, or miss the political weight of a phrase.

So when I plan or report, the agent suggests bullets and drafts. I rerank and edit. That judgment is the actual work; the draft is the cheap part the agent saved me.

Telling the truth about myself

The journal entries that have the most long-term value are the ones where I admit something uncomfortable about my own week. I made a worse decision than I’d thought. I procrastinated. I was wrong about how a conversation went. The agent will not produce those sentences. It can’t — the only person who knows the uncomfortable truth is me.

So when I capture a day, the agent’s structured output is the scaffolding. Inside that scaffolding, I write the one or two lines that are actually honest. Those are mine. They’re the part that pays back, six months later, when I read the entry and find the small piece of self-knowledge that the agent’s polished version would have hidden.

I want to be explicit about this: the agent is not a substitute for the introspective work. It’s a substitute for the clerical work around the introspective work. Confusing the two would erode the journal’s value entirely.

The honest version of this

I want to close with something I find easy to overstate.

The setup I described isn’t magic. There are days when the agent’s outputs are noisy and I throw them away. There are weeks when I skip the loop anyway because I’m tired or busy or the work has been chaotic. The system isn’t a productivity hack; it’s a small, quiet infrastructure that mostly works and sometimes doesn’t.

The reason I think it’s worth describing is that the direction of change has been consistent. Every iteration of this setup has produced more useful entries, sharper plans, and reports my audiences actually read. The friction keeps dropping. The cadence keeps tightening. The journal keeps becoming a more useful artifact instead of a less useful one.

That’s the whole win. Not “AI changed everything.” Just: a thing I knew I should be doing daily for years, that I now actually do daily, because the cost dropped enough that the habit could form. Some of that is discipline; most of it is the cost.