The Rule of Three: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
No edit summary
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
=External=
* [https://www.amazon.com/Facts-Fallacies-Software-Engineering-Robert/dp/0321117425 Facts and Fallacies of Software Engineering] by Robert Glass
* [https://blog.codinghorror.com/the-delusion-of-reuse/ The Delusion of Reuse and the Rule of Three] by Jeff Atwood
=Internal=
=Internal=
* [[Software Engineering]]
* [[Software Engineering]]
* [[DRY]]
* [[DRY]]
* [[Designing_Modular_Systems#Modularization_Downsides|Designing Modular Systems]]


=Overview=
=Overview=
The "rule of three" for software reuse suggests the you should turn something into a reusable component when you find three places that you need to use it.

Latest revision as of 02:41, 9 January 2022

External

Internal

Overview

The "rule of three" for software reuse suggests the you should turn something into a reusable component when you find three places that you need to use it.