|
|
|
|
|
|
by iainmerrick
2012 days ago
|
|
|
This is a good question, and I haven’t yet seen anyone reply with (I think) the real answer: it’s not the rule of 3 so much as “not 2”. When you start adding a new feature, and notice it’s very similar to some existing code, the temptation is to reuse and generalize that existing code then and there -- to abstract from two use cases. The rule of 3 just says, no, hold off from generalizing immediately from just two examples. Wait until you hit one more, then generalize. “Once is happenstance, twice is coincidence; three times is enemy action” (Ian Fleming IIRC) |
|
|