DEV Community

Cover image for Learning Technology Outside the Classroom: A Teen Developer’s Journey
Prasoon  Jadon
Prasoon Jadon

Posted on

Learning Technology Outside the Classroom: A Teen Developer’s Journey

WeCoded 2026: Echoes of Experience 💜

This is a submission for the 2026 WeCoded Challenge: Echoes of Experience

Learning Technology Outside the Classroom: A Teen Developer’s Journey

You don’t know me—and maybe that is better. Someone once said, “Don’t ask my name. Look at my work.”

Still, writing this makes me a little nervous. Maybe it is because this is my first time participating in something like this, or maybe because telling your own story is harder than writing code.

I am a teenager from India. I am not a professional developer, and maybe I wouldn’t even call myself a developer yet. But I am someone who can code—and more importantly, someone who is curious.

I didn’t learn programming at a big university. In fact, I am still in high school.

I never dreamed of becoming a developer. Coding simply attracted me. Sometimes in life you start doing something without fully knowing why—you just feel pulled toward it. That is what happened to me.

When I first wanted to learn programming, I didn’t even know where to begin. I didn’t have a laptop either. All I had was a phone and curiosity.

In my school there is a subject called Computer. One chapter in it was about Scratch. That was my starting point. Scratch was the only programming tool I knew at that time, so I began there.

But curiosity grows quickly.

Soon I started exploring web development. That was where I met my first real obstacle: CSS.

Understanding how to design things with CSS was difficult for me. I could write the code, but making something look good was another challenge entirely. The hardest part was animation. Pure CSS animations always confused me, and many times I felt stuck.

But I didn’t stop.

Before trying to animate something on a website, I began doing something unusual. I would take a sheet of paper and draw the structure of the page and the animation step by step. It was not perfect, and it didn’t always work exactly as I planned, but it helped me think clearly.

That small habit changed the way I learned.

Instead of randomly trying code, I started thinking about the problem first.

And slowly I realized something important:

Curiosity alone is powerful—but curiosity with clarity works even better.


Top comments (0)