JavaScript I Wrote to Figure Things Out
I could follow a JavaScript tutorial and end up with working code I didn't understand. So I stopped watching and started building. Small things. A password generator, a random quote generator, a tip calculator, a background colour changer, a countdown timer. Each one was a single concept I wanted to actually get rather than just copy. DOM manipulation in one, event listeners in another, the Date object, Math functions, handling user input. The project was just the excuse to sit with the concept until it clicked.
Small on purpose
Keeping each project tiny was the whole strategy. When the idea is simple enough, the code is the only thing left to think about. There's no framework hiding what's happening, no build tool in the way, just the browser and the script talking to each other. That's where the learning was. I wrote everything in vanilla CSS and JavaScript, no libraries, so when something broke I had to understand why instead of swapping in a package that papered over it. Figuring out why it broke taught me more than any of the parts that worked first try.
Open and shipped
Everything is open source and hosted on Netlify, so the projects are live rather than sitting in a folder. None of this is complex work, and it isn't meant to be. It's here because design and code aren't separate things to me. Knowing how JavaScript talks to the browser changes how I design, and being able to read and write it means I can hand cleaner work to engineers and build small things myself when I need to.