We can know one thing for certain about the code we write: It will fail. We are all human beings, no matter if we like it or not, and humans do mistakes.
Maybe we misspell a variable name? Maybe we omit a parenthesis? No matter what it is, our application will crash and we will be tasked with finding and fixing what we made wrong.
But finding and fixing isn’t very productive. Crashing an application isn’t very productive. What is then productive? Employing automatic tools that finds the mistakes for us and prohibit our human essence from shining through in our production environments.
In this meetup we will look at some such tools. How we can use static code analysis like JSHint and JSCS to not only find the mistakes that we make, but also make our code look better in the progress.
We will take a look at task managers like Grunt and at real world examples of how one can utilise it to prevent problems within multi-project organisations.
At the end of the evening we will all be better equipped to handle our human selves and stop it from impacting the world around us.