Jan 2026/Fullstack/professional
Lapor FSM!
This project was built together with a friend to replace the messy and manual incident reporting at our campus. We split the workload by roles, and I was fully responsible for the reporter, admin, and building PIC flows. The biggest challenge was not the tech. It was navigating the tension between what the client requested and what the most efficient implementation actually looked like. It was super frustrating at times when we would propose a much more effective process, only to hit a wall because that is just how the SOP is written.
We basically had to implement a super strict status lifecycle. This included fast-tracks for emergency reports directly to the Supervisor, and recalls if a supervisor rejected a technician's work. It was a massive exercise in aligning modern technical architecture with very rigid, legacy human processes. We used Next.js and an ElysiaJS backend on Bun, wired up with WebSockets for low-latency real time updates to make sure no incident gets left behind.
Looking back, dealing with institutional SOPs taught me way more about product engineering than writing the code itself. When you are building operational tools, the existing workflow of the client is the reality you have to design for, no matter how inefficient it seems. In the end, we built it exactly to their operational spec. Honestly, everything is a win when the ultimate goal is just to experience, learn, and ship real software.