The Beginner's Guide to Terminal for Node.js Development
When we are doing a NodeSchool or a Node.js/Microservices training we usually run into participants who feel lost when they have to use the terminal. Because of this we decided to do a mini blog series of two posts of using the terminal for Node.js development: one dealing with the very basics, and one with more advanced, in-depth tips and tricks.
Disclaimer: I'm using the word terminal here because I don't mean a particular shell, but a whole collection of shells.
Just to be clear: In computing, a shell is a user interface for access to an operating system's services.
The terminal is your universal Swiss Army knife, it will be always with you wherever you go, even if you're working on a remote server or a local machine.
The terminal is a computer console, a text output device for system administration messages.
Having text input has been always a part of the computer since the beginning of time, but since then we have changed for so called user-friendly interfaces that are much easier to use.
But are you sure that those are more efficient?
A text-based input and output is mandatory for building good software:
Write programs to handle text streams, because that is a universal interface.
Having a blinking cursor can be too scary at first for many, but when you get into using it, it will be as simple as any other program.
Read more/Post's link: