For no particular reason whatsoever, I recently found myself dusting off an old repository, InterviewPracticeQuestions and thought it a good exercise to restructure it along the latest C++ and CMake principles.

Having recently returned to dynamically-typed languages, I've found myself stumbling a little without the safety net of type-checking. Yet, I'm not convinced on the principles of duck-typing either.

For a discipline supposedly rooted in rationality and logic, it's surprising there isn't a greater emphasis placed on decision-making. All too often, critical decisions are led by heuristics rather than formal methods.

This might appear a little left-field, but it's always surprised me how the morphology of the Irish language lends itself to programming constructs.

A walkthrough of my approach to writing a good program, informed by Clean Code and A Philosophy of Software Design. The premise is simple, the structure of a program should be driven by its public interface, not its implementation.

It's a favourite pastime of critics to bash on the use of singletons, and that argument has merit. Frequent encounters have left an indelible mark on my psyche. This post is a continuation of an age-old argument.

As part of my first assignment for Media Programming, I was tasked with creating a Flash tutorial of an Actionscript technique. What follows below are the steps I took in building it.