Concurrency · interview question
What is the clearest sign that code around threads for blocking i/o should be refactored?
Multiple choiceMediumchapter-15-curatedpremiumconcurrencythreads-for-blocking-i-o
Answer and explanation
Correct answer
B. When the rule is no longer easy to trace, explain, or change without breaking nearby behavior.
Why
A refactor is justified when the code stops communicating its intent. Use threads when you need overlap around blocking I/O or synchronous libraries that do not fit asyncio cleanly.
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?