One SSO, every internal app
Multi-tenant SSO with rolling JWTs, RBAC, and AES-256 encrypted responses. One identity layer instead of everyone rolling their own.
Easy when it's just you writing to it. Gets messy once two teams need the same data to line up, or someone who's never touched a foreign key has to make sense of your schema.
So I keep it boring on purpose: real schemas over caches, real RBAC over shared logins, idempotent jobs over retry buttons.
Backend-first, but I ship the whole thing, schema to handover, so nothing quietly breaks in between.
Asset records lived in flat tables with zero audit trail. Everyone requested transfers their own way, so nothing ever matched up.
Schema first, API second. One source of truth instead of a dozen exports. FastAPI handles auth and the whole asset lifecycle, no more manual reconciling.
PostgreSQL mapped to how assets actually move: in, held, transferred, returned. SQLAlchemy handles the relations, Docker keeps it reproducible.
One schema instead of a workaround per unit. New features ship without breaking the trail, and I train the staff on it myself.
Build and maintain applications for the State-Owned Assets Administration Division, including SIRANGGA V2, a redesigned asset inventory & return system. Train work units across the Secretariat General on rollout.
Shipped user-facing web features and modular, reusable components across devices. Monitored performance and traffic to catch usability issues before they became tickets.
Three engagements: an AI chatbot that streamlined hospital appointment booking, a machine learning model recommending medication dosages, and a round of feature upgrades to an existing program.
A small assistant grounded in what's on this page, roles, projects, stack. Off-topic questions get pointed to email instead of a guess.
Quickest way in: tell me what you're stuck on. I'll tell you how I'd model it, and what I wouldn't build.