About
I've been writing software for a little over twenty years. Lately a good chunk of it writes itself, or close enough that I've had to rethink what the job even is.
I'm James, an engineer in Austin. I spend my days building inside a big enterprise and my nights building things of my own, mostly along the seam where regular software meets AI.
What I do
Twenty years gets you a long, unglamorous list: mobile apps, e-commerce platforms, databases, APIs, frontends, and most of the languages you'd use to wire them together. Wherever the problem happened to be, that's where I ended up. I stopped keeping the list a while ago.
These days I'm heads-down on agentic engineering: treating AI agents as force multipliers, not party tricks. At work that mostly means arbitrage: finishing in an afternoon what used to eat a week. After hours, I point the same tools at my own projects.
I'm not a thought leader, and I'd be a little embarrassed to be called one. I'm just an engineer who writes down what actually works.
What you'll find here
This is where I write up the tools and workflows I'm actually using: Claude Code deep dives, agentic patterns, whatever dev tooling I've been living in that week. If it earned a spot in my setup, it probably ends up here.
When I'm not in front of a terminal, I'm usually out on a trail or on a bike somewhere in the Texas hill country. Or, let's be honest, back at a different terminal.
Connect
I'm scattered across most of the usual places.