proilan
adolfo

I'm currently finishing my BSIT degree at Bukidnon State University, learning in public and building with a bias toward clarity, usefulness, and steady improvement.

Here's how that shows up in the way I plan, build, and ship projects, from classroom requirements to full capstone systems:

• 01

  clarity first

  I write readable code and document decisions so anyone, including future me, can pick up a project without guesswork.

• 02

  ship, then refine

  I get a working version out early, gather real feedback, and iterate instead of chasing a perfect first draft.

• 03

  user-centered

  Features get built around what people actually need, whether it's parents tracking attendance or clinic staff logging patient care.

• 04

  learning in public

  As a BSIT student, I treat every capstone and side project as a chance to document mistakes and lessons, not just ship features.

• 05

  small, testable pieces

  I break a big system into smaller modules I can run and test on their own, like separating the RFID scanner from the notification service, so bugs are easier to isolate.

• 06

  communication over guesswork

  Before writing code for a group project or client request, I confirm requirements and edge cases out loud so the whole team builds the same thing.

Right now I'm applying these habits while finishing my BSIT capstone and picking up more backend and AI-assisted tooling, so I can carry them into my first professional role.