[xiphias2]

The worst thing in having too many people working on the product is increased code size / code change velocity.

Compile time per person and code understanding time per person grows linearly with the number of people (which grows exponentially as revenue grows), which means that the total time people are spending with understanding the code base & total compilation time for the code server grows quadraticly with number of engineers (+ exponentially with revenue).

Total code size should be kept under square root of number of engineers in an organization probably to keep product velocity OK, and engineers should spend significant time minimizing the number of changes in the code base after they have the first proof of concept.