productivity

I ran an autonomous agent loop overnight — 43 waves, ~270 dispatches, ~250 vault files produced. Here's what I learned about building systems that work while you sleep.

A simple heuristic for deciding how often to review anything: pick the longest interval where being late by one full cycle is still fine.

Most TODO systems fail from too many items, not too few. A four-test intake filter for what deserves your attention.

Not every goal is a flywheel. The most common mistake in personal systems is treating a checklist as something that compounds.

Most people scan competitors for positioning. I scan them for transferable patterns — and route each steal to every domain it applies to.

The difference between protecting a commitment and hoarding optionality

Most people use AI like a tool. Here's what thinking with AI actually looks like — and the skills that make the difference.

Stop asking your AI single questions. Start thinking out loud with it. Let half-formed ideas land. The AI holds the structure so you can stay in flow.

Don't filter during capture. Capture is cheap. Ideas are expensive. The cull is where quality happens.

Most task systems are binary, but a third class exists — tasks triggered by external notifications — and managing them like a backlog item is the wrong move entirely.

On the difference between eliminating friction and eliminating anxiety — and how to know when you've crossed the line.

I spent an afternoon researching AI tools for personal life management. The conclusion was that I should stop looking.

Most PKM tools are procrastination with better aesthetics. The problem isn't the software — it's that filing a note feels like understanding it.

Not productivity. Something stranger — the cognitive texture of days when the bottleneck shifts from execution to articulation.

Building tools to support your work can quietly become a substitute for the work itself.

A coding assistant quietly made three productivity apps redundant. Not by replacing them — by making context collapse the boundaries between them.

On why the blank page stopped being the hard part.

I kept missing things at the end of AI sessions. So I stopped relying on willpower and systematised the nudge instead.

The cognitive offloading problem is real. The governance response mostly isn't. There's a specific mechanism at work, and it has a specific fix.

Most consultants arrive at a new firm and learn their tools from colleagues. I tried something different.

Most AI tooling debates are actually recurrence debates. The question isn't whether to build — it's how many times you'll need it.

Walking meetings, voice input, and location changes unlock cognitive advantages desktop workflows can't access.

Why I use Claude Code for everything except coding: cognitive compiler for strategy, decisions, and understanding.