How to write a testing framework

The task for this week was to build a Javascript front-end single page app framework. Ok, that doesn’t sound too bad. Here’s the catch – we weren’t allowed to use any existing JS libraries. No Node, Express, jQuery, Jasmine, Mocha…. nothing! Eeek!

Before we could even get started on the app, we needed to work out how we were going test our code. TDD is one the pillars of the Makers education after all. Despite using a string of testing libraries over the last few weeks, RSpec, Capybara, Jasmine, Mocha, Chai, I’ve never actually taken the time to look at the code and figure out how it works. So this is my attempt at breaking down a very elementary testing framework.

Read More »


Project week: AirBnBird

Week 6 arrived at Makers and finally we started working in groups! I’ve enjoyed pairing, but now that we’ve learnt just enough to take on all aspects of web development, working in groups feels so much more efficient. I had a lot of fun this week and was fortunate to be grouped with great coders, who I knew I would enjoy working with.

The Brief

We were set with the challenge to build ‘Makers BnB’, an Airbnb clone, and we were free to use whatever technology we wanted. We had two choices really – Rails or Node.js. Airbnb is actually built on Rails. It’s suited to it. So why did we end up choosing Node?

Read More »

A Retrospective Look at the Interview and Precourse

Time at Makers is flying. It’s now week 5 and we’ve finished our basic Ruby curriculum and been left to tackle JavaScript. Incidentally it’s also the time where we start our migration from being Junior Makers to Seniors and have our own mentees! As a result, I’ve ended up recalling some of my experiences, and with a bit more wisdom, understanding and thethe benefit of hindsight under my belt, I thought it was an opportune time to look at the overall process from application to starting the main part of the course.

Read More »

All things CRUD

CRUD stands for Create, Read, Update and Delete and these four functions make up the basis of persistent storage in the land of computers. By storing a state as data, we can ensure that this state will remain even if the process that created it does not. For example, I developed a web app at the weekend where you could play rock, paper, scissors, and I used a singleton class to store my game. As soon as I stop running the app though, that data vanishes. I can’t recall the game history. It’s gone and that’s not ok. There’s an obvious need to store information. This is where CRUD comes in.

Read More »