I know we didn't build any projects around multithreading, but just like you'll see in real life,
self-created multithreading code is super dangerous.
Even the best developers, the most seasoned ones can get it wrong and they can create all sorts of
bugs.
In reality, whatever you end up doing, whether it's mobile or web development to many frameworks,
rap multithreading around something that's already easy to use.
So the nitty gritty of Java multi-threading is not very important, in my opinion.
As long as you understand the concepts behind Threads, Concurrency Core is executing long running tasks
in the background, not blocking the main thread.
Then whatever framework end up using in the future, I'm sure you'll be just fine.