Latest

Finding resources to help you when you're trying to fix a memory problem can be a real pain. There's no central source of knowledge, information is scattered everywhere and a lot of the articles are already outdated. So, I tried to compile a list of articles I found useful and

You're part of a team where everyone understands and agrees unit tests are important and sees their value. Yet somehow you never get around to writing them. So how do you get out of this? How do you get from a situation where tests are an afterthought to one where

You've used MustacheJS templating to avoid code repetition and you're now dynamically filling in the template at run time. This works great, however you know that the user wastes time while the library is downloaded and the template is filled, when this could very well be done before hand, at

Wouldn't it be great if when you open the "File > New" menu you could also choose "React component"? WebStorm allows you to do this by creating custom "File templates". Start from an existing file The easiest way to create one is to just start from a file you already have

This probably sounds familiar: you have a setup with Gulp, Webpack and BrowserSync. Gulp compiles your scss/less files, Webpack compiles your JS files and BrowserSync nicely refreshes the page when anything changes. Now you'd like to make this even better - and have hot reloading of your JavaScript. But

You already know that it's a good practice to remove the console.log statements from your code when deploying to production. So you manually go over the code that you recently changed to remove any console.logs before uploading the files to the server. This is however a task that

You know you can use Grunt to automate some of the steps you already do when prepapring your code for production, but how do you actually go about it? First, let's install Grunt Fire up a console, navigate to the root of your project and then run: $ npm install --save-dev