Assuming user or partner input is well-formed spreads insecurity through the entire workflow.
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.