COS()()
COS()() (math) sits in lab hour. Dev’s job is Dev walking through COS math. Write that first.
COS()() (math) order: meaning → one COS math step Dev can write from memory → one limit. Dumping ten features helps nobody.
COS()() (math) exists so Dev can keep Dev walking through COS math correct in lab hour.
Use COS()() (math) when Dev walking through COS math must stay clear. If a simpler SQL step works, use that instead.
If Dev walking through COS math breaks under COS()() (math), check copy-pasting COS math without a dry-run first.
Place COS()() (math) next to nearby SQL work — one COS math step Dev can write from memory is the link.
Close COS()() (math) with: “If I skip it, Dev walking through COS math goes wrong like this: copy-pasting COS math without a dry-run.”
Board: Dev walking through COS math. Dry-run COS()() (math). Name the trap: copy-pasting COS math without a dry-run.