Build it, don't just talk about it
I'd rather build a thing than describe it. Putting something real in front of people is the fastest way to find out if it works.
I'm a College Teacher at the University of Eastern Pangasinan. On the side, I build websites and small browser tools that use AI to handle the repetitive parts of my work.
I've been coding since 2015. These days I lean a lot on Claude and Gemini, build websites, and write small programs that take busywork off my plate — and off my clients' plates too.
Good teams write things down, talk to each other, and actually finish what they start. If yours does, and you're hiring a developer or IT person, send me a message.
I'd rather build a thing than describe it. Putting something real in front of people is the fastest way to find out if it works.
Clear names, simple structure, notes where the reason isn't obvious. The next person who opens my code — usually me, six months later — thanks me for it.
Security goes in on day one, not after something breaks. Safe defaults and clear access limits, built in early — not patched on later.
If it isn't written down, it didn't happen. I take notes while I'm building — how things work, why I picked this over that — so whoever comes next isn't starting from scratch.
Before teaching, I freelanced. I built small web tools for whoever needed one. Every project taught me something tutorials don't — real data is messier, and real users do things you don't expect.
Teaching changed how I write code. When you have to walk a room of students through it, you stop hiding behind clever names. I write code now that I'd happily put on a slide.
Outside of work, I'm finishing my Master's in Information Technology (Cybersecurity). I trade for fun and build small browser tools whenever something annoys me enough to fix it. My job is in Pangasinan, but home is in Tarlac — where my dog Ginger and my cats Pepper and Tabby keep me company. My partner is based in Manila, and her dog Killer comes along on weekend trips.