Structure and Interpretation of Computer Programmers — One person per task
One person per task has the “nobody can help” disadvantage already mentioned. In fact, people are disincentivized from helping, because their task has their name on it and your task has your name on it.
Managers should support 6-8 engineers. Tech Lead Managers (TLMs). Managers supporting less than four engineers tend to function as TLMs, taking on a share of design and implementation work. For some folks this role can uniquely leverage their strengths, but it's a role with limited career opportunities. To progress as a manager, they'll want more time to focus developing their management skills. Alternatively to progress towards staff engineering roles, they'll find it difficult to spend enough time in the technical details. Most folks find being oncall for components they're unfamiliar with to be disproportionately stressful. An important property of teams is that they abstract the complexities of the individuals that compose them. and avoid creating a two-tiered class system of innovators and maintainers.
This normalization of deviance means that people within an organization stop seeing problems as problems, making it impossible to learn from them. Stagnation kills resilience. A change-resistant culture, however, risks burning out those new people, as they find that they are unable to make any meaningful changes. Knowing what decisions were made and why can help prevent “we’ve always done it this way” as a fall-back reason for doing something. If you understand the constraints and trade-offs around why a past decision was made, you’ll be better equipped to understand if they are still relevant in your current context. push authority for decision-making down closest to where the work gets done If different members of an interview panel have very different views of how the organization works, that can be a sign of deeper issues. This often indicates implicit power structures or lack of clarity around process that can be frustrating to deal with and difficult to change.
Of the early Stripe lore I’ve encountered, my favorite is that it managed to accomplish a tremendous amount with a small team because folks moved so rapidly from one project to another project that, leaving an afterimage behind them, it appeared that they were everywhere simultaneously.
The core observations from Fred Brook’s The Mythical Man Month is that assigning more folks to work on a project often slows down delivery. Part of that is the predictability tax.