The document discusses the benefits and challenges of parallelism and concurrent design. It notes that parallelism allows non-linear and unpredictable participation, which can introduce unexpected changes and make the current state unclear. However, it also acknowledges there are many benefits to parallel and concurrent approaches by giving more freedom and flexibility. In the end, it recommends serializing concepts for clarity but remembers there are also benefits to parallelization.
The document discusses the benefits and challenges of parallelism and concurrent design. It notes that parallelism allows non-linear and unpredictable participation, which can introduce unexpected changes and make the current state unclear. However, it also acknowledges there are many benefits to parallel and concurrent approaches by giving more freedom and flexibility. In the end, it recommends serializing concepts for clarity but remembers there are also benefits to parallelization.
The document discusses the benefits and challenges of parallelism and concurrent design. It notes that parallelism allows non-linear and unpredictable participation, which can introduce unexpected changes and make the current state unclear. However, it also acknowledges there are many benefits to parallel and concurrent approaches by giving more freedom and flexibility. In the end, it recommends serializing concepts for clarity but remembers there are also benefits to parallelization.
there are however a LOTTT of benefits when a concept is parallelized or used
in a concurrent style whereby the user is given the freedom to haphazardly
begin at step5, then freely reverse backwards to complete step3, then randomly move forwards to complete step7, and then randomly backwards again to complete step4, and then sideways to the LEFT again to complete step9, and then sideways to the right to complete step8, and so on and so forth with each step having no prerequisites or placing a restriction on the user / actor / observer to complete ANY OTHER step as a REQUIRED predecessor or prerequisite ! I call this the "building block" design, which means that the pieces (building blocks) that you use to assemble the final product, you have the freedom to place ANY of those pieces at ANY position and arrange them in any direction you wish, in the process of you assembling the final product (could be a house).
parallelism is the same as asynchronous participation where each participant
in the activity can enter the scene at any moment, in an unpredictable fashion and without prior notice, and this new participant can effect a {possibly-unmonitored and unexpected} change in the state of the scene. so with parallelism, if you do Not {have a way to} constantly monitor for these haphazard {and obscure} changes that may occur at ANY moment, the current/known state of the scene {or entity in question} at any point in time can become mysterious parallelism can also take the form of an autonomous choreography, whereby there is certainly some interaction happening around a centerpiece {entity}, but this interaction is Not centrally coordinated, supervised or monitored by any participant as a SINGLE or MASTER controller from this explanation, it is clear that parallelism can become a MONSTER of an arrangement style, due to the difficulties inherent in allowing things to happen in parallel. it follows therefore that if you want your story or proposition to really be crystal clear, avoid parallelism at all costs and stick to a SERIAL arrangement of the concepts in your story. Try as much as possible, to rather serialize the concepts {in your story} into a step1, step2, step3, step4, step5 . . . type of arrangement. in closing however, REMEMBER, like is said . . . there are a LOTTT of benefits when a concept is parallelized or used in a concurrent style, there are a LOTTT of serious benefits when you perform activities in a parallel or concurrent style, or when you arrange your activities as autonomous tasks/steps rather than as tightly-couple dependent tasks/steps !