Skipping DTOs can make the service layer speak in partner-specific language forever.
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.