posts projects docs books ui tools about

site

posts
projects
docs
books
ui
tools
about

connect

contact
resume
topics
rss

developers

api
openapi
llms.txt

legal

legal
terms
privacy

© 2026 Chase Pierce

Documentation

Overview
The Playbook

Reference

Docs

Documentation

The architectural playbook I bring to every team: the standards I've landed on, written down so they don't get re-argued in every codebase. New here? Start with the principles.

Start Here

The Playbook
How to read the playbook, the principles behind every standard in it, and a map of the whole book, from HTTP fundamentals to leading the team.

Fundamentals

6

REST & HTTP VerbsWhat GET, QUERY, POST, PUT, PATCH and DELETE promise to clients, caches and retries, and why breaking those promises causes real outages.
Time & Date FormatsRFC 3339 instants in UTC, local wall-clock times with IANA zones for future events, ISO 8601 durations, and iCalendar rules for anything recurring.
Identifier ConventionsUUID v7 as the default key, when integers, v4, v5 or ULIDs are the better choice, and what each format reveals, costs, and breaks when you get it wrong.
Addresses & GeocodingCapturing, standardizing, validating and geocoding addresses, what vendor licenses let you store, and keeping postal city, service point and jurisdiction apart.
Phone Numbers & Email AddressesPhone numbers in E.164 via libphonenumber, email accepted broadly and compared with care, ownership proven, and what was typed kept beside every key.
Text & UnicodeUTF-8 everywhere, four ways to measure a string, NFC for storage, case folding, locale-aware collation, confusables, bidi controls and database encodings.

Product

5

Discovery & User ResearchFinding problems worth solving before a problem statement: weekly customer contact, interviews about past behavior, assumption tests and small usability tests.
Problem Statements & Acceptance CriteriaProblem statements that set the frame, acceptance criteria that state outcomes and leave room for the solution, and hearing the pain behind a request.
BacklogsOne backlog for features, bugs and tech debt, sized to what the team can build, with stale items closed on a schedule and important ideas left to come back.
Roadmaps & CapacityRoadmaps that commit to problems and outcomes, not dated feature lists, with a fixed share of capacity engineering spends on debt, upgrades and improvements.
Release StagesInternal, alpha, beta and general availability as gates: who gets access at each stage, what each one promises, and what must be true before the next.

Development

9

Decisions & Design DocsHow much process a decision deserves, a named decider and a date, disagree and commit, and design docs and ADRs that keep the reasoning findable later.
Repositories & Local DevelopmentOne repository per product, trunk-based development with short branches, one command from clone to running, and formatters and linters CI enforces.
Commits, PRs & Code ReviewConventional Commits, small squash-merged pull requests with a real description, and code reviews that are fast, labeled, and focused on what matters.
Code OwnershipEvery service and directory has an owning team: CODEOWNERS for reviews, a catalog entry for operations, and a README that gets anyone running in one command.
DocumentationDocs as code in the repository, reviewed and checked in CI, sorted by Diátaxis, API reference generated from OpenAPI, and every page owned and kept fresh.
Dependencies & UpgradesLockfiles, SemVer, small continuous upgrades, an LTS runtime policy, vetting new dependencies, and supply-chain safeguards like provenance and pinned CI.
Build vs Buy & VendorsBuy what isn't your differentiator, total cost both ways, vendor evaluation and security review, exit plans, third-party risk, sprawl, open source and renewals.
Tech DebtTreat tech debt like a loan: know which kind you took on, track the interest you pay, budget a steady share to repay it, and modernize with strangler figs.
AI-Assisted DevelopmentWorking with AI coding agents: a person owns every change, review follows measured risk, standards live in the repo, CI enforces them, nothing ships unverified.

Architecture

9

