Our Code
How DTC writes software. Principles — not tutorials. Implementation guides (Docker conventions, branching, semver) live in the Developer Operations book and link back here. These principles apply to everyone who touches DTC-built code.
Build for Unreliable Integrations
Any third-party system DTC integrates with will eventually rate-limit us, drop a webhook, return ...
Writes Are Jobs, Reads Are Cached
User-facing requests never block on outbound writes. Every write to a third-party system is queue...
Everything Has a Timestamp and a Deadline
Every record in a DTC-built system answers three questions: when was I written? when did I last c...
Webhook-Driven, Reconciler-Bounded
Freshness comes from webhooks. The reconciler is what catches the webhooks that get dropped. Full...
Explicit Handling of Absent Data
NULL is not 0. NULL is not "". NULL is not false. NULL is not "no change." Treating any of those ...
Branding in the Environment, Not the Code
Company name, logos, support contacts, color palette, email footer copy, physical address — all t...
Versioned, Signed, and Tagged
Every deployment is traceable back to a specific commit by a specific author. Version numbers are...
Closed Records Are Immutable Until Proven Otherwise
A closed ticket, a paid invoice, a rejected quote — these are terminal states. They rarely change...
Observability Is a First-Class Citizen
When something breaks in production, the first question is always: "what happened?" The answer ha...
Every Integration Has a Resume Endpoint
Users close tabs. Networks drop connections. Browsers reconnect SSE streams. Servers deploy. Work...