Convention over Configuration
From APIDesign
(Difference between revisions)
| Line 1: | Line 1: | ||
| - | 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 | + | 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 analysed automatically and default configuration deduced from it. Modern frameworks (that wish to be [[Good Technology|cool and in]]) rely on this concept quite often as [[wikipedia::Convention_over_configuration|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. |
[[Category:APIDesignPatterns]] | [[Category:APIDesignPatterns]] | ||
Revision as of 12:03, 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 analysed automatically 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
