Besides, its not just about efficiency, but about scope and use of resources. In economic boom cycles there is more capital to play around with non-essential ideas. When that access to capital dries up, so does viability of keeping extra resources for things that are not essential.
Again, we are talking about how cutting people during regular operation absolutely would not make the team more efficient, not adding people to a project last minute.
Late projects is just a theme used to convey the core ideas, as it is a common thinking/pitfall, but the reasoning of why late projects because later equally apply to initial software estimates.
The core idea is that software cannot be simple divided into “man months”. That is, saying this software will take 80 manhours, and therefore 10 engineers can do it in 10 days, and a 80 engineers could do it in a day. The reasoning being 1. Software tasks are complex and not easily partitioned, and 2. Software projects require a lot of communication and the more people you have the communication channels needed greatly increase. Essentially what happens is when you have too many people, more time is spent communicating what needs to be done and whose going to do it than doing the actual work.
In any case, efficiency is not really relevant because what happens in layoffs typically, is that entire teams/projects/or initiatives are dismantled. So its not about serving the same projects with less people, but reprioritizing whats essential.
This is absolutely not true.
This is one of the most well known writings on software. https://en.wikipedia.org/wiki/The_Mythical_Man-Month
Besides, its not just about efficiency, but about scope and use of resources. In economic boom cycles there is more capital to play around with non-essential ideas. When that access to capital dries up, so does viability of keeping extra resources for things that are not essential.
Again, we are talking about how cutting people during regular operation absolutely would not make the team more efficient, not adding people to a project last minute.
Late projects is just a theme used to convey the core ideas, as it is a common thinking/pitfall, but the reasoning of why late projects because later equally apply to initial software estimates.
The core idea is that software cannot be simple divided into “man months”. That is, saying this software will take 80 manhours, and therefore 10 engineers can do it in 10 days, and a 80 engineers could do it in a day. The reasoning being 1. Software tasks are complex and not easily partitioned, and 2. Software projects require a lot of communication and the more people you have the communication channels needed greatly increase. Essentially what happens is when you have too many people, more time is spent communicating what needs to be done and whose going to do it than doing the actual work.
In any case, efficiency is not really relevant because what happens in layoffs typically, is that entire teams/projects/or initiatives are dismantled. So its not about serving the same projects with less people, but reprioritizing whats essential.