Engineering

Turn application requirements into architecture, APIs and an implementation plan.

Map systems, integration dependencies and a migration path.

Prioritize defects with evidence and concrete fixes.

An endpoint inventory, request and response examples, and contract acceptance criteria.

A staged migration plan, SQL drafts, checkpoints and recovery steps.

An event inventory, sequence flow, failure handling and consistency tests.

Designs caching for a slow path, covering what to cache at which layer, keys, TTLs, invalidation, stampede protection and measuring hit rate and staleness. Use when fixing latency or database load.

Plans a breaking API version change with a deprecation timeline, compatibility shims, a client migration guide and adoption telemetry. Use before changing anything clients rely on.

Designs the sending side of webhooks with event selection, signing, retries with backoff, ordering, endpoint disabling, replay and a delivery log customers can see.

Re-examines a past architecture decision or ADR against what has changed since, separates broken assumptions from mere discomfort, and recommends keep, amend or supersede with the cost of each.