v2 · More Polish, Same Fire

The Story Behind This Version

v1 had worked. But working is not the same as feeling solid. The code lived in just two files — over a thousand lines crammed together. Changing one thing meant scrolling endlessly, terrified I’d break something else. And there were bugs: the timer sometimes lost track of a session, and nothing was ever saved to a real file structure.

So I spent one month doing the least glamorous work in programming: I tore the two files apart and rebuilt them into nine. I learned about modules, separation of concerns, and the quiet satisfaction of importing your own code. I also added a simple SQLite database — not a fancy one, just a single data.db file that remembered what I did.

The biggest user‑facing change was automatic daily activity tracking. It wasn’t clever — it just attached the current date to every new entry, so I could look back and see what I’d done without typing it myself. That tiny bit of automation made the app feel less like a notepad and more like a companion that was quietly paying attention.

The GUI was almost identical to v1 — same buttons, same layout. But underneath, everything felt cleaner. More reliable. I ran it on the same 2 GB Pentium laptop, and it opened faster, crashed less, and finally felt like something I might one day show another person.

I still didn’t share it. But when I looked at those nine files, neatly separated and humming together, I felt for the first time like a real developer — not just a kid messing around.