Node.js

How I Got Into It

Node.js became part of my stack because JavaScript kept leading me there. Once I was building more seriously, it was hard to avoid. Scripts, package tooling, local servers, framework runtimes, a lot of the modern web world assumes Node is in the background.

So I learned it less as an isolated subject and more as part of learning how the whole development environment actually works.

The Learning Process

The early confusion was mostly about context. Browser JavaScript made sense to me faster. Node.js took a little longer because I had to understand what changes when the code is running outside the browser and why that matters.

I also had to get more comfortable with packages, scripts, terminals, and the general messiness that comes with real project tooling. That learning was worth it because it made the rest of the stack feel far less magical.

How I Use It Now

Node.js sits under a lot of my daily work now. It powers local development, scripts, project tooling, parts of Next.js, and the technical side of systems like n8n Workflow with VPS.

It is one of those layers I may not think about constantly, but I feel it every time I build.

What It Changed

It connected front-end work to the larger environment around it. Before that, it was easier to think only in terms of pages and UI. Node.js helped me think more like a builder working with a full system.

It also made my stack feel more unified. Staying close to JavaScript while still moving into backend-adjacent work gave me a lot of leverage.

Related

JavaScript · Next.js · GitHub · Vercel · n8n Workflow with VPS