Which of the following are considered pitfalls of directly using threads in your code?

Race conditions are a significant pitfall of directly using threads in your code because they occur when multiple threads access shared resources simultaneously, leading to unpredictable results. This situation arises when one thread modifies data while another thread is reading it, causing inconsistencies that can be difficult to debug. To manage shared resources safely, synchronization mechanisms such as locks or other concurrency controls need to be implemented, adding complexity to the code.

By directly managing threads, developers may inadvertently create scenarios where race conditions can thrive, especially in complex applications that require precise coordination between threads. This risk underscores the importance of understanding threading and concurrency in order to write robust applications, particularly in environments like Android, where UI responsiveness and data consistency are critical. Proper use of higher-level abstractions, such as Kotlin coroutines, can significantly reduce these pitfalls.