Inside Our Engineering Culture (Vol. 2)

Written by

in

Bringing this back around with a couple of updates worth sharing.

We’re a fully remote team spread across nine time zones, which means most of what makes our engineering culture work has to happen asynchronously. Pull requests carry more context than a typical Slack thread would, and design docs are written assuming the reader wasn’t in the room when the idea started.

We also protect focus time aggressively. Engineers get two meeting-free days a week by default, and any recurring meeting has to justify its existence every quarter or it gets cut. It’s not a perfect system, but it’s one that’s let a fourteen-person engineering team ship faster than teams three times our size.

Comments

3 responses to “Inside Our Engineering Culture (Vol. 2)”

  1. andres Avatar

    Great breakdown of the difference between reporting and being data-driven.

  2. andres Avatar

    Would love a follow-up post with the actual before/after query plans.

  3. andres Avatar

    Curious how this compares to building the same thing in-house with a BI tool?

Leave a Reply

Your email address will not be published. Required fields are marked *