Methods · History, human story & context

Predecessor comparison

Understand why the current way of doing something looks the way it does, by finding out what it replaced and what was wrong with that.

When to use this: When you want to go deeper
Learning impact: Reliable gain
Learning evidence: Credible with caveats
Where you are with the topic: Building understanding
How often to use it: Useful once for a topic

When to use it

A notation, convention, or standard feels arbitrary and you resent memorising it.
You can use the current method but cannot say what it replaced.
You want to know what the current approach is bad at, the trade that came with the upgrade.

What to ask AI

Type something like: "[Thing] feels arbitrary to me. What did it replace, and what specifically went wrong with the earlier approach that made this necessary?"

Follow with: what was given up, and which parts are vestigial.

Keep the hard part on your side: you state how the current design answers the predecessor's failure before you memorise more rules.

How it helps

Every established method is a solution to a problem you may never have met, because the solution worked well enough that the problem stopped happening.

That is why so much material feels arbitrary: you are handed an answer without its question.

Predecessor comparison recovers one step back: what came immediately before, and what specifically went wrong.

There is a second payoff: knowing the predecessor tells you what the current thing is bad at. Every replacement is a trade.

How to run it

Pick something that feels arbitrary: a notation, convention, procedure, or standard.
Ask what it replaced, the immediate predecessor, not the whole history.
Ask what went wrong with that earlier approach.
Ask what was given up in the trade.
Ask which parts exist only for historical reasons.
Check the account: convention origin stories are often myths.

Example exchange

You

dy/dx still feels arbitrary to me. What did people use before it, and what specifically went wrong with that earlier approach?

Earlier habits leaned on geometric slope talk and verbal ratios that did not compose cleanly for chained rates. The failure was operational: hard to calculate with. What does fraction-like notation buy you?

You

I can cancel and chain rates the way I already do with fractions.

Good. Next, where does treating dy/dx literally as a fraction mislead you?

Copyable prompt

[THING] feels arbitrary to me. What did it replace, and what specifically went
wrong with the earlier approach that made this necessary?

The Tell

Here is how you know this method has flipped: you can tell the story of what came before and still find the current thing arbitrary.

The connection did not land, you collected an anecdote instead of a design reason.

Principle evidence

Strength of the underlying learning idea, not a claim about AI products.

The underlying learning idea is rated moderate. Contrasting cases and conceptual-change logics support learning by seeing what the current method replaced and why the earlier approach failed.

AI delivery evidence

Whether an AI tutor delivers this method well is a separate question.

AI-supplied histories can invent or Whiggishly simplify predecessors. Verify the account; delivery is speculative even when the contrast principle is sound.