Letting raw row tuples leak upward makes the service layer harder to read and easier to break.
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.