PDF Í The Mythical Man Month Essays on Software Engineering Â Frederick P. Brooks Jr.
The Mythical Man Month Essays on Software EngineeringInitial 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 The Mythical Man Month starts of strong with a solid mix of good humor great story telling and even better analogies and metaphors Most interesting the claims Frederick Brooks made than 40 years ago remain true today But even so the book has not aged wellChapters 5 8 and 9 15 seem wildly out of date I give some reasoning below but the gist is that the middle is mostly skippable Worse is that the religious overtones get a little out of hand in this section And to make it even obvious how out dated it is the sexism is rampant where Brooks intentionally uses he for every pronoun Granted nearly all programmers were males at the time so it's not like his usage is misleading But reading it in this age it feels like the book intends to be sexistuestionable pronoun usage aside the first four chapters chapter 7 and the final chapters are still really insightful They mostly detail how and why software development costs so much even today and why adding engineers to a project is unlikely to speed productivity linearlyThe key take away is that the biggest problems in software development stem from 1 communication and organization and 2 managing added complexity In some ways I think I always knew this But the chapters articulated it very clearly and convincinglyIt makes me wonder why engineering interviews select so much for problem solving and hardly at all for communication and organization skills or the ability to manage growing complexityI'd highly recommend chapters 1 4 7 and 16 Here's a summary of why I'd skip the restChapter 5 can be summed up with Ernest Hemingway's famous uote The first draft of everything is shit Brooks gives some detailed explanations about why the first draft of every program is shit and how to prepare for that and design around it Chapter 11 mostly re iterates thisChapter 6 describes how cumbersome the OS360 manual became Although insightful because of how laughably out of date it is manuals have mostly been replaced with auto generated websites But back in the days of OS360 when engineers first arrived at work a stack of pages would be waiting at their desk These pages represented the changes made to the system in the previous day and the engineer was supposed to find the pages in the FIVE FOOT TALL manual and replace them with these new pages Brooks chronicles the problems of maintaining such a manual and how switching to a microfiche manual helped in some ways but hindered in othersChapter 10 talks about important documents for a software organization While these might hold relevance in a major enterprise y setting they seemed pretty out of place in a startup environmentChapter 13 explains the properties of a good testing framework basically preaching the importance of unit tests and integration tests This is taken for granted in the modern work place as every company at least knows of the importanceChapter 14 similarly explains the importance of milestones or major goals with clearly discernible and verifiable endpoints Again this is taken for granted in the modern work place Kanban Agile and every other Software Development Life Cycle mostly revolves around thisChapter 15 spells out the importance of documentation But peering into the future Brooks sees this becoming obsolete admitting that newer languages of the time like Ada allowed for code to be almost human readable Nowadays code is human readable enough that most programmers prefer for code to be self documenting It's always up for debate if the code written is in fact self documenting But the importance of documentation is constantly diminishing as languages become ever declarative and systems are better and better designed
Frederick P. Brooks Jr. Â The Mythical Man Month Essays on Software Engineering EBOOK
Few books on software project management have been as influential and timeless as The Mythical Man Month With a blend of software engineering facts and thought provoking opinions Fred Brooks offers insight for anyone managing complex projects These essays draw from his experience as project manager for the IBM System360 computer family and then for OS360 its massive software system Now 20 years after the In this classic book on the software development process Fred Brooks demolishes several persistent myths They never uite go away every new generation just has to learn them over again The first and most dangerous of these myths is the belief that putting people on a project means it'll be completed uickly Brooks includes one of the most brilliant graphs I've ever seen plotting number of women against time reuired to produce a baby Would you believe it the graph is flat at nine months irrespective of how many women are assigned to the project As he points out software development is often remarkably similarIf you're a young software developer and were at all surprised by the above you should get hold of a copy of Brooks without delay A few of his observations may now be a little dated but most of it is still pretty damn relevant
BOOK The Mythical Man Month Essays on Software Engineering
EPUB Ä MOBI The Mythical Man Month Essays on Software Engineering î FREE Ê FREDERICK P. BROOKS JR. · ➽ [Reading] ➿ The Mythical Man Month Essays on Software Engineering By Frederick P. Brooks Jr. ➲ – Dogsalonbristol.co.uk Few booksManagement 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; 3 a reprint of his classic 1986 paper No Silver Bullet; and 4 today's thoughts on the 1986 assertion There will be no silver bullet within ten yea I was underwhelmed with how badly this text has aged The references which made sense 15 years ago no longer hold water and the most referenced project is certainly no longer the way we write software nowadays While the idea remains valid I think people writing about this text are relevant than the text itself holding only historical value at most