Refactoring · interview question
Which option is the safer default when shipping code around types during refactors?
Multiple choiceHardchapter-10-curatedpremiumrefactoringtypes-during-refactors
def build_receipt(order_id: str, subtotal: float, shipping: float) -> str:
return f"{order_id}:{subtotal + shipping:.2f}"Answer and explanation
Correct answer
A. Choose the simpler shape that keeps the rule obvious, validated, and easy to observe in logs or tests.
Why
The safest default is usually the one that lowers ambiguity and makes errors easier to diagnose.
Test yourself on Refactoring
A free test with instant, explained results. No account needed.
More Refactoring questions
- What kind of contract clarity matters most for types during refactors?
- Another engineer will maintain this code later. What choice helps the most around types during refactors?
- Which explanation would best help the team align on types during refactors?
- Which judgment is strongest when choosing a data shape for types during refactors?
- Which move is the best default when types during refactors becomes part of this workflow?
- What is the healthiest performance judgment around types during refactors?