A workplace-jargon deck — 76 terms like sidecar and canary, with how they're used
The owner kept hitting workplace and infra jargon he'd never heard — sidecar, canary, dark launch, toil, bikeshedding — and felt lost. Generated and native-verified 76 high-frequency jargon cards, each with the meaning, a real sentence using it, and the common misuse to avoid, and routed the long tail to the on-demand term finder.
Right after the term-finder went in, the owner hit the wall behind it: workplace jargon. Words like "sidecar" — thrown around constantly in infra talk — that he'd simply never heard, and the volume of them felt infinite and demoralizing. The honest framing is that it isn't a memory failure; nobody is born knowing "bikeshedding," you just hear it once and it sticks.
So the approach is two-pronged: cover the high-frequency set as a drillable deck, and send the long tail to the on-demand term finder (/askright) rather than pretending to card every term. The deck is 76 curated terms — containers and infra (sidecar, daemon, cron job, blue-green, canary, dark launch, shadow traffic, feature flag, kill switch, autoscaling, cold start), data and ops (backfill, replay, dry run, source of truth, drift, throttle, debounce, fan-out), process and culture (dogfooding, bikeshedding, yak shaving, toil, tech debt, scope creep, bus factor, on-call, postmortem, RFC, ADR, spike, timebox, LGTM, nit, P0/SEV, war room, incident commander), git (cherry-pick, squash, force push, draft PR), and code (heisenbug, boilerplate, glue code, shim, polyfill, leaky abstraction).
Each card carries more than a definition: the Korean meaning and when you hear it, a sentence a real engineer says with the term, the collocation pattern, related terms, and the misuse to avoid — because the misuse is where non-natives get caught. A sidecar shares the pod and dies with the main container; a canary runs in production on real users, not in staging; a kill switch disables a live feature in seconds and isn't the same as a code rollback; "daemon" is said "demon." Generated then reviewed by a picky native for correctness, integrated into the existing jargon category (now 86), zero entities, tsc clean.
The reusable lesson: jargon is unbounded, so don't try to enumerate it — deck the high-frequency core and lean on the on-demand finder for the rest, and always teach a term with a real usage sentence plus the trap, not just a gloss.