Refactoring · interview question
A bug appears around types during refactors. What is the strongest first debugging move?
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
D. Trace one concrete example, inspect the state transitions, and compare them to the intended rule before rewriting anything.
Why
That approach is reliable because it creates evidence. Refactoring without any contract guidance can devolve into manual grep and hope.
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?
- Which option is the safer default when shipping code around 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?