I’ve been thinking a lot lately about functional programming, and I thought it might be kind of fun to walk through the process of writing a curry function.
For the uninitiated, currying refers to the process of taking a function with n arguments and transforming…
It’s a question I get asked pretty often.
For the past few years, my answer has always been: “Roll your own x”, where possible values of x include jQuery, Backbone, Redux, a DNS server, Express, Handlebars, Mocha, a…
I interviewed at a company late last year that was having a lot of trouble on the front end.
Their apps were unmaintainable. Code quality was poor. Build processes were slow and messy. Nothing was really standardized.
In the past few years, I’ve done kind of a 180° on unit tests.
There are a lot of really easy ways to rationalize not testing your code, and I’m probably guilty of saying each of them at one point or another.
I’m just gonna get this out of the way right up front, because people get really angry otherwise:
Consider this post as a series of learning exercises. These examples are designed to make you think — and, if I’m doing it right, maybe expand your understanding…