Two doctors can do the same job one doctor can.No but they both can deliver a baby in 2 hours, bringing the total to 2 babies in 2 hours, or a rate of 1 baby/hour.
Two doctors can do the same job one doctor can.No but they both can deliver a baby in 2 hours, bringing the total to 2 babies in 2 hours, or a rate of 1 baby/hour.
Yes, and they can deliver two babies in 2 hours.Two doctors can do the same job one doctor can.
And 4 doctors can deliver one baby in the same time as 4 doctors.Yes, and they can deliver two babies in 2 hours.
You're trying to salvage a failed analogy.And 4 doctors can deliver one baby in the same time as 4 doctors.
No you’re trying to find loopholes in a great analogy. The point is throwing money and resources at a business problem that relies on dependencies doesn’t always scale up because there is a bottleneck somewhere.You're trying to salvage a failed analogy.
Two teams can work concurrently, you sem to think they only can have one team working at a timeNo you’re trying to find loopholes in a great analogy. The point is throwing money and resources at a business problem that relies on dependencies doesn’t always scale up because there is a bottleneck somewhere.
You seem to think that two teams can work on the same thing at the same time.Two teams can work concurrently, you sem to think they only can have one team working at a time
I never said "on the same thing," I'm saying that two teams can work on two thing without having to move a team across projectsYou seem to think that two teams can work on the same thing at the same time.
The law of diminishing returns applies to scaling up.
not even app icon design change?
or ability to change fonts??
Come on Apple.....
That’s the point about the analogy. There is a limit to how resources scale. I dont know the limit and you don’t know the limit.I never said "on the same thing," I'm saying that two teams can work on two thing without having to move a team across projects
Edit: and it wasn't implied either
Your analogy is the opposite of what I'm saying. You're arguing that throwing more people at a problem is not a solution. I'm saying Apple should hire an AR/VR team instead of moving people from the iOS team. You say resources scale vertically (ie. more people), I say they scale horizontally (more teams working parallelly).That’s the point about the analogy. There is a limit to how resources scale. I dont know the limit and you don’t know the limit.
But people seem to believe throwing money and resources are the holy grail of fixing things.
More or less. Never discuss in absolutes.Your analogy is the opposite of what I'm saying. You're arguing that throwing more people at a problem is not a solution.
There may (there is a good reason to apple) be a valid reason for the way the teams are structured that you (and I) aren’t privy to.I'm saying Apple should hire an AR/VR team instead of moving people from the iOS team.
Depending. We don’t know enough about apples teams to make that determination. We of course could have our opinions of them.You say resources scale vertically (ie. more people), I say they scale horizontally (more teams working parallelly).