Concurrency · interview question
Another engineer will maintain this code later. What choice helps the most around semaphores, timeouts, and cancellation?
Multiple choiceMediumchapter-15-curatedpremiumconcurrencysemaphores-timeouts-and-cancellation
Answer and explanation
Correct answer
D. 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 like answers that mention backpressure, limits, and cleanup.
Test yourself on Concurrency
A free test with instant, explained results. No account needed.
More Concurrency questions
- What kind of contract clarity matters most for task coordination?
- What production risk should you worry about most if task coordination is handled lazily?
- A senior interviewer asks for one tradeoff behind semaphores, timeouts, and cancellation. What is the strongest…
- Which explanation would sound strongest in an interview when discussing threads for blocking i/o?
- What kind of contract clarity matters most for threads for blocking i/o?
- What is the clearest sign that code around threads for blocking i/o should be refactored?