One SSO, every internal app
One sign-in for every app: rolling JWTs, RBAC, AES-256.
Data is easy with one user. It gets hard once two teams share it.
So I keep it boring on purpose: real schemas, real RBAC, idempotent jobs.
Backend-first, but I ship the whole thing, schema to handover.
Flat tables, no audit trail, every transfer done by hand.
Schema first, API second. One source of truth.
PostgreSQL shaped like an asset's life: in, held, moved, returned.
One schema for every unit. New features never break the trail.
Building SATRIA, the asset inventory & return system, and training every work unit on it.
Shipped user-facing features and reusable components, then monitored them in production.
A hospital booking chatbot, a dosage-recommendation model, and feature upgrades.
Labor law and workplace compliance.

Innovation and problem-solving methods.

Led the new-student inauguration, end to end.

Python, SQL, visualization, statistics.

National award for content and communication.

Framework training for logistics platforms.

Competed in the national round.
Grounded in this page. Off-topic questions go to email.
Tell me what you're stuck on. I'll tell you how I'd model it.