Why I Started Development

Published on
Why I Started Development

I didn’t start development because of a dramatic movie moment, a life-changing keynote, or some “I built my first app at 12” backstory.

I was just interested.

That’s it.

I liked the idea of making something on a screen and having it actually do something. Press a button, something happens. Change some code, the whole page transforms. It felt like controlled chaos — and I liked that.

At first it was small things. Editing templates. Breaking things. Fixing them again. Googling errors that looked like ancient spells. Slowly realising most problems aren’t magic — they’re just missing semicolons.

The more I learned, the more it scaled.
HTML turned into CSS.
CSS turned into JavaScript.
JavaScript turned into backend logic.
Backend logic turned into full-stack projects.

I didn’t wake up one day and decide to become a “Full-Stack Developer™”. I just kept following what interested me and increasing the difficulty slightly each time. Curiosity scaled. So did the projects.

Now I build things properly. Sometimes clean. Sometimes chaotic. Usually functional.

There wasn’t some huge master plan.

I was interested — so I scaled it.