Wednesday, July 20, 2016

8 Steps to Constructing a Better Software Engineering Homework Interview

Links to this post
A recent trend in the SF tech scene, and perhaps elsewhere, is the take-home interview. I’ve been on both sides of this exercise, I’ve noticed it can have unintended consequences: a bad experience for the candidate and a filtering out of qualified candidates. I’d like to talk about some of the problems, and offer 8 suggestions about how to improve it.

Wednesday, June 8, 2016

Refactoring and Iterating on Generators

Links to this post

In this post, I delve into writing the same functionality in a myriad of ways. In the process, I'll evaluate some trade-offs, as well as try out generators of Javascript ES6.

Friday, January 15, 2016

Links to this post

Shh! Algolia for the Win

Sitting in our dining room, discussing our kids’ room full of books, I decided to regale our kids with a story about the old days of the library: rows of “card catalogs," little pieces of paper to jot down call numbers, etc. This got them very excited, and they love building things, so they were gearing up to re-create just such a system in their bedroom. 

Wednesday, July 23, 2014

Should we use multiple input fields to prevent mistakes by users?

Links to this post
(Also posted at

At Stitch Fix, we’re working on our sign-up flow. During this process, we debated whether we should have a single password field, or, as many sites do, two— the second one being a “password confirmation”.

Some sites use the same technique with email and email confirmation.

I found quite a few articles that advocated certain practices around this, but I thought it would be useful to synthesize them in one place. At the end, I offer some recommendations.