![]()
|
|||
When
Life Is Far From Certain, Lead With Clockware And Swarmware In Tandem. Balance data and intuition, planning and acting, safety and risk, giving due honor to each.
|
|||
|
In an informed approach to complexity, it is not a question of saying that one is good and the other is bad. The issue is about finding an appropriate mix for a given situation. Where the world is certain and there is a high level of agreement among agents (for example, the need for consistent variable names and programming language syntax in a large software system, or the activities in the operating room during a routine surgery) clockware is appropriate. In a clockware situation, agents give up some of their freedom and mental models to accomplish something they have collectively agreed upon. The CAS displays less emergent, creative behavior, and begins to act more like a machine. There is nothing wrong with this. However, where the world is far from certainty and agreement (near the edge of chaos) swarmware is needed with its adaptability, openness to new learning and flexibility. Swarmware is also needed in situations for which the old clockware processes are no longer adequate for accomplishing the purpose, in situations for which the purpose has changed or in situations in which creativity is desirable for its own sake.
|
||
Next | Previous | Return to Contents List
All Components of Edgeware Principles Copyright © 2001, Curt |