Assuming every CSV row is well-formed usually delays failure until much later in the pipeline.
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.