User Tools

Site Tools


the_relation_between_design_patterns_and_schema_theory

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision Both sides next revision
the_relation_between_design_patterns_and_schema_theory [2013/09/21 10:11]
yann
the_relation_between_design_patterns_and_schema_theory [2013/09/21 10:16]
yann
Line 21: Line 21:
 The paper makes other interesting points, including that "​[e]xperts usually have a better understanding of a given problem in their domain in that they can represent problem based on its second order features rather than its first order feature",​ that "our perception oft [design problem] depends on our previous experience and what we expect about [the design]"​ (which is typically express when an expert says "​Actually,​ the real problem is...",​ and that "​typical [designs] are retrieved by [designers] in term of general information rather than the specific information [but that] for extraordinary situations, [designers] often remember the specific details",​ (which highlights the interest of reading patterns, code). Yet, it recalls that "​schema [are] never fully [whole] because after thousands of hours of practice, [designer] can still improve his or her performance."​ The paper makes other interesting points, including that "​[e]xperts usually have a better understanding of a given problem in their domain in that they can represent problem based on its second order features rather than its first order feature",​ that "our perception oft [design problem] depends on our previous experience and what we expect about [the design]"​ (which is typically express when an expert says "​Actually,​ the real problem is...",​ and that "​typical [designs] are retrieved by [designers] in term of general information rather than the specific information [but that] for extraordinary situations, [designers] often remember the specific details",​ (which highlights the interest of reading patterns, code). Yet, it recalls that "​schema [are] never fully [whole] because after thousands of hours of practice, [designer] can still improve his or her performance."​
  
-Finally, the paper concludes ​+Finally, the paper concludes ​on implications of schema theory on design patterns. It is unfortunate that some of these implications are hard to grasp or not directly backed up by evidence in the paper, for example that "​individually constructed patterns do not differ that much when they are communicated"​ and that "[t]he pattern format therefore seems to be adequate vehicle to capture [experience]"​. Indeed, the examples in the paper are not always relating schema theory to design patterns but stay at a very high, yet interesting,​ level.
the_relation_between_design_patterns_and_schema_theory.txt ยท Last modified: 2019/10/06 20:37 (external edit)