So, as someone who works at a giant drone-filled corporation, my guess is that the answer to your question is no. My experience, based on the state of our own codebase, is that mediocre programmers tend to write code that's brittle, unmaintainable, untestable, etc... such that you end up with some classic anti-pattern like big ball of mud. The more people you have, the more you exacerbate this problem (see: Brooks' Mythical Man Month). Plus, with more programmers likely you have more churn, thus more who are relatively new to the codebase and liable to make mistakes, etc...
There are probably unique situations where the above doesn't apply. Perhaps something where you can parcel out relatively routine chunks of code that would otherwise be difficult to automate. Say, an ETL system that has different file formats, where each format requires a custom module. Still, even in such a case I could envision a template system or gui tool that a non-programmer could use instead. So I'm hard pressed to come up with a good example.
Perhaps a craftsman/artist metaphor is apt here: could 50 drone painters pool their talents to create a Mona Lisa?
That said, sometimes folks rise to the occasion. Perhaps some drones are only drones because they've been given boring work. I feel like there's a fair amount of stymied talent in the enterprise.