Confusing two adjacent concepts — TCP vs UDP, mean vs median, OAuth vs JWT, debounce vs throttle — costs exam points, fills your codebase with bugs you can’t reproduce, and makes interview answers wander. The fix isn’t more reading; it’s a structured side-by-side that surfaces the discriminating question — the one yes/no that flips the answer between A and B. These prompts force that structure: tables with one-word cells, decision trees with 4 forks, mechanism-vs-output pairs, worked examples solved twice. Pair with the theory simplification prompts when one of the concepts itself needs unpacking before the comparison lands.
Best for
- Exam prep
- Technical interview prep
- Writing tutorials and study guides
- Teaching juniors
- Resolving “wait, what is the difference?” moments
1. Side-by-side table
Compare {A} vs {B}. Output: a 6-row table — definition, when used, key difference, common confusion, gotcha, real-world example. ≤8 words per cell.2. Discriminating-question generator
For concepts {A} vs {B}, generate 5 discriminating questions: "if you ask X, the answer tells you which one applies". Each question should isolate one decision dimension.3. ELI5 vs PhD pair
Explain the difference between {A} and {B} twice: (a) as if to a smart 12-year-old, (b) as if to a graduate student in {field}. Mark which precision is lost in the simplified version.4. Why-people-confuse-them analysis
Why do people confuse {A} and {B}? Output: top 3 sources of confusion (shared vocabulary, similar diagrams, overlapping use cases), with a clarifying analogy for each.5. Decision tree: pick one
Build a 4-step decision tree to pick between {A} and {B}. Each step is a yes/no question that narrows the choice. End with the verdict and 1 edge case where the verdict flips.6. Edge-case comparison
Compare {A} and {B} at the edges: scale limits, failure modes, security implications, performance trade-offs, cost. Output: a 5-row table.7. Worked-example pair
Give the same problem solved with {A} and again with {B}. Use {problem context}. Mark which steps differ, which produce different results, and what each result tells the user.8. Three-way comparison
Compare {A}, {B}, and {C}. Output: a 3-column table on definition, use case, key benefit, key drawback. End with a 2-sentence guide on which to pick by default.9. Same-output-different-mechanism comparison
{A} and {B} produce similar outputs by different mechanisms. Explain each mechanism in 2 sentences, then list 3 cases where the mechanism difference matters in practice.10. “Same word, different meaning” disambiguation
The term {term} means different things in {context A} vs {context B}. Explain each meaning, give a sentence-level example from each context, and list 3 mistakes that happen when readers conflate them.11. Historical-evolution comparison
How did {newer concept} evolve from {older concept}? Output: what stayed the same, what changed, what new problem the newer one solves, and what edge case the older one still handles better.12. Comparison cheat-sheet for exam
Make a 1-page cheat sheet comparing {A} vs {B}. Optimized for memorization before an exam. Output: 1 mnemonic, 5 differentiators, 3 sample exam questions with answers.Common mistakes
- Listing 10 features without naming the discriminating one — which is the only one that drives the decision
- No worked example — readers can recite the difference but still pick wrong in code
- Pretending two concepts are unrelated when one evolved from the other, hiding the actual decision rule
- No edge case where one works and the other fails — that’s where understanding actually lives
- Cheat sheets that try to cover everything instead of the 5 differentiators you’d actually be tested on
- Comparing on dimensions that don’t change the answer (e.g., “both are widely used”)