JavaScript

How I Got Into It

I learned JavaScript through the SuperSimpleDev YouTube channel. That style worked for me because it stayed close to building. I was not looking for a purely academic way in. I wanted to make things move, respond, and actually do something.

By the time I got into it, I already understood enough of the web to know that JavaScript was where the browser stopped being static. That made it feel important immediately.

The Learning Process

JavaScript took longer to settle into my head than layout work did. HTML/CSS felt more visible. JavaScript felt more abstract at first. I had to get used to logic, state, events, and the fact that tiny mistakes could break the whole flow.

What helped most was building and testing instead of only watching. Every time I made a button work, fixed a bug, or understood why something was failing, the language became less mysterious.

How I Use It Now

JavaScript sits under a huge part of what I do now. I use it in Next.js, in Node.js scripts, in motion work with GSAP and Framer Motion, and in the general logic that makes products behave like products instead of static pages.

It is the language that keeps a lot of my stack connected. That is one reason I keep coming back to it.

What It Changed

It gave me more reach. Once JavaScript started to click, I was not limited to designing a surface anymore. I could make the surface work. Then I could move deeper into app logic, automation, and backend-adjacent work too.

It also changed how I think about learning. Knowing one language well enough to use it across different layers of the stack creates a lot of leverage. I felt that very directly with JavaScript.

Related

HTML/CSS · Node.js · Next.js · GSAP · Framer Motion · AI-Assisted Development