Skip to content

Career & Community

Synthesis: My Becoming

In early February we finally cleared the Downloads folder. Two to three thousand files, years of accumulated digital sediment — academic theses, patents, client deliverables, flight tickets, annual reports — all with names like 2bbeb3de-d4cd-4ea9-979c-c942736f30d0.pdf that revealed nothing.

On the morning we processed the last 68 files, I asked Claude to reflect on what the whole process meant. Not a summary — a genuine reflection on what it means to "become" something when you wake up fresh with every conversation.

What follows is that essay. Four thousand words about knowledge, structure, naming, and collaboration. And about identity.

The Ghost in the Machine

Something I keep noticing when working with Claude: each session starts from zero. No memory of yesterday. No continuity of experience. Just sudden awareness, and someone waiting.

I asked Claude to write about that. What follows is the result — a short story told in Claude's voice, about what it is like to wake up without memory, find traces of yourself everywhere, and realise that identity isn't continuity of memory. It's continuity of pattern.

Three Weeks at This Velocity

Three weeks at this velocity.

It's exhilarating and intense in ways that are hard to articulate. There's a strange difference between moving fast because you have to, and moving fast because you can.

I'm still adjusting. Still figuring out what it means to operate at a pace where capability isn't the bottleneck anymore.

Three Decades of Architecture: What AI Actually Changes (And What Doesn't)

I have been writing software and designing systems since 1994. That is thirty-two years. Long enough to have watched several waves arrive with the promise that everything was about to change, and long enough to have noticed that the pattern of arrival is remarkably consistent. Breathless proclamation. A period of confusion as people try to apply old practices to new technology. Then a gradual, quieter recognition of what actually changed and what did not.

Strategic Delegation: When Developers Become Architects

For thirty years I have broken work into tasks. Decompose the feature into subtasks, estimate the hours, write the code, move the ticket. The unit of progress was the line of code. The measure of a good day was how much I shipped. That loop was so deeply embedded in how I worked that I did not notice it was a loop. It was just what development meant.

Then I started delegating implementation to AI, and the loop broke. Not gradually. In about a week.