Service BoundariesWhere to draw lines in a system: start with a modular monolith, split only for a reason, give every piece of data one owner, and never share a database.
Retries & TimeoutsWhen to retry, how long to wait, and when to give up: timeouts on every call, exponential backoff with jitter, retry budgets, and what is safe to retry.
Events & Async MessagingPublishing and consuming events reliably: the transactional outbox, idempotent consumers, partition keys for ordering, CloudEvents, and schema evolution.
Background JobsMoving work out of the request: small idempotent jobs, retries with backoff and dead letters, scheduling without overlap, visibility, and shutting down cleanly.
Application CachingWhen a cache earns its place, the patterns for filling and invalidating one, surviving stampedes and cold starts, and what a cache must never be trusted with.
Realtime ConnectionsPushing changes to connected clients: an edge and routing tier, auth on connect, heartbeats, fan-out, resume and catch-up, and surviving reconnect storms.
Waiting Rooms & Admission ControlAdmitting users at the rate a system can serve: capacity per scope, queues with ceilings, honest wait estimates, signed admission tokens and fairness.
Multi-TenancyServing many customers from one system safely: choosing an isolation model, enforcing tenant scope in the database, and keeping noisy neighbors in check.
Replacing a SystemMoving off a legacy system or vendor: Strangler Fig, cutover options, crosswalks, suppressed side effects, reconciliation, rollback windows and exit plans.

Database

5

Database Naming ConventionsNaming and typing conventions for tables, columns, keys, constraints and indexes, so a schema is predictable enough to guess and safe to change.
Transactions & ConcurrencyWhat isolation levels really guarantee, stopping lost updates with optimistic or pessimistic locking, retrying serialization failures, and avoiding deadlocks.
Database PerformanceMeasure before you optimize: reading query plans, designing indexes that earn their write cost, catching N+1 queries, pooling connections, and timeouts.
Zero-Downtime MigrationsChanging a live schema without downtime: the expand and contract pattern, safe backfills, lock-aware DDL, and the order to ship code and migrations in.
Effective Dating & HistoryValid time and recorded time, effective-dated rows and as-of queries in PostgreSQL ranges, versioned plans and prices, snapshots and scheduled changes.

API Design

9

API Design PrinciplesThe rules every endpoint follows: resources and methods, bare JSON with metadata in headers, status codes that mean something, and a Request-Id on all of it.
Naming ConventionsHow API paths are named: plural kebab-case nouns, one level of nesting, IDs not names in URLs, actions as sub-resources, and no formats or versions in paths.
Relationships & ExpansionLinks between resources as their own sub-resources (PUT to link, DELETE to unlink), and related objects as IDs unless the client asks to expand them.
API AuthenticationHow API callers prove who they are: prefixed, hashed API keys, restricted by default, OAuth 2.0 for delegated access, scopes, and 401 vs 403 vs 404.
Versioning & DeprecationHeader-selected, date-named API versions, what counts as a breaking change, and announcing removals on the wire with the Deprecation and Sunset headers.
Choosing an API StyleREST, GraphQL, gRPC and events: what each one optimizes for, what it costs, and how to pick by who the consumer is rather than by what's fashionable.
GraphQL in DepthDesigning a GraphQL schema that survives years of change: nullability, connections, mutation payloads, N+1, cost limits, authorization, caching and federation.
SDK DesignWhen to ship client libraries, generated versus hand-written, and the behavior every SDK should build in: retries, idempotency, pagination and errors.
WebhooksSigned, at-least-once webhook delivery: payload shape, signature verification, retry schedule, and how consumers should dedupe and process events.

Requests & Responses

11

