Concurrency · interview question
Another engineer will maintain this code later. What choice helps the most around gil judgment?
Multiple choiceHardchapter-15-curatedpremiumconcurrencygil-judgment
Answer and explanation
Correct answer
B. 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. Clear GIL explanations are strong interview signals because many candidates stay vague here.
Test yourself on Concurrency
A free test with instant, explained results. No account needed.
More Concurrency questions
- If you wrote a test around cancellation, what should the test prove first?
- What production risk should you worry about most if cancellation is handled lazily?
- Which option treats cancellation as an engineering policy decision instead of a syntax trick?
- Which option describes the most likely pitfall around cancellation?
- What does a strong engineer do when reasoning through cancellation code?
- You cannot rewrite everything today. What is the best incremental improvement around async def and await?