Hard-coding or scattering auth handling across the codebase makes security and debugging both worse.
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.