JSON Field ConventionsHow fields are named and typed in JSON bodies: snake_case, absent versus null, string enums, boolean prefixes, and safe handling of 64-bit numbers.
Error ResponsesOne error shape for every failure, status codes that carry the outcome, and the 400 vs 422 and 403 vs 404 calls clients branch on to recover.
IdempotencySafe retries for any write with the Idempotency-Key header: how keys are stored and replayed, and what happens on conflicting or concurrent requests.
PaginationCursor pagination by default, page numbers only for small stable lists, metadata in the Link header, and why offsets break on data that keeps changing.
Filtering & SortingQuery parameter conventions for filtering and sorting collections: field filters, range operators, sort=-created_at, allowlists, and when to use QUERY.
HTTP QUERYSupporting RFC 10008's QUERY method today: one query model behind GET, QUERY and a POST fallback, plus caching, CORS, and where the ecosystem still falls short.
Caching & Conditional RequestsCache-Control, ETags and conditional requests: cheap revalidation with 304, safe concurrent updates with If-Match and 412, and Vary on Api-Version.
Rate LimitingWhy every endpoint is rate limited, what to key limits on, the headers that report them, enforcing them in Redis, and staying up when the limiter fails.
Long-Running OperationsWork that outlives a request: 202 Accepted with an operation resource to poll, Retry-After pacing, webhooks on completion, cancellation, and result retention.
Bulk OperationsBatch endpoints that create or update many resources in one call: size limits, per-item results, partial failure, idempotency, and when to go async.
HTTP CompressionAccept-Encoding and Vary, gzip, Brotli and zstd trade-offs, precompressed static assets, dictionaries, BREACH, and capping decompressed request bodies.

Frontend

9

AccessibilityWCAG 2.2 AA as the baseline: semantic HTML first, keyboard and focus, contrast, reduced motion, and testing that goes beyond what automated tools can catch.
Web PerformanceCore Web Vitals targets measured from real users, performance budgets enforced in CI, and the handful of habits that keep pages fast: less JavaScript first.
Design Tokens & ThemingNamed, semantic design tokens as the only source of color, type and spacing, so light and dark themes are one redefinition away and can never drift apart.
Forms & ValidationNative inputs first, validation that waits until people are done, server errors mapped onto fields, accessible error messages, and forms that never lose work.
Error & Empty StatesDesigning every view's loading, empty, error, partial and success states up front, with messages that explain what to do, retries, and no blank pages.
InternationalizationBuilding software that can be translated and localized: externalized messages with ICU plurals, Intl formatting, locale choice, RTL layouts, and Unicode traps.
SEOSearch engine optimization for engineers: crawling, indexing controls, canonicals, sitemaps, structured data, rendering, redirects, migrations and AI search.
Link Previews & Social CardsHow a page looks when shared, unfurled or installed: Open Graph, X Cards, each unfurler's rules, oEmbed, generated images, icons, the manifest and theme color.
Mobile AppsBuilding iOS and Android apps: native or cross-platform, an API that serves old versions, push, deep links, secure storage, OAuth, store rules and startup.

Building Blocks

21

