When reading the title I figured it would explain something different to what the author does: when doing a organ transplant (except for the liver maybe) the or

When reading the title I figured it would explain something different to what the author does: when doing a organ transplant (except for the liver maybe) the organ is no longer usable to the donor. Translatable to software, your reusable piece of code might not be so reusable as you think, missing lots of abstractions and having lots of specific code for just one specific consumer. Taking a piece of functionality from one part of your software and using it for something else might harm the original use due to broken API's, introduced complexity latency and failures, etc. Even ending up with having 2 split versions of your reusable component for each use case that you now have to maintain seperately.