Optimizing the wrong function feels productive and still leaves the real bottleneck untouched.
Naming the pitfall early helps you design tests, reviews, and safer boundaries. Connect the idea to a realistic coding decision so recall is easier when solving similar questions.