1
00:00:00,240 --> 00:00:04,500
I know we didn't build any projects around multithreading, but just like you'll see in real life,

2
00:00:04,500 --> 00:00:07,650
self-created multithreading code is super dangerous.

3
00:00:08,070 --> 00:00:13,560
Even the best developers, the most seasoned ones can get it wrong and they can create all sorts of

4
00:00:13,560 --> 00:00:14,100
bugs.

5
00:00:14,460 --> 00:00:18,630
In reality, whatever you end up doing, whether it's mobile or web development to many frameworks,

6
00:00:18,630 --> 00:00:21,690
rap multithreading around something that's already easy to use.

7
00:00:21,990 --> 00:00:26,670
So the nitty gritty of Java multi-threading is not very important, in my opinion.

8
00:00:26,760 --> 00:00:33,510
As long as you understand the concepts behind Threads, Concurrency Core is executing long running tasks

9
00:00:33,510 --> 00:00:35,970
in the background, not blocking the main thread.

10
00:00:36,270 --> 00:00:40,890
Then whatever framework end up using in the future, I'm sure you'll be just fine.