Getting Faster

JavaScript, by nature, is a pretty easy language to build. One advantage that JavaScript has is that JavaScript is an interpreted language, which means that the code developed can still be deployed, and even work, according to a project's specifications.

Non-compiling code is both good and bad. Without the need to compile, a developer can quickly build a web page on a full web application in a very short amount of time. Also, it's very approachable for new- or intermediate-level developers in general, making staffing for web projects a bit easier.

Now, what's bad about not using a compiled language is that JavaScript doesn't compile and common errors tend to get missed by the developers involved; even if the code appears to be working, it may not be working efficiently. During the days where developer tools were most likely to be Notepad on Windows and a web browser, any errors were apparent to a user only, leaving out any issues with regard to code performance.

Today, we have various tool sets and build systems on top of our JavaScript skills. It's important to understand that having deep JavaScript knowledge can help you write and review better JavaScript code but, in many cases, we as developers are only human, and we make common mistakes that affect our JavaScript code—not adding spaces after a function's starting brackets or forgetting a semicolon at the end of our code statements, for example.

Choosing a proper editor for a given project that includes basic error-checking before writing a single line of JavaScript can improve the performance and quality of our codebase dramatically, without learning anything new in terms of the inner workings of JavaScript.

Complete and Continue