Re:Write Everything Twice
by wpietri on Tuesday December 25, 2018 @07:02PM
(#18759723)
This is good advice, but I'm a little disappointed to see it written up as a complete novelty. The principle appeared in Martin Fowler's 1999 book Refactoring as the "rule of three", where he attributes it to programmer Don Roberts. I've heard it a zillion times in discussions about when and how to refactor.
[ Parent
| on HN ]
I have my own rule of three that I also try to apply to use cases for adding functionality in a way that's not overly specific. Never heard of it before.
But now that you mention it, I haven't actually read Refactoring :| The knowledge actually required for programming is tiny compared to what's available; people's exposure is all over the map.