Support the builders behind API products
Ten topics, one lesson each: a short primer, links to primary documentation, and exercises to prove the concept has stuck. Start with HTTP.
The request/response cycle, methods, status codes, and headers — the shared language of every API.
Start lessonTelling identity failures apart from permission failures: API keys, OAuth, JWTs, scopes and roles.
Start lessonWebhooks, retries, ordering, idempotency, and diagnosing missing or duplicate callbacks.
Start lessonAssessing impact, escalating with evidence, and writing root-cause analyses that prevent recurrence.
Start lessonUsing AI tools as a force multiplier — triaging tickets, summarizing logs, and drafting RCAs faster without losing rigor.
Start lessonZendesk, Jira, Linear, LaunchDarkly, and billing tools — the stack a ticket actually passes through.
Start lessonTurning a customer’s "it just stopped working" into a reproducible request in Postman.
Start lessonStructuring a walkthrough, narrating through a live failure, and handling questions you don’t have the answer to.
Start lessonSame fundamentals, richer state machine: workers, tasks, and reservations that can each fail independently in a contact center.
Start lessonWhat breaks when a whole company logs in through their own identity provider instead of your user table.
Start lessonWhat building this project taught me.
/projects/onboard stays the single-page overview of TSE skills. This trail is where each of those topics grows into a real lesson — definitions, source reading, and an exercise — one topic at a time.
Each topic card only becomes clickable when its lesson page ships. That keeps the trail honest about what's actually built versus what's still a plan.
