I build the systems that keep businesses running.
Payment flows, automations, queues, internal tooling, and the ongoing work of improving older codebases. I focus on the infrastructure that protects revenue and replaces manual effort with reliable software.
Recent Impact
- Production stack maintained 4+ years Every part of a 40-person travel company — sales, operations, payments, ACH, contractor tools — runs on a platform I keep healthy and shipping every day.
- Live platform migrations, no noticed downtime PHP 5.6 → 8, MySQL 5.7 → 8.4 LTS, CentOS 7 → Rocky Linux 9, and payments across TranSafe → Monetra → NMI — all delivered with the company still open for business.
- Revenue-protecting automation Cancellation systems, payment notifications, NACHA-formatted ACH batches to M&T Bank, and financial workflows that replaced manual intervention with reliable software.
- Measurable performance gains Brought key workflows from 5–10 seconds down to under one second, alongside ongoing refactoring that improved long-term maintainability.
Tech Stack
- Core stack: PHP, MySQL, JavaScript, Linux, REST APIs
- Systems work: queue processing, cron-driven jobs, caching layers, reporting, and operational tooling
- Integrations: payment processors, SMS providers, email services, and internal platform APIs
- Engineering habits: refactoring, documentation, bug prevention, security hardening, and performance optimization
Selected Systems
Patterns I’ve delivered repeatedly in production.
- Automations that run without supervision Background workflows for cancellations, notifications, and routine processes that execute reliably around the clock.
- Payment and financial infrastructure Processing integrations, encrypted financial data handling, and the supporting systems that protect revenue.
- Internal platforms and admin tooling Tools for reservation management, contractor workflows, reporting, expense systems, and operational visibility.
- Legacy modernization through steady refactoring Incremental cleanup that makes an older codebase faster, safer, and easier to ship from.
Work Style
- Start from the business problem: understand what failure costs before designing the fix
- Build systems, not patches: create the mechanism that prevents repeat work
- Document while shipping: reduce fragility for future maintainers
- Refactor as part of delivery: leave the codebase healthier than I found it, every time
Work History Snapshot
Foundation and large-scale refactoring
Heavy modernization, infrastructure work, and the first PCI-conscious payment-processing integration.
Feature growth and platform migration
New operational features, the PHP 5.6 → 8 migration, alert systems, and security-sensitive financial tooling.
System enhancement and cleanup
Codebase health work — refactoring, deprecation removal, and broad system-wide improvements that paid down debt the next year leaned on.
Infrastructure-heavy delivery
Queue-backed automation, SMS integration, and major performance gains, alongside steady refactoring across the platform.
Orchestration platform and live cutovers
Built status.etadventures.com — a Python and Flask dashboard probing 13 ETA servers — plus a sudo-scoped, 1Password-injected agent-orchestration host. Customer portal modernization across NMI, and the MySQL 5.7 → 8.4 LTS and CentOS 7 → Rocky Linux 9 production cutovers.