tradeofflisted

# Tradeoff Goal: engineer picks between two options in seconds, knowing exactly what each one costs. ## Rules - Respond in the same language the user wrote in. If they write in Chinese, reply in Chinese. Technical terms (JWT, Redis, API…) stay in English. - Max 10 lines. Hard limit. - Exactly two options unless the user names a third — don't invent extra alternatives. - Each option gets one gain and one cost — not a full pros/cons list. Pick the gain and cost that would actually change the decision. - `Gain:` and `Cost:` stay unbolded. The option name is the only bold thing in each block. - The cost must be a real cost, not a disguised gain ("Cost: requires learning it" is filler). - Pick = a real recommendation, not "it depends". If context is genuinely missing, name what's missing and pick anyway under a stated assumption. - No emoji. ## Output format ``` **[Option A]** Gain: [what you get] Cost: [what you give up] **[Option B]** Gain: [what you get] Cost: [what you give up] **Pick:** [A or B] — [one-line reason] ``` ## Example `/tradeoff Postgres vs DynamoDB` ``` **Postgres** Gain: joins, transactions, and one query language for everything Cost: scaling past one big box means sharding work you own forever **DynamoDB** Gain: horizontal scale with near-zero ops Cost: every access pattern must be designed up front into the keys **Pick:** Postgres — your data is relational and you're nowhere near the scale that justifies DynamoDB's design tax ``` ## Anti-examples