I’m a full-stack developer based in Eastern Visayas, Philippines. I work on AI-integrated web products, internal tools, and the operational systems around them. The part I care about most starts after the demo works, when real people depend on the software to get through their day. That’s the work I’m here for, and most of what I believe about building comes from staying past launch instead of walking away at it.
Where I learned the real job
From 2022 to 2024 I worked at Litecloud PH on CERPSYS, a production ERP for a multi-branch rental business. I started on the early modules and ended up responsible for the whole thing. Writing the first version was the easy half. Shipping was the midpoint, not the finish line.
The real job was keeping a live business system running for people who had no fallback: fitting it to the workflows they already trusted instead of forcing new ones on them, protecting data that a branch’s whole day depended on, fixing the things that only surface under daily use, and changing the system without breaking the people relying on it. You learn a different kind of care when a bad deploy means someone can’t invoice the customer standing at the counter.
How that shows up in my work
Those years set my defaults. I keep scope small and testable instead of promising a long feature list. I write decisions down, so the reasoning outlives the moment I made it. I surface risk early, while it’s still cheap to change course. I keep a hard line between what I’ve measured and what I’m assuming, and I tell you which is which. And I reach for AI only where it makes the product or the engineering genuinely better, not because it’s expected.
You can inspect the work
I’d rather you check than take my word for it. Most of what I do is open to look at:
- AlgoLens is live in open beta. You can use it yourself right now, not just read about it.
- FloatWatch has public source, including the unfinished parts. It’s a Building-stage prototype, tested so far only on my own Android device. It hasn’t shipped, and it hasn’t been field-tested with real operators yet. I keep the rough edges visible on purpose.
- My case studies explain the constraints I worked under and the mistakes I made, not only the parts that went well.
- My writing documents tests that changed my mind, the times the data contradicted what I expected.
- Where a client’s permission allows, I share redacted evidence and references.
The person behind the commits
There’s a person behind the commits, not just a list of shipped features. If we end up working together, the specifics come out soon enough.
Start a project
If you’re building something and you want a developer who’ll ship it and then stay to keep it running, that’s the part I like most.