Audit TrailsRecording who did what, when and why: typed actors, before and after values, same-transaction capture, snapshots, tamper evidence, access logs and exports.
Data Retention & DeletionHow long data is kept and how it is removed: soft vs hard delete, retention windows, GDPR erasure next to append-only financial records, and backups.
Custom FieldsPer-tenant custom fields: JSONB with a definitions table, validation, indexing, option lists, changing definitions, limits, and exposing them everywhere.
Rules as DataPolicies that vary by jurisdiction, channel and date as versioned, sourced data: stages, final checks, precedence, stored deadlines and decision records.
Workflows & State MachinesBusiness processes that outlive a request: explicit states guarded by the database, durable engines vs a jobs table, sagas, timers and human approvals.
Matching, Merging & Many SourcesReconciling one real thing reported by many sources: observations, per-field survivorship, crosswalks, match-before-create, reversible merges and overrides.
SearchProduct search: Postgres full-text and trigrams first, when to add a search engine, keeping it in sync, relevance, tenant filtering, hybrid search and quality.
Imports & ExportsSpreadsheet import as a product feature: encodings, mapping, row-level errors, dry runs, re-import and undo, plus safe CSV and XLSX exports and portability.
Third-Party IntegrationsBeing a client of other companies' APIs: connections per tenant, OAuth with PKCE, token refresh races, sync with cursors and webhooks, their limits.
Notifications & ConsentSending email, texts and push safely: a consent ledger per contact point and purpose, one outbound gate, send-time re-checks, templates, and the message log.
File UploadsUploads straight to storage on a scoped credential, resumable protocols, checks on what arrived, hostile files, and a gate before a file is usable.
Media CompressionLossless and lossy coding, the pipeline image and video codecs share, generation loss, formats by content class, perceptual metrics, and what encoding costs.
Generated DocumentsReceipts, invoices, statements and contracts as PDFs: renderers compared, templates as code, background rendering, numbering, PDF/A, PDF/UA and delivery.
Offline-First SyncApps that work without a network: a scoped local store, commands in a device outbox, attachments apart, two clocks, and conflict rules decided per command type.
Location Tracking & GeofencesPositions with accuracy, mobile sampling limits, geofence arrival with dwell and hysteresis, ETAs, safe tracking links, and consent and retention.
Reservations & HoldsSelling scarce slots and inventory: holds that expire on read, caps per holder, idempotent confirmation, and a database that refuses double-booking.
Automated Risk DecisionsRules and models that decide about people: score bands with a human middle, decision records, late labels, holdouts, error costs, fail-open or closed, appeals.
Trust & SafetyModeration for any product where people post, chat or trade: policies, report queues, automated detection with review, penalties, appeals and reporting duties.
Weighing Competing ObjectivesFolding many goals into one solver score: levels or weighted sums, hard and soft constraints, money as the unit, integer scaling, replay and explanations.
LLM FeaturesSummaries, extraction, classification, drafts and answers inside a product: structured outputs, retrieval, evals as tests, latency, cost and fallbacks.
AI Agents in the ProductAgents that act for customers and operators: narrow tools, typed results, decisions in code, identity checks, handoff, evals, auditing and the law.

Security

14

Threat ModelingA lightweight threat model for every new service or trust boundary: four questions, a data flow diagram, a STRIDE pass, and mitigations tracked as work.
Authentication & SessionsHow people sign in and stay signed in: passwords per NIST, passkeys, MFA, recovery, server sessions over browser JWTs, and stopping credential stuffing.
Choosing an Identity ProviderHosted platforms, self-hosted servers and in-app libraries for sign-in: Auth0, Clerk, WorkOS, Cognito, Keycloak, FusionAuth, Better Auth, and how to choose.
SSO & Identity FederationSigning people in through someone else's identity provider: OIDC with PKCE, validating ID tokens, SAML for enterprises, per-tenant SSO, SCIM and logout.
AuthorizationDeciding what an authenticated caller may do: RBAC, ABAC and relationship-based models, where checks belong, object-level access, and testing deny-by-default.
API SecurityThe OWASP API Security Top 10 (2023), risk by risk, and the playbook practice that prevents each one, so security is designed in rather than bolted on.
Security Headers & CSPThe response headers every site should send, a strict Content Security Policy, and how to roll CSP out safely with Report-Only mode before enforcing it.
Sensitive DataHandling card data and PII: keep PCI scope small with tokenization, never log secrets, redact by default, and treat access to sensitive data as an event.
Encryption at RestDisk, database and field encryption and what each stops: envelope encryption, KMS or HSM, rotation jobs, crypto-shredding, blind indexes and key-use logs.
Support Access & Internal ToolsHow staff reach customer data safely: delegation over impersonation, read-only by default, reasons, banners, time limits, approvals and internal consoles.
Infrastructure & Employee AccessHow engineers reach production: SSO for every tool, zero trust over VPNs, device posture, cloud roles, short-lived credentials, just-in-time and break-glass.
Vulnerability ManagementFinding and fixing vulnerabilities faster than they're exploited: remediation targets by risk, CVSS with EPSS and KEV, SBOMs, and patching by redeploying.
Securing Software UpdatesAn updater that survives a hostile network: TUF's threat model, keys split by role, signed monotonic manifests, verified chunks and deltas, and staged rollout.
AI & LLM SecurityBuilding with LLMs and agents safely: the OWASP Top 10 for LLM Applications, why prompt injection is unsolved, and designing so it can't do damage.

Money

7

