Timeline for Difference between Pattern and Principle
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 18, 2016 at 11:35 | comment | added | Raúl | "Patterns are more high-level things, than principles". I beg to differ ==> A pattern is close to realization (i.e. low level), while a principle is high level rule. | |
| Jun 20, 2012 at 11:38 | history | migrated | from stackoverflow.com (revisions) | ||
| Jun 20, 2012 at 10:19 | comment | added | Jarkko | I can see what you meant by that and understand your thinking on the matter. It is, however, contrary to the common meaning of the concepts "high level" and "low level" in the context of software. (For some reason i can not @-tag you.) | |
| Jun 20, 2012 at 10:14 | comment | added | lazyberezovsky | @Jarkko see my example. When I talked about level, I meant that patterns are based on principles, not vice versa. Brick is not more high-level thing, than building. | |
| Jun 20, 2012 at 10:07 | comment | added | Jarkko | Actually patterns are of a lower level than principles. That is to say, that a pattern is closer to the actual implementation than a principle in this context. In other words, principles are more abstract than patterns with principles meaning general design guidelines and patterns representing solutions suitable for a particular class of problems. | |
| Jun 20, 2012 at 9:57 | history | answered | lazyberezovsky | CC BY-SA 3.0 |