In Mythical Man Month (2), Brooks compares historical software engineering practices to a tar hole, a mess that effort alone will not fix . Productivity can stop halfway through a project. Time and personnel can be added to try to resolve the problem, but to no avail. Brooks identifies five different misconceptions that lead to this chasm. Programmers tend to be overly optimistic in their predictions, without taking into account possible bugs and obstacles to learning. There is a good chance that problems will arise, especially in larger projects. Another misconception is that progress is proportional to men and months. Having more developers collaborate means more communication is required, which takes time and resources. To optimize progress, the core developer relies on the number of independent tasks; having too many developers hinders progress. To maximize costs and reduce risks, have a smaller team that takes more months; the biggest risk will be that the product is no longer viable in a new market. “Good cooking takes time. » When a chef is pressed for time, he does not cook up something to appease an impa....