While the examples may be quite facetious, they often are for demonstrative purposes...
I myself have been burnt by Over-DRYed code - Over-DRYed code tends to lead to God Functions, where 1 change has many unintended consequences. Unintended side effects should be considered a worse scenario over "tedious chore".
In any case, (at least in a API context) a robust test suite focused on end user requirements SHOULD make the mythical "code quality" metric irrelevant.
I myself have been burnt by Over-DRYed code - Over-DRYed code tends to lead to God Functions, where 1 change has many unintended consequences. Unintended side effects should be considered a worse scenario over "tedious chore".
In any case, (at least in a API context) a robust test suite focused on end user requirements SHOULD make the mythical "code quality" metric irrelevant.