3 ms·
> The caveat here is in the "if your team is competent", Maybe it's from a place of privilege, but I have no interest in working where the team is not competen
by toast0 4y ago
> The caveat here is in the "if your team is competent",
Maybe it's from a place of privilege, but I have no interest in working where the team is not competent.
But, even if your team is incompetent, there's no guarantee of competence of the people who wrote the dependency you use instead of building it yourself. Most of the time, I'd rather deal with local incompetence than remote incompetence.
At the end of the day, if you want your project to work, you're responsible for the whole thing, include the dependencies you outsourced to others.
- lionkor 4y agoThat's a very fair point. > there's no guarantee of competence of the people who wrote the dependency This is, in my opinion, the best reason to build stuff in-house. Thank you!