Problems with patterns:
A pattern concists of a problem, forces around the problem, solutions and its consequences. The name was caught by the media, bashed up and left alone. The most important part of a pattern is the coining a name, which makes its representionin our mind easier. We can talk about it with others and make more complex operations with it. Well compexity is reduced by finding patterns inside the mess, right? The value of the pattern depends on the quality of design it produces.
Patterns are tree structure: Replacing the web structure of the real world with linked trees will make the design easier for humans, who are essentialy “tree thinkers” For more info read “A city is not a tree” by Cristopher Alexandar. It says that, humans arrange informationin tree format because it reduces complexity. But the world is really a semi-lattise or a web. We need different view points when solving a problem. But an individual considers only one view point, thats why we do group discussions. In order to reduce redundancy and complexity in a database, we have relational databases which link up different sets of data. Will this method provide an insight into how outliners will be useful to solve problems? How will it help in creating a central model? Will having templates for outliners make our tasks easy, will it help in innovation? How do the views in MVC fit into this? Is a view tree hierarchy from a view point?
Comments Off on Problems with patterns: