Convention over Configuration
From APIDesign
(Difference between revisions)
| Line 2: | Line 2: | ||
[[Category:APIDesignPatterns]] | [[Category:APIDesignPatterns]] | ||
| + | |||
| + | Anyone knows older use of [[Convention over Configuration]]? | ||
| + | |||
| + | <comments/> | ||
Revision as of 12:02, 20 September 2009
Due to cluelessness being present in almost every user of our API, it is better if they don't need to configure anything. It is good if the code API users create can be analyses and default configuration deduced from it. Modern frameworks (that wish to be cool and in) rely on this concept quite often as wikipedia says. It is however fair to remind us that Java used Convention over Configuration sooner then it was invented: the JavaBean specification relies on it heavily.
Anyone knows older use of Convention over Configuration?
<comments/>
Follow
