Memory · interview question
A teammate submits shaky long-lived objects code. Which review comment is the strongest?
Multiple choiceHardchapter-16-curatedpremiummemorylong-lived-objects
Answer and explanation
Correct answer
A. Make the rule clearer and easier to explain. Inspect caches, buffers, and retained rows to find why data lives past its useful moment.
Why
The best review comment anchors the change to readability, correctness, and future maintenance. If everything is kept 'just in case', memory usage becomes a design problem rather than a garbage collector problem.
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?