Too little logging hides the story, but noisy logs bury the one field or event you actually need.
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.