On AI.
Where I use it, where I don't, and how I keep a human in the loop.
What I use
At work, ChatGPT and Cursor are my daily drivers. Away from work, I use Gemini for research and ideas.
For building, I use Claude Code. Prototypes, tools, small projects: things I want to exist but would otherwise take long enough to build that they'd stay ideas. It shortens the distance between intention and a working thing.
It's changed how I work professionally
I work in digital innovation at Sky and NBCUniversal, focused on customer care technology across our streaming platforms: Peacock, NOW, WOW and SkyShowtime. AI isn't theoretical in that context. It shapes how customers get help, how teams process feedback, how we detect friction at scale.
I've built internal proofs of concept with it. Streamsight, a RAG system for turning workplace insights into a searchable knowledge base, came directly from this environment. The through-line is always the same: use AI to reduce the distance between having a question and getting a useful answer.
The hardest part is never the model. It's the judgment layer: knowing when an answer is good enough, when it's confidently wrong, and when a human needs to be in the loop. That doesn't get automated.
East Village Hub is the live experiment
I've built an agentic system on Hermes, working with ChatGPT, to manage East Village Hub. I'm part way through handing the day-to-day to a team of agents. They find and list events and local info, write and publish news and the weekly digest, handle live issues and Ask Rosie, and make code changes, fixes and deploys.
Everything public goes through me. The agents do the operating. I stay accountable for what goes out.
Art and images are a hard no
I don't use generative tools for images or art. Not on this site, and not on East Village Hub. Making a visual that looks like craft without any craft in it doesn't interest me.
Words and code are different. I use AI to draft, build and do the work, and a human stays accountable for everything that goes out under my name.
How this site was made
I built this site with Claude Code. The copy, including this page, was drafted with AI and edited by me.
On the hype
Most AI discourse is theatre. Announcements engineered for attention, demos that don't survive contact with real users, breathless predictions that confuse capability with deployment.
I'm genuinely excited about what's happening. I wouldn't build with it if I wasn't. But excitement isn't the same as credulity. The interesting stuff is always quieter: a tool that actually reduces friction, a workflow that saves real time, a prototype that answers a question you couldn't answer before.
I'm more interested in what works than in what's impressive.