Moishe Lettvin

I like coffee, bicycles, camera and code. Currently learning at Recurse Center.

A Landscape Generator

21 January 2022

One of my favorite things at Recurse so far has been the weekly “Creative Coding” meetup. Every week a group of about half a dozen of us get together and spend about 90 minutes writing code to respond to two randomly selected prompts. For instance, last week one of the prompts was “tech support” so I wrote a thing that creates a Markov chain from the longest Outlook FAQ I could find, and used that chain to build nonsense tech advice. Other people made very clever animations and even interactive games; it’s really amazing what can be done in 90 minutes!

Read More

A Story of a Wordle Solver

20 January 2022

A Narrative Journey

Like the rest of the Internet I’ve been enjoying playing Wordle for the past few weeks. While playing it I started thinking about good ways to approach the game, which of course led writing a computer program.

Read More

The Myth of the Potato

01 February 2021

A few years ago, when I was teaching interview training classes at Etsy, my co-teacher Tim came up with a great metaphor to describe the goal of an interview: by finding the bounds of a candidate’s knowledge, you’re discovering the shape of a “lumpy potato” that describes their knowledge. Every candidate’s potato is unique, and your job as a team of interviewers is to discover the shape of that potato. No individual interviewer can find the whole, but you put your slices together after the panel of interviewers and get the whole potato.

Read More

Remote Interviewing

16 March 2020

First, let me get this out of the way: I’m having trouble writing about anything practical or work-related with everything happening with COVID-19. I’m worried about my family, I’m worried about my friends, I’m worried about neighbors and anyone vulnerable. But this seems like a small, topical thing I can contribute to that might make a narrow sliver of people’s lives a tiny bit easier.

Read More

Unit Tests Aren't Free

19 January 2019

When I was thinking about leaving Google, and interviewing at lots of companies, I tried to ask at least one interviewer per company about unit tests. Google’s culture was very pro-unit test - it was basically impossible to get a PR approved without unit tests, there was a ton of internal documentation and education about how to write unit tests (even in the bathroom. Seriously), etc. etc. - and I thought that I could probably learn some important information about a company’s engineering culture by asking this question. During one of my interviews, the interviewer said, “well, we really don’t have that many unit tests. We have really good monitoring and generally the code coverage of people using our product is better than the code coverage we’d get by adding unit tests, so we’ve built a system where we can see things go wrong very quickly and fix them very quickly.”

Read More

I Don't Know

23 February 2016

As I’ve mentioned before, my co-worker Tim & I teach an interview training class at Etsy. The 2nd most important thing we teach (after “respect the candidate”) is the concept of “mapping the potato” – discovering the boundary between what a candidate knows and doesn’t know, along many many different vectors.

Read More