Tips & Tricks, page 1:

Quote: in 2017, I started to feel that the Dark Ages of mutex-based thread sync were over

Another Quote: Another issue which almost universally rears its ugly head when speaking about not-so-trivial uses of CAS is the so-called ABA problem.

[→]

Quote: “Programs are not the self-contained, self-reliant, self-sufficient things they once were.”

Another Quote: “I highly recommend you log every HTTP request you send and every HTTP response you receive.”

[→]

Quote: “We decide which set of types we’re using (fundamental or int*_t), and use it consistently”

Another Quote: “The only thing we’re doing here, is changing the name of the type, NOT its behavior”

[→]

Quote: “with std::reduce() such code, while it compiles at least under MSVC, MAY occasionally provide wrong results”

Another Quote: “if you happen to need something beyond that – take a deep breath and allocate at least several months to understand how does parallelism really work under the hood.”

[→]

Quote: “as long as serial code provides good-enough response times from end-user perspective – DON’T PARALLELIZE”

Another Quote: “out of all the premature optimizations, premature parallelization is the most premature one”

[→]

Abstract: “I made an experiment which demonstrates Big Fat Dangers(tm) of implying that parallelization can be made as simple as just adding a policy parameter to your std:: call.”

Quote: “it is still necessary to understand what we’re doing”

[→]

Quote: “we’re just narrowly avoiding a disaster without understanding how close we were”

Another Quote: “there is a chance that intuitive::lt MIGHT be a good thing to make behaviour of our C++ code to correspond better to our-expectations-when-we’re-reading-it”

[→]