mojo - kn

Today I’m officially announcing the launch of Prismatest, a Javascript library to decouple your front-end tests from the view layer details.

I’ve been asked at least once “How can I get better at programming in a compositional style, with functions?” This question usually stems from someone trying to learn a language dedicated to functional programming and struggling to make the paradigm feel “natural”. As one of the more outspoken advocates of functional programming in the office, I thought I’d provide a “listicle” of tips in the inimitable style of BuzzFeed to address the question.

TypeScript provides some nice facilities for quick and easy error detection when writing React components. Writing React components in TypeScript isn’t hard, but getting the most out of higher-order components in TypeScript can be a bit tricky, especially when they need to be generic.

MojoTech, like most companies, has the concept of a Project Lead. Initially, I wasn't sure what to expect when I took on my role as Project Lead, so I'm writing this post to shed a little light on the responsibilities and expectations of the role, as I approach them. Typically my morning and afternoon look the same, so to avoid redundancies, we’ll take a look at a typical morning schedule.

As developers we're tasked to take a problem specified in the fuzzy language of human interaction and translate it into a representation that can be understood by a machine. To do that we have to simulate the machine in our heads, and manually trace every possible path of execution. The number of execution paths grows at every branch point in the code, and there are often many different ways to branch an execution path. This results in a search space that can very rapidly grow to be unmanageable when trying to figure out which code path is being followed.