I didn't start coding because I had a five-year plan. I started because I was curious, and curiosity at 13 doesn't ask permission — it just follows whatever is interesting that week.
Where It Actually Began
My family noticed it before I did. I gravitated toward anything technical: taking things apart, asking how apps worked, poking at settings menus until something broke. When I found programming, it wasn't a switch flipping — it was the first thing that could absorb all of that curiosity and give something back. Every bug fixed, every small script that worked, felt like proof that the curiosity was worth something.
Learning Without a Roadmap
There was no bootcamp, no mentor waiting with a syllabus. I learned the way most self-taught developers do: badly at first, then a little less badly, one tutorial and one broken build at a time. What made the difference wasn't talent — it was that I kept coming back to it after school, every day, without anyone forcing me to.
Why the Early Start Mattered
Starting young gave me something that's hard to manufacture later: years of just building, with no pressure to monetize or specialize immediately. By the time I joined a real edu center and started competing with older students, I already had a stubborn habit of finishing what I started. That habit is still the thing I trust most, ten years and two-hundred-and-something projects later.
If you're reading this at 13, or you know someone who is: the age isn't the constraint. The habit of showing up is.