About

19 year old IT student,
building at the intersection
of design and engineering.

I'm based in Pangasinan and I'm in my second year of Information Technology at the University of Pangasinan. I finished senior high school in May 2024 at Saint John's Cathedral School in Dagupan City, and I stayed on the dean's list every year from grade ten through grade twelve.

Long before I wrote my first line of code I was the person friends came to when their phone or laptop started acting up, so fixing other people's machines taught me to be patient and to actually listen to the problem instead of guessing. I still do that, and I've spent the last few years doing the same thing with programming. I've tutored classmates on programming and on how security systems work, walking them through everything from how a web app handles a login to why a password hashing choice matters.

I first sat the CompTIA A+ exam at fifteen and scored 681 on that attempt, then passed it at seventeen while I was still a senior high school student. What I care about now is shipping things that run fast and hold up, especially machine learning that works on a phone and full stack tools that people can actually use.

Years old

Projects shipped

Years dean's lister

A+ first attempt

Spencer Calimlim2026

Pangasinan, PhilippinesDagupan City

Spencer Calimlim

Full stack developer and creative engineer, based in Pangasinan

SCANNING...

● PROCESSING

Where I started

I finished senior high school in May 2024 at Saint John's Cathedral School in Dagupan City. I was on the dean's list every year from grade ten through grade twelve, which mostly meant I got good at working consistently rather than cramming at the end.

Before any of that, I was the person our neighbours came to when a phone or laptop would not behave. Fixing other people's machines taught me to slow down, ask what was actually wrong, and not assume you already know the answer.

These days I spend my time on machine learning that runs on a phone, browser based AR, and full stack tools. I also tutor classmates on programming and on how software security actually works, from how a login flow handles bad input to why a hashing choice matters.

How I work

I would rather ship something small that genuinely works than a big plan that never runs. Most of my work starts as a question I cannot answer yet, like can this model run on a phone, or why is this page slow, and I stay with it until I know.

When something breaks I want the real reason, not the first plausible one. That habit comes from security practice, where guessing gets you nowhere and reading the actual data is the whole job.

I keep notes as I go. Most of what is in my writing section started as something I had to work out for myself and did not want to figure out twice.

What I'm into lately

Compressing models until they run somewhere useful, and getting inference fast enough to feel instant on a normal phone.

Browser side computer vision, and finding the line between a fun demo and something that does not fall over on a bad connection.

Security fundamentals, mostly through picoCTF, the National Cyber League, and HackTheBox. I first sat the CompTIA A+ at fifteen and scored 681, then passed it at seventeen while I was still a senior high school student.

Under the hood

I think in systems. When something repeats I want to turn it into a tool, a script, or a better interface, because the second time should be cheaper than the first.

I care more about the boring details than I let on: input validation, what happens when a request fails, and whether a page is usable on a slow connection.

What I care about

Software that makes a complicated thing feel obvious. The machine underneath can be as clever as it likes, but the person using it should never have to think about that.

For an audio model that means it just has to name the bird. For an AR game it means the thing you point at responds. For this site it means it loads, it reads well, and it does not get in your way.