I agree with bad_user's points, but I would like to add my own phrasing in support of his points. Concurrency with "independently executing processes" are not

I agree with bad_user's points, but I would like to add my own phrasing in support of his points. Concurrency with "independently executing processes" are not strictly independent. There must be some communication between the processes, otherwise they cannot coordinate to achieve the same task. A typical mechanism is to have a shared queue between the processes as the only point of communication - use of that queue will involve "shared writes". People build abstractions on top of such mechanisms which hide these shared writes, but they are still there. And that is part of bad_user's point: even though you, yourself, are not actually writing the code for a "shared write", you must call code that eventually performs one.