Talk:Rule of three (computer programming)

Three times? That's overkill! If the same code is used twice then it should become a procedure. SJ2571 (talk) 20:41, 9 July 2009 (UTC)

As a rule of thumb this is poor. It might have been taken out of context or misrepresented. When the portions of code being replicated are quite large it is very unlikely this rule will do any good (in my opinion).

There are some cases where it makes sense to apply such a rule but there is no compelling reason given to adopt this as a general rule for any case. An example of such a case where this rule might make sense is where two systems have a portion in common that may be changed in the future yet at least one system might not support every reasonably possible configuration of the portion supported by another. Over zealous duplicate removal can lead to a situation where a change must be made but due to an incompatibility the original process of duplicate removal must be reversed which is a waste of time. This may entail exactly the same kinds of technical complications that would be brought about by too much duplication.

This rule limits duplication it does not eliminate it. It clearly links to justification for limiting it but not for tolerating a small amount. If this article is to be balanced and useful it must include such a justification. — Preceding unsigned comment added by 212.85.4.184 (talk) 18:07, 18 August 2011 (UTC)