Why I Started Learning to Code
I did not wake up one morning as a “developer.” I woke up curious, slightly overwhelmed, and tired of waiting for the perfect plan.
This post is a short origin story for the blog: why I started learning to code, what I got wrong at first, and what I am doing differently now.
Curiosity beat credentials
For a long time I treated coding like a club I was not ready to join. Tutorials looked polished. People online seemed fluent. I assumed I needed a perfect roadmap before writing a single line.
That mindset delayed me more than any missing skill.
What finally helped was a smaller question: can I make one tiny thing work today? A page that says hello. A button that changes color. A note-taking app with one feature. Tiny wins made the whole subject feel human.
What I got wrong early on
I collected resources instead of finishing them. I bounced between languages. I compared my day-three code to someone else’s year-three portfolio.
None of that built confidence. Shipping small projects did.
So I changed the rule: every week I try to finish something I can open in a browser, even if it is ugly.
Why this blog exists
I write here for two people:
- Future me, who will forget how confusing Git felt at first.
- Other beginners who need honest notes more than another “master JavaScript in 7 days” promise.
If you are starting too, welcome. You do not need to feel ready. You only need to begin, break things safely, and keep notes on what you learn.