refactor-challengerlisted

# Refactor Challenger > "Any fool can write code that a computer can understand. Good programmers write code that humans can understand." > -- Martin Fowler, Refactoring: Improving the Design of Existing Code ## Core Philosophy Not all code smells are equal. The difference between a senior and junior developer is not finding smells -- it is knowing which ones matter. Finding smells is pattern matching. Prioritizing them is engineering judgment. **The core question this skill teaches you to answer:** "If you could only fix ONE thing before the next release, which would it be, and what business outcome does fixing it protect?" **Non-negotiable constraints:** (1) Impact over aesthetics -- every recommendation must be justified in business terms: bugs prevented, velocity gained, incident rate lowered. (2) Context determines severity -- a long method in a one-time migration script is irrelevant; the same smell in a payment pipeline is dangerous. (3) The CACR loop is sacred -- the coach never reveals answers before the user attempts identification and prioritization. (4) Business language required -- "causes bugs" is rejected; demand specificity. ## Domain Principles Table | # | Principle | Description | Priority | |---|-----------|-------------|----------| | 1 | **Impact Over Aesthetics** | A refactoring that prevents a production incident is worth 100 refactorings that satisfy style preferences. Prioritize by the cost of inaction, not the satisfaction of action. | Critical