Hi. I do two things:
I write software and help
engineers use AI in real work.
I've spent my career building full-stack web software. These days mostly in Elixir and Phoenix, but I'm also comfortable with Node and TypeScript. I take on full-stack contracts when teams need an extra set of senior eyes.
I've also been working with agentic engineering daily since close to the start of it. I share what I've learned with other software professionals: where these tools help, where they get in the way, and how to think clearly about them in real engineering work.
Senior engineering work
Full-stack Elixir & Phoenix, with regular forays into Node and TypeScript. Greenfield product builds, backend systems, and rescue work on codebases that have outgrown their original shape. Picking up unfamiliar languages quickly is part of the job.
Sparring on AI
Sitting down with your team and looking honestly at where AI fits in what you're already doing: what is worth automating, where your existing data might mean more, and where the current tooling runs past the reality.
Talks
Talks for engineering audiences about what it is actually like to lean heavily into AI day to day. My setup, my mental model, the parts that changed, and the bits I had to unlearn.
A couple of things to know that cut across both sides of the work.
-
Real software, real experience. What I know about AI comes from shipping production code with it daily, not from a feed full of demos and screenshotted prompts.
-
Honest about the limits. AI is a tool. I'll tell you where it helps your team and where it'll slow you down.
-
Full-stack with a capital F. My full-stack experience runs past code: deployments, databases, UX, and UI design.
Working on something interesting? Tell me about it.
Email's the best way. I read everything; usually reply within a day or two.
[email protected]