Good perspective, I agree. One needs to pick the concurrency model and design up front. Document it before writing a single line of code. Then stick to the pla

Good perspective, I agree. One needs to pick the concurrency model and design up front. Document it before writing a single line of code. Then stick to the plan. It takes discipline, but it's not difficult. I mostly write in C with pthreads and as long as one is willing to apply discipline to the task, there's no reason to fear concurrency. If one starts adding a thread here and a mutex there and some shared structures over there without any prior plan then yes, absolutely, that leads to a world of hurt and a deep hole that is very difficult to get out of. So, don't do that.