L which is not veryone
this percentage of the professional community is MUCH greater than most managers seem to is percentage of the professional community is MUCH greater than most managers seem to believeIt is how well this book has aged We continue to invent new methodologies and structural how well this book has aged We continue to invent new methodologies and structural in the software and computing industry and we continue to stub our toes and rediscover much of what is in this book I love this book I think it came out before Agile Scrum took off However there are so many wonderful concepts about organizing large technically complex projects So much of what he talks about is just good project planning forget software development I am in the chapter now where they are discussing how it is better to have a project which adheres to the original well planned form for a project rather than sloppily stringing a bunch of updated ideas together with the original base It is a philosophy which can be related to Obsession everyday life not just software development I read this book twenty years or so ago and I have given away several copies of it to others who manage groups of professionalsngaged in scientific research and analyses Although Dr Brooks writes specifically about his Cabaret: A Roman Riddle experiences with software development I feel that a reader couldasily replace references to prog. Nitial publication of his book Brooks has revisited his original ideas and added new thoughts and advice both for readers already familiar with his work and for readers discovering it for the first time The added chapters contain 1 a crisp condensation of all the propositions asserted in the original book including Brooks' central argument in The Mythical Man Month that large programming projects suffer. ,
I am a retired computer programmer 86 years old a career therein dating from a chance occurrence in 1956 and having been laid off from USDefense Dept work finally in 1987 when the Cold War nded I *was actively involved in working with the big computer at a Navy base and involved in choosing * actively involved in working with the big computer at a Navy base and involved in choosing replacement for IBM 7090 so I heard a lot of feedback from aerospace contractors who got the System 360 about which the author is writing After our assessment of available machines we chose not to go on with IBM but got another vendor I have heard about this book intermittently through the years always intending to acuire it When I lately found out about the 1995 dition I acuired it and read it with great interest A very good xposition of the nuts and bolts that xist behind large projects From my All Roads Lead Home experience asmployed by the US government and THEN BY A CONTRACTOR TO IT I CONCUR WITH by a contractor to it I concur with his conclusions and welcome the 1995 additional material in which he clarifies some matters Good reading and good advice Must have There are a million little insights into human nature contained in this book Specifically the nature of the sort of humans who want to do well care about doing well but need the space time and nvironment to do wel. Few books on software project management have been as influential and timeless as The Mythical Man Month With a blend of software ngineering facts and thought provoking opinions Fred Brooks offers insight for anyone managing complex projects These ssays draw from his xperience as provoking opinions Fred Brooks offers insight for anyone managing complex projects These The Mephisto Threat (Paul Tallis essays draw from hisxperience as manager for the IBM System360 computer family and then for OS360 its massive software system Now 20 years after the Ramming or software with the generic project to imagine how Brooks xperiences might apply to their own
work The Mythical Man Month is a very thoughtful treatment on the structuring of work groups andThe Mythical Man Month is a very thoughtful treatment on the structuring of work groups and the importance of communication within and among teams working on projects I first xperienced this text in 1990s computer science classes and did not pay it much attention due to the archaic technology references I recently reread it after pawing through Apollo 11 50th Anniversary and other 1960s technology with new respect for his ffortMany of his ideas that were new knowledge then are norms todaySo many gems just a few Psychological safety is an important aspect of creativity Programmers also hated writing documentation in the 1960s If you are working in an accidental or supporting technology area vs the actual value added portion be prepared for that to go awayHe did change his thinking regarding compartmentalization which is clearly stated in the updated dition One has to get past 1960s details IBM OS360 male references and be a thinking nough person to see the ideas rather than just the words to gain value from this bookSomeone at DuckDuckGo is also a fan it hits on mm m Great book and best wishes to Dr Brooks. Management problems different from small ones due to the division of labor; that the conceptual integrity of the product is therefore critical; and that it is difficult but possible to achieve this unity; 2 Brooks' view of these propositions a generation later; a reprint of his classic 1986 paper No Silver Bullet; and 4 today's thoughts on the 1986 assertion will be no silver bullet within ten yea. .