The Pragmatic Programmer

by Andy Hunt

If it isn't easy, people won't do it. And if you fail to reuse, you risk duplicating knowledge.

By planning for concurrency, and decoupling operations in time, you have all these options—including the stand-alone option, where you can choose not to be concurrent. Going the other way (trying to add concurrency to a nonconcurrent application) is much harder.

Keep the question option about being concurrent or not as much as possible.

Developers who don't actively think about their code are programming by coincidence—the code might work, but there's no particular reason why.

I faced with this cases so many times. It works by nobody knows why it just was tested under small set of conditions and nobody reads documentation