Reorganizing the house before it grows
The front-end code had grown fast and tangled. Before building the app, every piece got its own name, its own boundary, and its own test.
Weeks of shipping features fast come with a cost that doesn’t show up until the bill arrives: the front-end code had grown all tangled together, everything depending a little on everything else. It worked, but every new change cost more to figure out where to touch, and something as simple as testing one piece without spinning up the rest had become impossible.
I spent a few full days on something that doesn’t show up on any screen: splitting that code into pieces with clear names and clear boundaries — one for local storage, one for the session, one per screen — so each one could be understood, tested, and documented on its own, and a change in one wouldn’t force a review of the other ten. It’s invisible work to whoever uses the product, but it’s what makes it possible to keep building fast afterward without every new piece getting more fragile than the last.
Doing it right now wasn’t a coincidence. What was next on the list — turning Nada Menos into something you install on your phone, not just something you open in a browser — needed an orderly foundation underneath. Building that on top of the previous mess would have meant paying the same confusion tax, only now across two platforms at once.