I build around the work that actually happens.
My background started in healthcare, where vague problems have real consequences. That trained me to observe closely, document clearly, and look for the constraint before prescribing a fix. I carry the same habit into software: map the system, remove the friction, then make the result repeatable.
Started in healthcare. Stayed in systems.
Three years in physical therapy taught me to triage before fixing — read the symptoms, isolate the cause, ship the smallest intervention that works. Same discipline now, different domain. Patients became products. Treatment plans became architecture.
Off the keyboard, on the ground.
Community medical outreaches, donation drives, and clinical work with classmates. Practical coordination — small teams, tight windows, real deliverables — kept sharp outside the screen.
Student leadership, every year of college.
Vice President External of the Supreme Student Council, secretariat head, feature writing editor. The work was running the room, closing the deck, finishing the budget. Same operating muscle I now bring to technical projects.
Finish what you start.
Two half marathons, more donation drives than I can count, and a long list of side projects that actually shipped. Same rule every time: ship the boring middle, finish the last 5K, log the result. Software has never asked anything different.
The work is the practice. The practice is the same.
Timeline as infrastructure.
Operator to architect.
os
Building fulfillment platform infrastructure: multi-API order sync, real-time operations dashboards in Svelte 5, D3.js visualizations, Supabase automation, webhook handlers, and edge functions.