How *Not* to Write Concurrent Code

Invariants, locking, mutexes, critical sections, monitors, barriers, race conditions, non-deterministic, memory coherence, consistency models, etc. "Multithreading is hard", hard to do correctly and easy to do incorrectly. "Correctly" is almost always application-specific and usually caveated with "it depends". It's hard to define specific rules or practices that work in all circumstances. This session takes a different point of view on things and shows you specific ways to do things "wrong" with regard to multi-thread. This session will detail some of the common primitives and techniques use in multi-threading, but used in the wrong ways. Why they are wrong and alternatives will be covered. Topics like Sleep, DoEvents, volatile, lock, interlocked, thread priority, non-shared data, etc. will be covered.