4 ms·
You say it like it is essential that we scale to lots of programmers up front. The problem is that there is an organizational barrier. It is easy to have team
by btilly 14y ago
You say it like it is essential that we scale to lots of programmers up front.
The problem is that there is an organizational barrier. It is easy to have teams of under 8 programmers. It is doable to scale teams of 20+ programmers. But if you're between those numbers, small team dynamics fall apart horribly, and large team organization leaves you with less productivity than the small team.
For a small company, the cost jump from 8 to 20 programmers is pretty significant. Therefore it is worth considering the strategy of getting the most out of your existing programmers and not trying to cross that chasm. If you succeed, you eventually will have to face the scaling problem. But success tends to take care of itself.
- ww520 14y agoI think GP meant the number of people touching the software over its lifetime, not necessary at the same time in one location like in a company. e.g. Eclipse must have hundreds if not thousands of contributors, loosely networked and hardly seen each other, contributing over a long period of time. Yet they are able to understand each other's code and build on top of each other. The readability of a language is a must to foster this kind of cooperation. Java is a very readable language and the knowledge in the code can be easier shared among developers.