Starting a journal

I spend most of my week somewhere between two worlds: the engineering detail of building agentic systems, and the boardroom conversation about what they actually mean for a business. This journal is where those two worlds get to talk to each other in public.

What this is

A weekly note. Short enough to read between meetings, specific enough to be worth your time. Mostly on three things:

  • Agentic AI in production — what works, what quietly breaks, and the plumbing in between.
  • Capital markets technology — reference data, regulatory change, buy-side operations, settlement.
  • Building in the open — notes from the ventures I'm working on, including the bits that don't go to plan.

What it isn't

It isn't a hype feed. If something is genuinely useful I'll say so; if it's a solution looking for a problem, I'll say that too. The framing I keep coming back to is governance before glamour, plumbing before prompts, people before platforms — and I'd rather be useful than fashionable.

Say something back

Every post is open for comments — sign in with GitHub and the conversation is yours. Disagree, sharpen, or send me down a better path. That's the point of writing in the open.

See you next week.

> ./comments --thread
Comments not wired up yet.
1. Enable Discussions on your GitHub repo (Settings → Features).
2. Install the giscus app: github.com/apps/giscus.
3. Go to giscus.app, enter your repo, and copy the four values it generates.
4. Paste them into .env.local (see .env.example) and redeploy.
> cd ..