Skip to content
Back to handbook
Department Archives

Engineering

Listing 12 documents under this division.

We build things that work

This handbook outlines the practices and operational standards we use to build correct, stable software.

Every dependency is a liability

We evaluate, add, and remove third-party packages to keep our dependency graph small and maintainable.

How we handle incidents

We prioritize system stabilization over root-cause debugging during production outages.

How we review code

We review code to verify logic, catch edge cases, and prevent latency spikes, leaving formatting to compilers.

Instrument your code before you ship it

We set up logging, error tracking, and metrics dashboards for every service before it handles production traffic.

Record your architectural decisions

We write Architecture Decision Records (ADRs) to capture the reasons behind our technical choices while they are fresh.

Ship small, isolated changes

We deploy code in small increments to reduce risk and maintain speed.

Test what breaks

We prioritize integration tests over unit tests and eliminate flaky tests within 24 hours.

The on-call rotation

We assign clear ownership of production systems to resolve incidents quickly and distribute the operational burden.

Treat migrations like surgery

We write, test, and execute database migrations under strict controls to prevent data loss and downtime.

Your laptop should mirror production

We maintain local environments that match production to prevent configuration drift.

Build software that lasts

This closing chapter checks whether we have internalized our operational values.