Keep Your Errors Close

Sometimes you write code that doesn’t work. If you’re lucky, you notice immediately; if you’re NOT so lucky, then you might not notice until it’s all the way into your customers’ hands when… BANG! NoMethodError on undefined TypeError DANGER DANGER, etc.

What this talk is about is how to discover errors as soon as possible, and why doing that is valuable. Focusing on JavaScript, we’ll have a practical look at how we can structure our code (to avoid propagating errors) and what tools we can use (linting, tests and types) to avoid these nasty surprises.