Build
From the database schema up: I plan the data model first, then build the API and the interface on top of it, in React, Flask, or whatever the project calls for.
About
The short version
I'm a Computer Science student based in the Philippines, building full-stack apps, small games, and developer tools while finishing my degree.
Most projects start the same way: pick a problem, sketch the data model, then work outward to the interface. AxisPT is the clearest example, a school management system with role-based portals on a shared schema, but the same approach shows up in the smaller projects too: a chemistry game backed by a real compound database, a limit calculator that evaluates symbolically instead of guessing.
What I offer
From the database schema up: I plan the data model first, then build the API and the interface on top of it, in React, Flask, or whatever the project calls for.
Getting a project from 'it works on my machine' to something deployed and clickable, the auth, the edge cases, and the empty/loading states nobody asks for until they're missing.
Outside of app-shaped work, I build small games in Unity: systems, UI, and the kind of mechanic that's more fun to build than to play.
The tools I design, animate, and build with, kept to the ones I actually reach for.
Languages
Frontend
Backend
Game dev
Databases
A bit of background
Working through the last stretch of a BS in Computer Science while rounding out AxisPT: a two-portal school management system with role-based logins, a shared PostgreSQL schema, JWT auth, and a small admin analytics view built on Chart.js.
Designed the entity-relationship model first, then built the React front ends, the Express API, and the JWT-based role checks on top of it. Two portals, student and admin, sharing one schema and one auth system end to end.
Built a React travel and hotel-booking app around a single Context API store, a Flask + SymPy limit calculator that evaluates limits symbolically instead of guessing, and ChemBine, a Unity drag-and-combine chemistry game backed by a real SQLite compound database.
First real projects in both stacks: a 3D endless runner with Rigidbody physics and the new Input System, a 2D arcade game tuned the way Flappy Bird is tuned (gravity, flap strength, gap spacing, repeat), and a React temperature converter built around one reusable calculator hook.
Began a BS in Computer Science: data structures, algorithms, and the first real programming courses, the foundation everything since has built on.
Small scripts and smaller games, mostly broken, mostly for the fun of seeing something run. The part of the story that explains why a CS degree, rather than the part worth a case study.
What I do
Tools