Money & AmountsHow monetary amounts are represented: integer minor units, an explicit ISO 4217 currency on every amount, and rounding rules that never lose a cent.
Payment States & LedgersExplicit state machines for financial objects, append-only records, and a double-entry ledger, so every balance can be explained and nothing is ever edited.
Multi-Currency & FXCharging in one currency and settling in another: who takes the FX risk, locking a quoted rate, storing both amounts, refunds, and checkout conversion.
Subscriptions & Recurring BillingSubscription states, billing periods and anchors, idempotent renewals, proration, dunning, cancellation, and the automatic renewal laws that govern all of it.
Usage-Based Billing & MeteringMetering events, aggregation and rating, late events and period close, credits and commitments as a ledger, spend alerts, invoice evidence, and engines.
Sales Tax & VATIndirect tax as data: a tax code per item, tax as a quote until the invoice finalizes, engines, exemptions, sourcing, US nexus and VAT on digital sales.
Accounting & Revenue RecognitionWhat the product owes the books: deferred revenue as ledger facts, ASC 606 and IFRS 15 basics, breakage, accounting sync, month-end close and write-offs.

Compliance

8

PCI DSSWhat PCI DSS v4.0.1 demands of engineering: merchant and service provider levels, which SAQ or assessment you land on, and shrinking scope.
SOC 2SOC 2 as an engineer meets it: the Trust Services Criteria, Type 1 versus Type 2, and how reviews, pipelines and on-call become the evidence auditors test.
GDPR & PrivacyGDPR as a design constraint: lawful bases, controllers and processors, data subject rights, transfers, 72-hour breach notice, and how each maps onto a system.
HIPAAHIPAA for engineers: covered entities and business associates, the BAA chain, what the Security Rule asks of a system, breach deadlines, and de-identification.
Calls, Texts & EmailThe law behind contacting customers: TCPA consent and revocation, calling hours, AI voices and disclosure, call recording, CTIA texting rules and CAN-SPAM.
Electronic Signatures & RecordsE-signatures for engineers: ESIGN and UETA, consumer consent, embedded or remote signing, signing evidence, versioned click-through terms and retention.
Children's Privacy & Age AssuranceBuilding for children: COPPA and its 2025 amendments, parental consent, the UK Children's Code, age assurance, state app-store laws and data minimization.
Open-Source LicensesLicense families and what triggers them in SaaS and shipped software, SPDX, scanning in CI, an allow and deny policy, attribution, CLAs, and deal diligence.

Quality

11

Quality StrategyWhat quality means, why it's the whole team's job and not a gate, what quality engineers are for, shift-left and shift-right, and risk-based test depth.
Testing StrategyThe test pyramid and why it has that shape, what each test type covers, real databases over mocks, deterministic fixtures, and zero tolerance for flaky tests.
Automated TestingChoosing test tools, end-to-end tests that survive redesigns, page objects vs helpers, property and snapshot tests, suite speed, and failure artifacts.
Manual & Exploratory TestingWhat people catch that scripts can't, chartered exploratory sessions, heuristics, bug bashes, acceptance testing, and when manual work earns a place.
AI-Assisted TestingAgents that drive a real browser to explore, find UI and UX gaps, and write bug reports, and how every confirmed finding becomes an automated test.
Test Data & EnvironmentsWhere tests run and why shared staging decays, seeding, synthetic data over production copies, third-party sandboxes, isolation, and test accounts in prod.
Visual & Cross-Platform TestingA browser and device matrix from real usage with support tiers and version floors, desktop OS differences, device clouds, mobile checks and visual regression.
Load & Performance TestingPerformance budgets tied to SLOs, the test types and when to run each, realistic traffic, capacity headroom, and the measurement trap that hides slow responses.
Defects & TriageA good bug report, severity and priority as separate axes, triage that keeps the backlog honest, a regression test for every fix, and escaped-defect reviews.
Release ReadinessReadiness as pipeline gates, exit criteria by risk tier, when a go/no-go earns its place, the release checklist, the first hour, and when to freeze code.
Quality MetricsQuality metrics worth tracking (change fail rate, escaped defects, flake rate, time to detect), the ones that mislead, and mutation testing.

