Ongoing work across a family of laboratory information systems for public health lab clients — sample intake, testing workflow, results, and reporting. Started as feature work, grew into full production ownership: I am usually the one who gets paged when it breaks.
- Maintain a production laboratory information system for a government client — 4+ years in, six-figure line count, several integrated services, real staff depending on it daily
- First responder when it breaks in production: SSH in, read the logs, trace the failure across services, ship the fix — same day, not "next sprint"
- Comfortable making direct database fixes on production when the situation calls for it, with a strict confirm-before-write habit
- Built and shipped sibling systems for related lab-network clients: sample/specimen tracking, surveillance data, staff competency records, quality management
- Delivered an end-to-end technical-training management system (registration, payment, e-signed certificates with QR verification) using Laravel + FilamentPHP
- Traced and fixed silent data-loss bugs caused by mismatched form field names between near-duplicate module variants — the kind of bug that only shows up after weeks of nobody noticing
- Diagnosed and fixed a filesystem-permission fault that was causing intermittent 500 errors across a live system
- Laravel
- FilamentPHP
- PHP
- MySQL
- Vue.js
- Linux
- Incident Response
2024 — Present
2+ yrs