Functions · interview question
What is the clearest sign that code around return values should be refactored?
Multiple choiceMediumchapter-2-curatedpremiumfunctionsreturn-values
Answer and explanation
Correct answer
D. When the rule is no longer easy to trace, explain, or change without breaking nearby behavior.
Why
A refactor is justified when the code stops communicating its intent. A good return value lets the caller continue the workflow with a clear next piece of information.
Test yourself on Functions
A free test with instant, explained results. No account needed.
More Functions questions
- Which judgment is strongest when choosing a data shape for return values?
- When is return values being used in the wrong way?
- What does a strong engineer do when reasoning through function extraction code?
- A teammate submits shaky function extraction code. Which review comment is the strongest?
- What is the healthiest performance judgment around function extraction?
- Which move is the best default when return values becomes part of this workflow?