Treating every problem as a list can make lookup-heavy code slow and awkward.
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.