I build the parts underneath the parts people see.
Most of my work happens below the interface: authentication, data models, the logic that decides what's allowed to happen. I like systems that hold up once someone actually starts using them.
A bit of background
I'm a CS student who got into building software through a drag-and-drop CRUD tool early on, enough to teach a short class on it. Since then I've moved into writing backend systems by hand: authentication flows, database design, and the unglamorous logic that keeps an app from breaking the moment a real user touches it.
Right now most of my time goes into a full inventory and sales system: barcode-driven stock tracking, role-based access, sales reporting, and a demand-prediction feature, built solo, end to end.
Featured project
Inventory & Sales Prediction System
A full retail management system: role-based login for Admin, Manager, and Cashier accounts, barcode scanning for stock in/out, a working point-of-sale checkout flow, sales reporting, and a forecasting feature for restock planning.
How I got here
Full inventory & sales system in ASP.NET Core: auth, barcode scanning, POS, reporting, predictions.
Sessions, password hashing, and why "it redirects to the wrong page" is rarely one bug. Learned the hard way.
Ran a short class on a drag-and-drop CRUD tool I built as a freshman.