&gt; Senior&#x2F;Lead devs need to carefully curate what a projects foundation is. A strong, well designed foundation means you have something solid to build on. If you don&#x27;t understand what&#x27;s in your deps, haven&#x27;t read their code, see how often it&#x27;s updated and how many people actively use it, and can say you are using 80% or more of the code in it then don&#x27;t use it.<p>Having to deal with my share of poorly supported components in Django&#x2F;DjangoCMS, I can confirm your observation for Python. But betting on the wrong opensource component is often better from betting on the wrong proprietary technology. It comes with the territory.<p>&gt; Writing your own code is often the best route since it fixes your exact use case, no matter the language, libraries or frameworks being used.<p>The problem is not you supporting your own code versus you supporting the code of a random dude from Internet, the problem is when you move on to the next job and some poor guy has to support and fix bugs in your code from 3 years ago. In my experience the average quality of community components and components developed in-house are not that different.<p>Personally I wish project managers starting caring more for life-cycle planing.