A functionally organised engineering team seizes up at around a hundred people, because every feature then has to be negotiated against every other team's bandwidth.

Added to korrents 1 Apr 2026 · How quotes work · Something wrong? Tell us

Related korrents

Our reading — they may agree, disagree or merely touch the same thing. Closest first: a shared subject counts for most, then how near the wording is.

• Uber's thousands of microservices were not an architectural preference but a survival decision: under that growth only independent, unblocked teams could build fast enough to stay alive. TPThuan Pham1 Apr 2026similar wording
• Working with coding agents is exhausting rather than deskilling, and that exhaustion — not the technology — is what limits how many projects one engineer can run at once. SWSimon Willison19 Mar 2026similar wording
• A swarm of agents with the right loop and the right metric can already out-produce a team of a hundred engineers. AWAlexandr Wang29 Jul 2026similar wording
• A company must cut half its engineers to pay for the other half's tokens, and that is what the layoffs are actually about. SYSteve Yegge11 Mar 2026similar wording
• The fear that a big lab will simply build your product is overstated, because no organisation can aggressively prosecute a hundred priorities at once. PCPatrick Collison31 Jul 2026similar wording

On the map

Open the map on its own page →