Difference between revisions of "Once and only once"
Jump to navigation
Jump to search
(the practice of defining and describing something in a central place, and then referring to this in other places. It's especially helpful for things that are rapidly changing or complex) |
m (category edit) |
||
| Line 1: | Line 1: | ||
'''Once and only once''' is the practice of defining and describing something in a central place, and then referring to this in other places. It's especially helpful for things that are rapidly changing or complex. | '''Once and only once''' is the practice of defining and describing something in a central place, and then referring to this in other places. It's especially helpful for things that are rapidly changing or complex. | ||
It is a rule of thumb in [[agile software development]]. A function should be defined in only one place, because it is easier to maintain that way. Even a few lines of code or one complex formula is better wrapped into a method or subroutine. | It is a rule of thumb in [[agile software development]]. A function should be defined in only one place, because it is easier to maintain that way. Even a few lines of code or one complex formula is better wrapped into a method or subroutine. | ||
| − | [[Category:Software]] | + | [[Category:Software Engineering]] |
Latest revision as of 22:29, December 1, 2016
Once and only once is the practice of defining and describing something in a central place, and then referring to this in other places. It's especially helpful for things that are rapidly changing or complex. It is a rule of thumb in agile software development. A function should be defined in only one place, because it is easier to maintain that way. Even a few lines of code or one complex formula is better wrapped into a method or subroutine.