Falcor is a new open source project from the great engineering team at Netflix. The power of Falcor comes from the use of of a new graph object called JSON Graph. JSON Graph is a new structure for delivering the entire graph on an object in a very simplified javascript object. The team at Netflix has provided great documentation and video on the Falcor page that I highly recommend you read. Initializing the Connection Before we create a connection to a remote Falcor router lets begin by providing a local

Hey Junior

So you just signed the offer and it’s official: you are a junior software engineer. First of all, congratulations! I hope you took a second to celebrate. Maybe you are self taught, maybe you took courses online or in person, maybe you went to a coding bootcamp, or maybe you went to a lot of meetups. However you chose to approach your climb into the world of software engineering, you’ve arrived at the base camp. As with any other occupation, there are good habits that those that came before us

One year ago, I joined Laurel & Wolf as its first marketing hire. At that time, our customer acquisition strategy relied mostly on startup press, word of mouth, and our investors.  Laurel & Wolf brought me on to scale paid acquisition, improve conversion, and ramp up overall client growth. For years, I’ve obsessed over using programmatic methods to generate revenue online.  Engineering interest started early – I began coding (Perl) at 15.  My dad and brother have been computer programmers for a combined 65 years – Dad coded for various aerospace companies most of his career, starting

Hi! I’m Nina and I head up Product at Laurel & Wolf. I wanted to write up something short and sweet for this weeks blog posting, so I decided it would be interesting to address two questions I get asked every so often: 1) how one gets into product management and 2) what skills are required to be a great product person. The answer to the first question is, in short: there are a million ways to get into product. I’m not sure I’ve ever met two product people that had the exact same story of

Outgrowing an MVP

As 2014 came to a close, our business was rapidly growing. We finally felt like we had the amount of product usage and feedback to validate our product hypotheses in a meaningful way. Our designers and clients were being successful and having fun using our platform, but it was by no means without its deficiencies and kinks. At the time, our site was primarily a Rails application with some augmented features added to the HTML using Backbone. We started to encounter issues with some of our more interactive features. For

A Big Ball of Mud

We recently went through the process of rethinking a large part of the architecture of our Rails app, which taught us many things. One of the things we learned was that there is an existing concept to describe what our codebase was — a big ball of mud. According to Wikipedia, “a big ball of mud is a software system that lacks a perceivable architecture. Although undesirable from a software engineering point of view, such systems are common in practice due to business pressures, developer turnover, and code entropy”. Unless you are working

Last time we talked about using docker-compose in the second part of our three part series. Now we have to show you how to move the (metaphorical) furniture so your team can define the perfect environment. docker-rsync Most developers want to mirror their source code to the guest container. They’d like to be able to edit and commit on the host while running and testing on the guest. There are three primary ways to do this and none of them are particularly pleasant. The COPY You may have noticed a

Last time we talked about using docker-machine in the first part of our three part series, but that only gets you to the house. Now we have to show you the (metaphorical) paintbrush and ladder so your team can define the perfect environment. docker-compose There are two ways to use Docker: An isolated ecosystem for your program sitting inside a container. A series of ecosystems that are interconnected, with a service per container. I think the future and mature way to use Docker is the latter. If like me you

On-boarding, the process of bringing a new worker into the fold, is often the hard part in starting at a company. Usually you are sat in front of a company computer and given a wiki link, GitHub repository, or maybe just an email with the steps for setting up your machine. If you’re lucky it’s been updated in the last year. We have the tools to do this better now and I want to explore them with you. The first time I remember an on-boarding experience as a developer was