Why I Started Coding

I started with a simple question: how do the apps I use every day actually work? The answer led me to JavaScript, then to the smallest possible proof that I could make a computer do something on purpose: a button changing colour on a page.

That moment mattered because it changed my relationship with technology. I was no longer only consuming software; I could inspect it, remake it, and eventually imagine things that did not exist yet. The tools have changed since then, but that sense of agency has not.

Learning by making

I learned the way I still learn now: by choosing a problem just beyond my current ability and building until it either works or teaches me why it cannot. HTML and CSS taught me that structure affects feeling. React taught me how state changes a product. Node and Rust taught me that a beautiful interface still needs a serious system behind it.

The useful lesson was not to collect technologies. It was to learn how to reduce uncertainty: read the documentation, make the smallest test, observe what happens, then keep going. That loop is a superpower in an industry that keeps changing its tools.

What stayed the same

I still care most about the moment an idea becomes real. A product can start as a sketch, a sentence in Notes, or an awkward prototype. With enough attention, it becomes a thing another person can use. That is why coding never felt like a subject to me. It became a way of thinking, designing, and taking responsibility for an outcome.