POW()()
Don’t start POW()() (math) with jargon. Start with a POW math dry-run. That is the whole point.
Do POW()() (math) once by hand. one POW math step Dev can write from memory. Change one input. Say the new result out loud.
POW()() (math) exists so Dev can keep a POW math dry-run correct in lab hour.
POW()() (math) shows up in lab hour. Name a POW math dry-run, not “a real-world scenario”.
POW()() (math) miss — copy-pasting POW math without a dry-run. Fix it before you talk about advanced SQL.
POW()() (math) is not a lonely heading. Dev ties it to a POW math dry-run.
Close POW()() (math) with: “If I skip it, a POW math dry-run goes wrong like this: copy-pasting POW math without a dry-run.”
Board: a POW math dry-run. Dry-run POW()() (math). Name the trap: copy-pasting POW math without a dry-run.