My journey into the world of code began at 14 with Python. Like many, I started with the basics of logic, but the allure of the visual web quickly pulled me toward the "holy trinity" of frontend: HTML, CSS, and JavaScript. It wasn't long before I wanted to make those static pages actually do something.

The turning point came with Harvard’s CS50. It introduced me to Flask and SQLite, which opened the door to the backend. For the first time, I could handle data and create dynamic logic. However, as I looked further into the vast ecosystems of Django and complex database management, I’ll be honest: it felt overwhelming. I decided to pivot, keeping my Python roots but exploring other directions like mobile development with Flutter, while continuing to build and refine static websites.

As I started coding professionally for friends, family, and local businesses, a new challenge emerged. These clients didn't just want a site; they wanted to manage it themselves. I went on a hunt for the perfect Content Management System (CMS), but I was met with what I call "CMS Trauma." Most platforms were either too rigid or incredibly over-engineered for a simple local business site. I eventually found TYPO3, which offered a great balance of customizability and ease of use. This was my gateway into PHP and MySQL, the tools that eventually powered my first major open-source project, Track, an inventory management system designed to mirror real-life storage racks and shelves.

Despite these successes, a specific frustration lingered. I wanted a way to build a clean HTML site and make it editable without the overhead of heavy frameworks, complex databases, or endless configuration files. I wanted the simplicity of static files with the power of dynamic content. This persistent itch led me to create Planalite, a lightweight, flat-file, HTML-first CMS written in PHP. No database, no complicated setup, just drag and drop, and you're live. (I'll be sharing a deep dive on the architecture of Planalite in a future post!)

Today, the challenges I face aren't just about syntax; they are about finding the balance between power and simplicity. In a world of increasingly complex tech stacks, I’ve learned that sometimes the best innovation is the one that gets out of the developer's way.