How We Code at Teachable

jack phelps
May 16, 2018 · 2 min read

We spend a lot of interview time describing our stack, architecture, and processes to candidates. Like good little engineers, we figured it’d be nice to automate the process by writing it down so we can focus on more important things.**

Stack and Tools

Image for post
Image for post

We use fairly standard tools and practices in our daily lives:

Image for post
Image for post

We deploy most weekdays. We have a “no Friday deploys” rule to protect our weekends, but we’re willing to skip it for bugfixes or other rare cases where it makes sense.

Image for post
Image for post

Structure

Image for post
Image for post

After being completely flat for years, we reorganized to create some structure and process as we grow to ensure that engineers are able to focus on the right priorities without distraction. There are some projects we’d always wanted to tackle but that would continually be pushed off in favor of short-term priorities.

Now that people are formally staffed in these areas, it’s their job to make sure those projects happen. We’re also trying ensure some amount of rotation amongst pods to reduce siloing and keep people well-rounded while also giving them a chance to work on things that interest them.

** {sigh} I made yet another thing and now I have to maintain it :( Last updated 2018–10–03

Teachable

The official office blog of Teachable.

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch

Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore

Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store