The long version.
Lead full-stack software engineer, thirteen years in, based in Orlando — mostly with digital agencies and startups. I started in aviation, then moved into software engineering and have been shipping web applications ever since.
Right now
- 13 years in
Lead Full-Stack Software Engineer
@ Orlando, Florida
- Full-stack applications
- cloud infrastructure
- Since 2025
VERA
Lead Software Engineer · Orlando
- AWS
- Terraform
- Express
- MongoDB
- React
- Unity
Projects
I started my career in aviation, then moved into software engineering. Different industry, same instinct: work out what actually has to hold before anyone commits to anything.
Since then the work has moved between agencies, startups, and in-house teams — full-stack throughout, from the interface to the infrastructure underneath, and always as part of a team rather than instead of one. Two of those years were spent teaching full-stack JavaScript, which is still the best thing I’ve done for the way I read other people’s code.
Right now I’m the lead engineer on VERA, a platform that runs behavioural and VR studies end to end, and I build HoloMetrics — portfolio analytics for trading card collections — on my own time.
A good deal of the rest is public. SchemaPress brings structured content types to WordPress, a headless starter turns Advanced Custom Fields data into a REST contract a front end can rely on, and OfferPilot sits on a model-agnostic generation layer. Open source is where I try the things client work can’t carry the risk of, and where the reading goes both ways.
Thirteen years of moving between those settings has left a short list of positions I keep returning to. They’re arguable, and most of them have been argued — which is rather the point.
How I work
Data model first
Most debates about which tools to use are really about what the data means. Agree on that first and the rest gets easier.
Scope is a decision
Choosing what not to build matters as much as what you do build, and it’s far cheaper to decide early than undo it later.
Boring foundations
Try new tools where they’re easy to swap out. For the core parts everything else relies on, stick with what’s proven.
Reviews that matter
Good review feedback points out what will be hard to change later, and it’s just as welcome from a junior as from a lead.
Built to hand over
Whether it goes to a teammate or a client with no developer, handing it over is part of the job, not an add-on at the end.
Checklists over memory
A habit from aviation: important steps get written down, since the one you forget is never the one you expect to forget.