Memory · interview question
Another engineer will maintain this code later. What choice helps the most around long-lived objects?
Multiple choiceHardchapter-16-curatedpremiummemorylong-lived-objects
Answer and explanation
Correct answer
C. Make the rule obvious in names, flow, and boundaries so the next reader does not have to reverse-engineer your intent.
Why
Maintainability comes from explicit intent. Interviewers respect candidates who can explain object lifetime as well as allocation.
Test yourself on Memory
A free test with instant, explained results. No account needed.
More Memory questions
- What kind of contract clarity matters most for tracing allocations?
- Which explanation would best help the team align on long-lived objects?
- Which option is the safer default when shipping code around tracing allocations?
- A bug appears around long-lived objects. What is the strongest first debugging move?
- Which option treats tracing allocations as an engineering policy decision instead of a syntax trick?
- If long-lived objects fails in production, what handling philosophy is strongest?