In 1975, the late Fred Brooks published "The Mythical Man-Month: Essays on Software Engineering," a collection of essays on software development and project management. At some point, a black and white version of the tar pits mural was used on the book cover. The image is a metaphor for the feeling one often has when working on complex software projects––being trapped in a tar pit with no way out.
The book is famous for its assertion that "adding manpower to a late software project makes it later," which is now known as Brooks's Law. Brooks argues that the complexities of software development mean that communication overhead increases as more people are added to a project, leading to diminishing returns.
If there is one book that every software engineer should read, this one is it. Fifty years after its publication, it remains relevant and insightful, offering timeless wisdom on the challenges of software engineering and project management
Many years ago while living in New York City, I gave a course on software engineering at the CUNY Graduate Center's Continuing Education department. Explaining the principles outlined in Brooks' book were a key part of the course's curriculum. I coined the term the Mythical Man-Month Method (FourM) as a shorthand to convey how Brooks' seminal ideas had been encapsulated in agile software development practices.
Over the course of the ensuing years, I made several attempts to create a blog to share my thoughts on software engineering, but was too busy actually managing software projects to have time to write too much. However, I kept the FourM domain name and use it for my personal Github. So I include this study project under the FourM "umbrella".
This is a personal study repository, but feedback and suggestions are welcome. You can find the source code for this site and individual projects linked from their respective documentation pages. You can contact me from my Github profile FourMInfo.
This project is licensed under the https://creativecommons.org/licenses/by-nc-sa/4.0/. Feel free to use these guides and templates for your own non-commercial projects. Individual code examples and implementations may have their own licenses as noted in their respective documentation.