A month or so ago, I wrote about my grand ambitions for a project called The Folders Project - an experiment with frontend development building the same application in a variety of different ways. These ways will include different frameworks, different libraries/methodologies in those frameworks and all sorts of experimental stuff along the way.

This post aims to talk about the very first of these FoldersJS, and all the things that I had to do to get this effort out the door. There are a lot of items to mention in this post, so this one will probably be a little bit long.


Read More →

An Intro to Unbiasify

A few years ago, I had a recruiter reach out to me on Twitter to discuss a project. Unlike the usual “Plz come work for my company” pitch that one would expect - instead, he was responding to a post I’d made about seeking open source projects for the TorontoJS meetup group to contribute to during a hack night. This was what I received:

Screen Shot 2020-10-08 at 3.12.07 PM.png

Read More →

The Folders Project

Picture this - the year was 2015, and the framework wars have really taken off. For years the front end development landscape and JavaScript in general was ruled by jquery, but everything was changing. Backbone had been out for a while and had started to change everything, for web development - bringing in a robust solution for front end dev and simplifying some of the daily hassles that developers were facing.

On the tails of its success, and the outcry for better front end developer options, a plethora of frameworks and tools burst onto the scene. This included frameworks like Angular, React, Polymer, Ember, and more; the web developer scene was exploding with choice. There was so much super cool stuff, but it was impossible to keep up with everything! For me, this is where the pet project 52 Folders came in.

Read More →

Refactoring away Recompose

At my current employer, like many other software companies, we aim to prevent unnecessary code duplication (where it makes sense!) and to share functionality in our code base. In the earlier days of working with React, there was one relatively defacto solution for being able to share functionality between your components - Recompose: a library that aimed to make code reusability much simpler through the use of the highly lauded ‘Higher Order Component’ (or HOC) pattern that was extremely popular at the time.


This Post is a helper to explain how to do remove Recompose from a codebase. Caution, it’s long and pretty technical - but it’s a good helper if you’re also trying to get rid of recompose and need a tip or two:

Read More →

What's Nuxt?

Earlier this year, I started a side project that I invariably abandoned. Like many other random side projects, I spent way too long determining what fun new technology I wanted to experiment with while I was fiddling around with this app.

Read More →