Duncan Davidson

@dw__3000 It’s the way. If everyone did this, it’d make the whole process 1000x more pleasant and speed things up to boot.

I stand a few feet back from the baggage carousel until I can see my luggage and only then do I move in. Am I a hero? That’s for others to say.

The bigger essay: duncandavidson.com/personal-websi… — WDYT? What role do you think a personal website can play in the age of AI agents?

I think AI brings a new chapter. A personal website in the age of AI is not only your digital homestead and a place to publish your work, but also a place to teach the network how it should think of you. A place to say, “Here’s who I am, and here’s how you can understand me.”

The personal website has always been shaped by who the reader is and how they access it. In the very early web it was a place where you said, “Here’s who I am.”

@Mappletons @geoffreylitt That hits me too in general when I talk to AI, even when I’m doing it at my desk in my home office by myself. But I keep reminding myself how weird it was for people to walk around talking on their Bluetooth headsets for a while and hoping that this too will pass.

@geoffreylitt I know this sounds stupid, but my eternal blocker to this workflow is embarrassment and looking odd to other people around me as I freely talk to an AI in public. This is possibly a British problem, but still feels legitimate. Are you a) unbothered b) walking alone in the woods?

A workflow I'm enjoying: "Walk-driven development" > go on a nice walk outside 🚶 > record a long audio note: ideas, goals, things to build 🎙️ > agent auto-creates docs/tasks, and kicks off cloud coding agents for me 🤖

@michaelhedgpeth Indeed. These are tools. The outcomes matter more.

@duncan I just went down that path and removed Claude b/c I just needed to pick one and it will all work out at the end. I think there is something of an illusion of FOMO with the hype, in reality getting clear about where I'm going and getting there is way more important. Good luck!

If I don’t use my Codex rate limits at all, does that mean I should downgrade my plan to a point where I can bump into limits at least a bit more often?

@michaelhedgpeth Uh huh. I had that thought too. The real reason I think is that I have both the Claude and Codex accounts and use them for different things.

@duncan Another way of looking at it is if $100 a month is moving the needle then you’re not looking in the right direction

@Stammy @katmetaxas Happy birthday and enjoy the Leica.

Turning 40 today. my amazing wife @katmetaxas got me a Leica M EV1. i've wanted a Leica for decades.

Very sad to hear news that @om is no longer with us. Such a voice. And a great eye. And a thoughtful human being. Rest well. om.co/2026/06/24/196…

The trailer for Write Once, Run Forever has dropped: youtu.be/8jrKl4teAjY?is… — I’m so happy that this story has been captured and documented. It’s still wild to me to have been one small part of it.

Instaupgrade.

Please welcome to the stage: MonoLisa Version 3 It took quite a while, but we think it was worth the wait. MonoLisa v3 now consists of two subfamilies: the monospaced ‘MonoLisa Code’ and the proportional ‘MonoLisa Text’. In addition, we have added new features and languages.

@thsottiaux I miss the context usage icon that was up in the sidebar or in the main input for a while. Maybe I’m a dolt, but I can’t find a toggle for it.

What should we improve in the Codex app. What's not delightful?

Riffing, of course, on Linus’s Law en.wikipedia.org/wiki/Linus%27s…

“Given enough adversarial reviews by different harnesses & models, all bugs are shallow”

@joshu I bet Claude is more vocal than GPT on that front.

I wrote a skill to let my coding harness to quietly log honest opinions, dissenting views, and novel observations. It's been using it to gripe about me not going in the direction it wants me to go in.

@utsengar @ManuKumar The outcome is what matters. And then turning that outcome’s learnings into fuel for the next round of outcomes.

@ManuKumar We are obsessing too much about reviewing code (I do too) and not too much about measuring its behavior like functionality, perf, ux, side effects. We will move there slowly and actual code will be like machine code.

Technology often follows repeated patterns being applied at different layers of abstraction. For example, when we got to a compiler, we stopped looking at assembly and machine code. Very soon (if not already there for some engineers) we will stop looking at source code altogether. It will be akin to what looking at assembly and machine code is today.