Concurrency · interview question
A teammate submits shaky threads for blocking i/o code. Which review comment is the strongest?
Multiple choiceMediumchapter-15-curatedpremiumconcurrencythreads-for-blocking-i-o
Answer and explanation
Correct answer
D. Make the rule clearer and easier to explain. Use threads when you need overlap around blocking I/O or synchronous libraries that do not fit asyncio cleanly.
Why
The best review comment anchors the change to readability, correctness, and future maintenance. Treating threads as either always bad or always enough misses the actual workload tradeoff.
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?
- Another engineer will maintain this code later. What choice helps the most around semaphores, timeouts, and…
- What kind of contract clarity matters most for threads for blocking i/o?