Best Node.js Explanation For a Newbie

Why is this the best node.js explanation for a newbie

It is plain and right to the point, if you are a seasoned programmer this may seem silly but honestly, everything out there was too in-depth for me to understand. Knowing about Node.js is important for a full stack developer, but being confused and not wanting to learn it is another challenge. Above I spoke of how node.js uses your code and how you can expect it to work once you start learning more about it. There is nothing like documentation so I recommend rolling over to NODE.JS after this and checking out the documentation.

What is node.js:

It is an environment that allows you to run javascript also known as a runtime environment. At first, JS was solely used in the browser, but the creators realized that there was so much more power available such as running a stand-alone application. Now with Node.js, the language has similar capabilities of popular scripting languages such as python.

Both Javascript and Node.js use the V8 JavaScript runtime engine. This takes your code and turns it into code that your computer can read without having to interpret it first. In short, it speeds up the process of a computer reading your code allowing for magical things to happen. Node.js is event-driven and does not block the input or output. That alone can tell you the beauty of this as it keeps it simple and executes what’s needed based on the event instead of worrying about the bits and pieces.

How you normally execute javascript

In the past, you would create a local HTML file on your computer then add a call to a relative JS file. From there you can open it up in a browser and play with it in the console. But that was the environment and in my mind made it to where being limited to just that made me feel that other than some functionality on a website that was all to be had. Then Node.js comes along and as mentioned before that RunTime Environment takes what I described out of the equation and opens to the doors for so many possibilities.

Node.js example

  1. First you need to have node installed on your computer
  2. Open your terminal / command line and type node -v
  3. Now you will see the version you have on  your computer
  4. Create a folder and put a normal js file in there stuff.js
  5. Navigate to that folder in the terminal and type node stuff.js

BOOM you will see your code executed without having to be on a browser.


Once again this was not for someone who is looking for that technical aspect of node and what it does but instead just the best node.js explanation for a newbie. Nothing was talked about NPM which is really neat and stands for Node Package Manager. What was talked about is this awesome way that you can execute JavaScript without the limits of a browser and hopefully you will continue to explore more of this amazing portion of web development. I write about things I am doing or dealing with just like my SEMRush tool breakdown or SEO for images, if you really like my style then sign up for the email below.

Learning Quest For a Front End Developer

It seems that the term “on the job experience” is so true for quality learning. For a front-end developer by not having this, the motivation can wean to easily especially if you already have a job that is not challenging new front-end technologies. I current am a “corporate developer”, and what that means in my own terms is that I manage a few sites for the company I work at keeping them up to date and add new features as needed. This is great but I can’t seem to find the time to practice some of the other areas I want to grow in. The first thought would well just rebuild the current site not using a framework, or take a page and see if you can template it out with the new CSS grid, but with the red tape working on those projects are not always able to be done.

How to keep learning

Finding a good site like Plurasight or even the infamous Freecodecamp which is not only amazing but also it is a great cause. By going through these I think it is important to use tools like to in some way have a playground or portfolio of some kind you can look back on.

Just going through tutorials is only going to get you so far, but not having a plan to practice with will also get you stuck quick. One new tip is, I started a document where I literally just jot down code challenges for myself that I would like to complete. I have found that this is rewarding for sure, and gives me that motivation that can lack when you are just trying to learn for fun. There are so many cool neat new ways to learn code in general like codewars and also codecombat which gamify the experience. As a developer in his mid 30’s those are great to practice but that real world scenario is just not there.


What this does is also give you an opportunity to have new skills if you decide to change jobs or start a new direction in your career. For example, you may be a front-end dev like me and really just work in HTML, Vanilla JS, and CSS, but have a passion for Python. If so then having projects on the side that help defines those skills will give you an opportunity to grow. Once again you may have to make those projects yourself and staying motivated could come from just being a little more intelligent than you were the day before.

Essentially this was a rant for me to continuing to attempt to grow. I have the goal of one day having the opportunity to do more software engineering using languages such as Python or even Java. With that said keeping up with newer JS tech (VUE, React, Angular) has seemed to be just as challenging. If anyone does read this and shares the same struggle, I guess it’s safe to say keep charging forward and sometimes write about it.