Status Updates From Java Concurrency in Practice

Chapter 4 - Solid, practical chapter. The contents are a lot more intuitive to me than chapter 3, though. I didn't learn as much.

To me, the need for safe publication is one of the least intuitive parts of concurrency in Java. I didn't even understand what safe publication was, let alone why I needed it or how to achieve it, before reading this book.

Visibility concerns are a lot less intuitive to me than a need for atomicity. It's hard to remember now, but I'm pretty sure I used to think that if only one thread writes to a variable, and all writes are single step (so the data is never in an inconsistent state, even temporarily), no synchronization is needed. But the variable needs to be volatile if no locking is used. This book has really hammered that home.

Chapter 2 - I love this chapter! It is really concurrency basics that could apply to most languages, but laid out so clearly.

"It is a common mistake to assume that synchronization needs to be used only when writing to shared variables" - can confirm. I definitely know better, but I have still forgotten before.

Haha, you don't have to convince me concurrency is useful and hard. I am sold!