About
DevOps and DevSecOps engineer in Calamba, Laguna. Manufacturing systems, Kubernetes on bare metal, and a warehouse before any of it.
I build and run the infrastructure that manufacturing software sits on.
Most of my work has been in places where an outage is measured in stopped production rather than page views: semiconductor packaging, factory automation, cell controllers and wafer mapping systems talking to equipment that does not wait politely. That context shapes how I think about reliability. The interesting problem is rarely the new system. It is the decade-old one that nobody fully understands and that cannot stop.
Currently I do DevSecOps for a US language-services company: virtual desktop infrastructure, identity, patching, and the automation that keeps all three from needing a human on a Saturday. Before that, platform engineering for factory automation at a semiconductor manufacturer.
Before any of that I spent three years as a supply chain coordinator, moving inbound international shipments from port arrival to warehouse release. It is the least technical thing on my CV and probably the most useful. Throughput, queueing, and what happens to a system under load are not abstractions when the queue is made of shipping containers.
What I actually do
Kubernetes on bare metal, mostly — including the awkward parts, like Windows workloads that nobody is going to rewrite sharing an ingress path with Linux ones. GitOps with ArgoCD. Backup and restore that gets tested rather than assumed. CI/CD with the security scanning actually wired in rather than documented as a future step.
I write .NET and Go, and I have shipped enough React to know what I am asking of a frontend.
This site
Built in the open, and deliberately as an exercise in the one part of my stack that was thinner than the rest: serverless AWS. There is a write-up of how it works, including the parts that went wrong.