A product
studio of one.
Production Rails since 2005. Two books, thirty-plus shipped applications, one engineer you actually work with.
Rails 5 Revealed · 2016
VegasNearMe
VegasNearMe brings shows, attractions, dining, nightlife, maps, and booking paths into one Rails platform. Partner feeds are normalised once, then published across the website, app, and internal editorial tools.
Alan is extremely talented and is just a pleasure to work with. He's always thinking outside the box; a huge asset to any company he works with.
I've had the pleasure of working with Alan in several capacities over many years. Alan is the best kind of developer to work with in my opinion: not only does he understand technology and what he's capable of building, but he makes sure he understands why he's building something.
I've had the privilege of working with Alan across three distinct chapters of my career. Most recently, when founding AgendaScope, I made it clear I wouldn't proceed unless Alan joined the team as my CTO.
Beyond being one of the best and most trustworthy professionals I've encountered, Alan is a meticulous software craftsman who combines remarkable speed with proper engineering practices.
Index






Twenty-five years building web applications—as a developer, CTO, founder, and consultant on product architecture and delivery for larger companies.
In 2007 I wrote one of the very first Ruby on Rails books, Practical Rails Social Networking Sites. Rails 5 Revealed followed in 2016. Rails has been my primary tool for two decades; I've been shipping Elixir and Phoenix LiveView in production since the early releases.
XenoCode is deliberately a bureau of one. When you hire me, you work with me — not a revolving door of junior developers, not a project manager reading status off a Jira board.
Bibliography
Practical Rails Social Networking Sites
One of the earliest books on Ruby on Rails: a practical guide to building a social application while the framework and its conventions were still new.
Rails 5 Revealed
A focused tour of what actually changed in Rails 5 and a pragmatic take on what to adopt versus what to ignore.
How I work
Sprint / Defined idea to live app
Four weeks to turn a defined product idea into a deployed application people can register for and use. Includes architecture, implementation, deployment, and a written handover.
Build / Embedded product engineering
I join as a senior engineer or acting CTO for three to twelve months, own the architecture and delivery, and leave a Rails or Phoenix codebase the next team can operate.
Audit / AI-assisted codebase
A one-to-two-week review of an AI-assisted or early-stage codebase, covering security, scalability, and maintainability. You receive ranked findings and a concrete remediation plan before real users depend on it.
Tell me
what you're
building.
A paragraph is enough: what exists, what is stuck, and what you want to ship. I'll reply within two working days.
Prefer a call? Book thirty minutes. No sales deck; we'll talk through the product and decide whether I can help.