There are no free meals
Bob: “Hey, what will we use to communicate with X in this project?” Ted: “We’re using library Y, of course! 5k stars at Github. Looks solid!” (5 months later…) Bob: “Ted, we have a problem. We need to update X and library Y does not have support for it.” Ted: “Hmmm… We could just monkey-patch Y and then create our own in-house version. Problem solved!” (and then it begins…) Dear CTO/VP of Engineering / Head of Development, please do not allow your team to do these kind of things. They are bad. They are bad for your software, for software, in general, and they will hurt your company, sooner or later. Why? You may think that this is the quickest way to solve the above stated problem, but let’s talk about what could happen: ...