> will require an n log n number of people. (In bad organizations, it's n^2.)
I understand this is signaling that the author understands technical concepts like big-O, but why use technical terms imprecisely when non-technical terms work just fine?
I understand this is signaling that the author understands technical concepts like big-O, but why use technical terms imprecisely when non-technical terms work just fine?
It's beyond the scope of this conversation, but the short is that it seems to become a network effect problem. Every team does not work with every other team, but it does end up in a hub-and-spoke system with matrixes over the system. Oversight (ops, security, PMO) do not scale linearly because the competing priorities make scheduling more difficult.
I've read others who have spoken about it, but I'd have to go back and find it.