Logging everything 'for debugging' often leaks exactly the data you most needed to protect.
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.