Posted by Paco Moreno
Yesterday I started working on developing a web based application that can be useful for living system business(Nodal Network Business). It is called the Profit and Return Chart. It is part of a group of applications needed for Nodal Network Business Operations.
I worked about 12 hours and believe me, its not hard to code such an application. What is hard is trying to create a living system software application. Let me try to explain myself.
Just being a web server application is not enough. The application must be related to and arise from an underlying morphic field. It must be embedded in the living system nature of the web, not just use the web as linear communication channel for the user to operate the application. Furthermore, the application should be consistent with the principles of living system science and their application to creating a whole new Genre of Software - Living System Software.
John Clayton Caris and I are collaborating to discover the principles of Living System Software and then apply them to create new applications. We welcome you to join us in this fascinating challenge that is a major part of the work of the Isis Group Network in developing the theory and practice of Living System Life and Work.
John wrote an entry to this blog (Living System Software # 1) that began our work to define what living system software is and how it is created. In my current work I am struggling with how to create my application consistent with Point 8) that John wrote in his blog entry.
John's Point 8) says:
"8) This means that the knowledge and data structure has a standard underlying Morphic structure that can then be customized - This means that all knowledge and data inputs go into the server base in a standard way and THEN customized by collaboration based on the standard While keeping the original structure as the start of the input channel - Space is cheap and database mapping to the customized structure is not difficult"
That's an incredibly hard to do. Why, if the user needs to create a new model in his work, like an experiment, the application must have the capability to try to do it even if it leads to an apparently absurd equation. It needs to be done, because that is how living systems work. They can deal with application uncertainty that is not allowed in normal linear system software. They must be able to somehow work through a million errors without code error. They involve a new type of practice - An experimental experience that that CAN TRY many unconventional alternatives and somehow arrive at an acceptable solution.
I think there are a lot of roads that can lead to creating living system software. Possibly some useful experience can be Miguel de Icaza with GNOME or MONO, but thats just the beginning of a very long road.
The first goal for me in learning how to create Living System Software now is to create an application's access to the underlying morphic field (Previously called the database) and become a dynamic transformational part of it.
" It's so easy create linear software, that almost all the people believe its a very difficult task".
" Living system software applications have to be based on the link between the user and his own solution".
I hope I am not boring with my ideas. www.fmoreno.com.mx
Comments