I like the piece but the author might want to update it for distributed repositories where 'DRY' might mean you inherit a CVE from some other developer, and it

I like the piece but the author might want to update it for distributed repositories where 'DRY' might mean you inherit a CVE from some other developer, and it also may mean that you've got code in your system that nobody who works for you knows how it works or why it was written the way it was written. Both situations are "sub optimal."