It began as a fairly compact prototype, but as the project became more real, the structure around it had to grow too.
What I did
Turning an existing spreadsheet-based way of working into an application that could grow beyond the spreadsheet itself
I worked across the frontend and backend, translating spreadsheet-driven processes into application flows and building the early version with Next.js and a database. As the prototype grew into a fuller application, I helped move the backend into its own Express.js service so the responsibilities were easier to separate and continue developing.
This was also where I started experimenting more deliberately with code organization. I proposed an N-layered structure with feature-based vertical slicing, turned it into a reusable backend boilerplate, and walked the team through the approach. The goal was not to make the architecture look more sophisticated, but to make the code easier to follow when someone needed to change one part of the system.
For internal projects, I keep the details broad enough to explain the work without exposing private data, internal processes, or anything that should stay inside the company.