I fix broken systems, flaky infrastructure, and slow apps.
30 years of experience. PHP, AWS, legacy systems.
When things stop working, I make them work again. Fast.
Problems I solve
How I work
You show me the problem
Send a message, share a screen, drop me into the repo. Whatever works.
I diagnose quickly
No endless meetings. I dig in, find the root cause, and tell you what's going on.
I fix it or give you a clear path forward
You get a working solution, not a slide deck about one.
No fluff, no overengineering, no wasted time.
Recent work
Fixed production outage affecting thousands of users
Root cause: cascading connection pool exhaustion across microservices
Stabilized multi-server WordPress infrastructure with recurring crashes
Identified memory leaks in custom plugins and misconfigured caching layers
Debugged cross-network MySQL replication issue
Cloud-to-on-prem replication failing silently. Traced to MTU mismatch and packet fragmentation
Reduced AWS cost by identifying misconfigured resources
Oversized instances, forgotten snapshots, and unattached EBS volumes adding up to thousands per month
Recovered broken deployment pipeline under time pressure
CI/CD chain broken by dependency conflict. Fixed and shipped same day
How to work with me
Emergency Fix
Something is broken right now. I'll diagnose and fix it, usually within 24-48 hours.
System Audit
Deep dive into architecture, performance, and risks. You get a clear report with priorities.
Ongoing Support
Priority access, ongoing fixes and improvements. Like having a senior engineer on call.
How I think about software
I help founders and teams build software that's boring in the right ways: simple, stable, and easy to maintain. I'm a full-stack developer with 30 years of experience, and I've learned the hard way that clarity beats cleverness every single time.
I've worked across startups, long-lived business systems, and products that had to survive real users, real traffic, and real constraints. I mostly build with TypeScript, Python, PHP and React, but tools are secondary. Choosing the right level of complexity is the actual job.
These days I split my time between consulting and building my own products. I care about clean architecture, long-term maintainability, and shipping things that make sense in the real world, not just in slides, trends, or hype cycles.
12 Projects in 12 Months
I spent too many years overanalyzing instead of shipping. So in January 2026, I started a challenge: launch one project every month for a year.
Got a problem?
Send me a short description. I'll tell you if I can help.