The short version
I'm a senior full-stack engineer in Davao City, Philippines. I've been shipping production web applications since 2014: Laravel and PHP on the backend, React, Vue and Inertia on the frontend, and the queues, WebSockets and CI that hold them together.
What I get called in for
Looking back over ten years, the same kind of job keeps finding me: the feature that has been "almost done" for months.
- An invoice PDF generator had blocked a client team for about four months. Every fix for one invoice shape broke another. I replaced the special cases with a configuration-driven layout engine that handles long descriptions, taxes, payments and deductions without anyone touching the code.
- A chunked file upload had defeated another developer for about four months. I wrote it from scratch in PHP and JavaScript and shipped it inside a recruitment and examination platform.
- A Python platform crashed whenever someone paged through a few million profiles, because it loaded the whole result set into memory first. I fixed the pagination and daily operations stopped falling over.
None of these were glamorous. They were all blocking real people, and they all needed someone to slow down, read what was actually happening, and then build the boring, correct thing.
How I work
- Boundaries first. I reach for domain-driven design and ports and adapters when a codebase has to outlive its first framework version. I led one client's move from a tangled legacy app to a modular, hexagonal monorepo, and development got noticeably faster once the modules stopped knowing about each other.
- End to end. Schema, REST API, queues, WebSockets, automated tests, pipeline. I'd rather own a feature all the way to production than hand over half of it.
- Tests are part of the feature. Pest and PHPUnit on the PHP side, Vitest and Playwright on the JavaScript side. This site has more than 300.
- I write things down. Specs before code, docs with the package, and posts here when I learn something worth keeping.
What I build when nobody is paying me
My open source work is where I try ideas properly: Inertia Live makes Inertia pages update in real time from event-sourcing projections, and laraversine does exact nearest-location search in plain SQL. The work page has the full list, each with the problem and the reasoning.
Working with me
I'm open to part-time and contract remote roles, working from UTC+8. I speak English, Filipino and Bisaya. If you have something stuck, or something that needs to be built so it stays built, tell me about it or grab my résumé.