Delivery

7

CI & Continuous DeploymentFast, trustworthy CI with parallel jobs and real services, then every merge to main deployed on its own, and what must be true before that is safe.
Feature Flags & Progressive RolloutSeparating deploy from release: flag types and lifetimes, OpenFeature for vendor-neutral evaluation, percentage and canary rollouts, kill switches, and cleanup.
Deployment StrategiesRecreate, rolling, blue-green, canary and dark launches: how each one rolls back, what it costs, and why the database is usually the real constraint.
Where to Run ItChoosing compute: a platform first, managed containers next, Kubernetes only with a platform team, and what functions, VMs and metal cost to own in people.
Containers & Immutable InfrastructureWhy you rebuild and redeploy the whole artifact instead of maintaining servers, and how to build container images that are small, patched, signed and safe.
Infrastructure as CodeInfrastructure declared in code and changed by review: remote locked state, plan and apply from CI, drift detection, modules, and secrets kept out of state.
Mobile ReleasesShipping mobile apps when you can't roll back: release trains, phased rollouts, flags, minimum versions, health gates, signing, beta tracks and OTA rules.

Observability

9

ObservabilityRequest IDs on every response, the three signals and the IDs that join them, bounded metrics beside wide events, and a map of the Observability section.
LogsStructured JSON logs, levels with meaning, trace correlation, the OpenTelemetry logs model and bridges, what never to log, sampling noise, and retention.
MetricsInstrument types, temporality, histograms that aggregate, RED and USE, cardinality and its bill, exemplars, recording rules, and pull versus push.
Tracing & SamplingSpans, kinds, status and attributes, what deserves a span, tracing through queues, batches and webhooks with span links, and head and tail sampling.
Instrumenting with OpenTelemetryAPI and SDK, zero-code agents and the Kubernetes Operator, resources, failing open, semantic conventions, OTLP, propagation, signal status and GenAI spans.
Running the OpenTelemetry CollectorDeployment patterns, an annotated agent and gateway config, distributions and ocb, queues and retries, monitoring, securing, and managing a fleet with OpAMP.
Errors & ProfilingError tracking with grouping, releases, symbols and PII scrubbing, and continuous profiling from pprof to eBPF and OpenTelemetry's profiles signal.
Frontend & Synthetic MonitoringCore Web Vitals from real users, traces that start in the browser, synthetic checks from several regions, and health checks that tell Kubernetes the truth.
Dashboards & AlertsService dashboards as code with deploy markers, alerts on symptoms and burn rates, routing, runbooks, alert fatigue, silences and testing alerts.

Operations

8

Environments & ConfigurationOne build everywhere: what each environment is for, config validated at boot, secrets in a manager and never the repo, rotation built in, and who deploys where.
Kubernetes OperationsRunning services on Kubernetes without the classic outages: requests and limits, probes, disruption budgets, graceful shutdown, secrets, GitOps and upgrades.
SLOs & Error BudgetsPicking SLIs that reflect what users feel, setting SLO targets, spending error budgets deliberately, and alerting on burn rate instead of raw thresholds.
On-Call & RunbooksA sustainable on-call rotation: who carries the pager, paging and escalation, written handoffs, a runbook for every alert, and time budgeted to drive toil down.
Incidents & PostmortemsRunning an incident: declare early, a commander who doesn't debug, mitigate before diagnosing, update on a clock, then a blameless postmortem that sticks.
Disaster RecoveryRecovery targets set from business impact, backups you've actually restored, the four DR strategies and their cost, and infrastructure rebuilt from code.
Cost & FinOpsCloud cost as an engineering input: unit economics, an owner for every dollar, budgets and anomaly alerts, the few levers that matter, and free-tier cliffs.
Customer Support OperationsRunning support as a system: channels, tickets with states and context, classify and route, macros, bots that hand off, escalation, metrics and QA.

