Heavy runtime patching can hide dependencies and make behavior difficult to reason about.
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.