A personal game tracking application built with Python.
GameTracker started as a way to practice core Python while solving a real, everyday problem: keeping track of which games I'm playing, which ones are finished, and which ones are still sitting in the backlog.
Instead of a tutorial project, I built something I'd actually use: a command-line tool that lets me add games, update their status, and keep that list saved between sessions. It's simple by design: the goal was to get the fundamentals right before adding complexity.
The project touches on data structures, file I/O, and basic program architecture: the concepts a CLI tool needs to feel solid rather than fragile.
GameTracker is a small project, and it's meant to be. The point was never to build something impressive on day one, but to build something real while the fundamentals were still being learned. The next version will likely move past the terminal, but the habit it built (shipping something working, then improving it) is the part that carries forward into whatever comes next.