Telemetry & Analytics

5

Event Design & InstrumentationWhat to track and why: questions before events, object_action names, properties and context, versioned schemas, tracking plans as code, and identity stitching.
Collecting EventsGetting events from devices and servers to the warehouse: batching SDKs, retries with event IDs, two clocks, sampling, page lifecycle, CDPs, late data and cost.
Consent & Privacy in TelemetryAnalytics within the rules: consent before device storage, gating SDKs, opt-out signals like GPC, minors, minimizing, pseudonymous IDs, retention and deletion.
Product AnalyticsWhat product analytics answers and how: funnels, cohorts and retention curves, active users and stickiness, segments, attribution, north stars and pitfalls.
Experimentation & A/B TestingRunning A/B tests you can trust: units and hashing, sample size, peeking and sequential tests, sample ratio checks, guardrails, CUPED, interference and ethics.

Data Platforms

9

Separating Production from AnalyticsWhy analysts never query production primaries, where read replicas stop helping, and how CDC, events, contracts and reverse ETL cross the boundary safely.
Warehouses, Lakes & LakehousesFrom Hadoop to cloud warehouses and open table formats: what Iceberg, Delta Lake and Hudi each provide, Parquet and ORC, and how I choose where data lives.
Running a Cloud WarehouseOperating Snowflake, BigQuery and Redshift: how each bills compute, workload isolation, table layout, caches, loading, recovery windows, spend and sharing.
Real-Time Analytical DatabasesClickHouse, Druid, Pinot, StarRocks and DuckDB: how columnar storage and vectorized execution work, where real-time OLAP beats a warehouse, and update costs.
Streaming & Event ProcessingLogs, partitions and consumer groups in Kafka, Kinesis, Pulsar and Redpanda; event time, windows, watermarks, state and exactly-once in Flink and Spark.
Data Pipelines & AnalyticsMoving production data into analytics without breaking either: CDC, ELT, tested transformations, replayable pipelines, contracts and one definition per metric.
Modeling Analytical DataShaping warehouse data people can trust: grain, facts and dimensions, conformed dimensions, slowly changing history, dbt layers, semantic layers and tests.
Data Science & ML PlatformsRunning data science without breaking production: notebooks, reproducibility, feature stores and skew, experiment tracking, model registries, serving and drift.
Data Governance & AccessKnowing what data you hold and who can see it: owners, catalogs and lineage, PII tags, masking and row-level security, quality contracts, erasure and cost.

Leadership

9

Hiring & InterviewsHiring engineers on evidence: define the bar first, structured interviews with rubrics, work samples over puzzles, and independent feedback before debriefs.
OnboardingGetting a new engineer to a merged change in week one: access ready on day one, a buddy, a written 30/60/90 plan, real starter tasks, and on-call by stages.
1:1s & FeedbackRunning 1:1s that belong to the report, giving feedback that's specific and timely with situation, behavior and impact, and having the hard conversations early.
Career LaddersWritten levels described by scope and impact, equal IC and management tracks, staff and principal archetypes, and promotions that recognize sustained work.
Performance ReviewsPerformance reviews with no surprises: continuous feedback, evidence against the ladder, calibration that checks bias, and humane handling of underperformance.
Team StructureDesigning teams on purpose: Conway's law, stream-aligned teams that own services end to end, platforms run as products, and cognitive load as the sizing limit.
Growing ManagersGrowing engineering managers: management as a career change, not a promotion, a new manager's first 90 days, coaching managers, and the way back to IC.
Communication & MeetingsWritten by default, async first, meetings that earn their place, decision logs, status updates that lead with the ask, chat norms and working across time zones.
Measuring EngineeringEngineering metrics that improve the system, not rank people: DORA, SPACE and DevEx, developer surveys, PR flow, and measuring AI-assisted work honestly.

Reference

1

API ReferenceInteractive reference for the syntaqx API, generated from its OpenAPI description, with a live console to send requests and inspect responses.