This is a good advice, but I feel to add a few points of mine: 1. the author says "premature optmization", and it has the right context, however I prefer to us

This is a good advice, but I feel to add a few points of mine: 1. the author says "premature optmization", and it has the right context, however I prefer to use "premature abstraction" or even "speculative generalization". 2. YAGNI and DRY can be counter-principles because at times "you aint gonna need that level of abstraction/genericity". 3. Inadequately abstract and generic code hurts simplicity and readability.