> An early abstraction that would've grouped those coincidentally similar pieces of code would then have to stretch to cover both evolutions. In that case, my

> An early abstraction that would've grouped those coincidentally similar pieces of code would then have to stretch to cover both evolutions. In that case, my takeaway would be that it ain't the abstraction itself that's wrong, but the unwillingness to get rid of it (or decompose it) when it no longer serves its purpose.