If you're in trouble and cannot find an answer to a question which goes beyond Stack Overflow...
If you have a not-so-usual solution for your problems but need to justify it to your boss...
If you like to think on your own rather than blindly follow "common wisdom" and "profound truth"...
...then 'No Bugs' Hare on Soft.ware might be the right place for you.
Your mileage may vary. Batteries not included

Assorted Rants Tagged ‘Multithreading’, page 2:

Client-Side. Client Architecture Diagram, Threads, and Game Loop

Quote: “To have a good concurrency model, it is not strictly necessary to program in Erlang”
Another Quote: “Most of developers agree that FSM-based programming is beneficial in the medium- to long-run.”

Multi-threading at Business-logic Level is Considered Harmful

Quote: “However, the window for triviality is very narrow: for example, even going into two interrelated mutexes instead of one, can easily make multi-threading non-trivial”
Another Quote: “Technically you are able to jump to any point of your program, but the variables you see may (and if you have a multi-threaded bug – will) differ every time you jump there.”