Add a slide to compare Brooks and Torvalds laws GH-46

Author: pintergreg

lectures/10_planning.md

@@ -588,6 +588,21 @@ This may be considered as a part of the communication overhead, it is an importa
 <!-- ## what can be done? -->
 <!-- Brooks' law says that it is impossible to measure useful work in man-months. -->
 
+## Brooks' law vs Torvalds' law
+
+> Adding manpower to a late software project makes it later.
+>
+> -- Fred Brooks (1975)
+
+> Given enough eyeballs, all bugs are shallow.
+>
+> -- Linus Torvalds (1999)
+
+::: {.fragment}
+- if you have many users (testers), they will find the bugs
+- if you have many developers, someone will understand and fix the bugs
+
+:::
 
 # references
 

lectures/HOME.md

@@ -142,6 +142,7 @@ MVC-MVP-MVVM
 - [What Scrum Says About Estimates](https://www.scrum.org/resources/blog/what-scrum-says-about-estimates)
 - [How to create a Minimal, Reproducible Example](https://stackoverflow.com/help/minimal-reproducible-example)
 - [Walking Skeletons in Software Architecture](https://medium.com/@jorisvdaalsvoort/walking-skeletons-in-software-architecture-894168276e3f) - by Joris van der Aalsvoort
+- [Brooks’ Law: Adding Manpower to a Late Project Makes It Later](https://effectiviology.com/brooks-law/) - by Itamar Shatz
 
 ## week 7