Why "It works on my machine" is a leadership failure
Deployment shouldn't be a personality trait. A short rant about why reproducible environments are a team sport, and how to get there in 30 days.
Read more โBackend developer and consulting architect in Austin, TX. 11 years shipping products from a blank repo to production at scale โ and leading the teams that make it happen.
Years building
Products shipped
Engineers led
Avg. uptime
Most of my career has been inside product startups โ both as a full-time engineering lead and as a consulting architect parachuting in to rescue projects that stalled. I'm the person who asks "what are we optimizing for?" on day one, and "is it deployed yet?" on day 30.
I love the mess of early-stage chaos: vague requirements, tight deadlines, a team of three. I thrive there. I've designed systems that scaled to 50M requests/day, mentored junior devs into senior roles, and I still get a kick out of a clean migration with zero downtime.
UT Austin, 2013
Central time, remote-friendly
And a stubborn refusal to ship crappy code
Go, Node, Python. APIs that stay fast even when your user base grows 10x overnight.
Hiring, roadmapping, and trade-off talks. I make the hard calls so your team can move fast.
I've been employee #3 twice and #1 once. Lean sprints, scrappy solving, zero bureaucracy.
Audits, system design, and rescue plans. I walk into chaos and leave behind something boring and reliable.
Product definition to CI/CD pipeline. I'm comfortable owning the full lifecycle โ and I document everything too.
Shipping beats talking. Every sprint ends with something deployed and measurable.
Rebuilt a stalled financial reporting API that was 6 months behind. Migrated to event-driven architecture, cut p95 latency from 1.2s to 180ms.
Led a team of 6 as fractional CTO. Scaled from 2,000 to 50,000 active patients in 8 months without any major outages.
Designed a payment reconciliation system that handled 2M+ transactions/month with zero discrepancies. Saved the company ~$180K/yr in manual audit.
"Milo took our backend from 'please don't crash' to 'we brag about it in investor meetings.' He's rare โ equally strong at writing code and setting strategy."
"We hired Milo for 6 weeks and kept him for 9 months. He mentored our juniors, shipped our core API, and left documentation we still reference daily."
I currently have capacity for one new consulting engagement starting next month. Let's talk about what you're building โ and what's blocking you.
Deployment shouldn't be a personality trait. A short rant about why reproducible environments are a team sport, and how to get there in 30 days.
Read more โTraffic doesn't matter. Revenue per request does. The practical questions that turn vague startup ideas into boringly stable architecture.
Read more โ