The Mythical Man Month Essays on Software Engineering review é eBook or Kindle ePUB

download É eBook or Kindle ePUB ↠ Frederick P. Brooks Jr.

Itial publication of his book Brooks has revisited his original ideas and added new thoughts The Mythical Epuband advice both for readers already familiar with his work and for readers discovering it for the first time The added chapters contain 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. Since what I know about programming probably could be written on the back of a postcard and wouldn't be worth reading there's nothing worthwhile that I can say about the software engineering side of this collection of essays about software engineeringFurther Brooks was writing in the 60s in part based on experience from the 50s which I suppose means I'll be making some claim to wider applicability with regard to project management people management and understanding the nature of tasksI read the 20th anniversary edition which I recall as not cheap and to justify the price is expansively laid out with lots of black and white picture of prehistoric beasts caught in a Tar pit the Tower of Babel werewolves and other such things that leap to mind as metaphors to explain the experience of certain projects there isn't one of a burning Zeppelin but perhaps that will be rectified in a future editionI'll proceed with brief summaries of the essaysThe Tar Pit The Mythical Man Month if a project is late adding additional manpower will only delay it further particularly if the nature of the project reuires communication between team membersThe surgical Team a project team is best organised with fixed and exclusive roles each member focused on one task like a surgical team this approach is scalable if a large project can be sliced up into appropriate chunksAristocracy Democracy System design Be like the Cathedral builders of Rheims accept the creativity of implementing somebody else's vision to achieve greatest over all harmonyThe Second System effectDesigner of their first system will be feeling their way and so cautious and lean their second system tends then to filled with baroue detailing and pet ideaspassing the word I think that was about project documentationWhy did the Tower of Babel Fallcommunication problems also don't vex God unnecessarilyCalling the Shot ten pounds in a five pound sack The documentary hypothesis plan to throw one away or less what it says sharp tools meh computer stuff those things will never catch on the whole and the parts as above and get off my lawnhatching a catastrophe How does a project get to be a year lateOne day at a timep246 the other face no silver bullet good news for Werewolves there are no silver bullets Then the main points are repeated in brief pp230 250 obviating the need for the rest of the bookI had dog eared a couple of pages in the No Silver Bullet chapter the first time I read it but it was another person who read it and I couldn't see or imagine what had caught his attention then I'm dead to myself apparently view spoiler which is probably for the best you know this skull ain't big enough for the two of us and all that hide spoiler

read The Mythical Man Month Essays on Software Engineering

The Mythical Man Month Essays on Software EngineeringManagement 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 Mythical Man Month PDFEPUB #236 this unity Brooks' view of these propositions a generation later a reprint of his classic paper No Silver Bullet and today's thoughts on the assertion There will be no silver bullet within ten yea. I'm really surprised that people still recommend this book It's primarily concerned with very large scale software projects ie an operating system much of the data is anecdotal and many of the assumptions are simply outdated For instance Brooks writes about 1 creating paper manuals with documentation about the system that get updated daily for the engineers 2 strategies for time allocation on centralized computers and 3 about optimizing for compiled code size Those simply aren't problems any outside of niche applicationsAdditionally Brooks' main thesis about man months is most often misuoted and misunderstood He writes that people and months aren't interchangeable and that adding people to late projects will only make them later—because people initially have a negative contribution The details of that aphorism are incredibly important but always forgottenIt would be nice to see a new updated book on this topic that includes actual data and measures concepts from this century But I did find Brooks' articulation of a few other concepts helpful Among themSimplicity and straightforwardness proceed from conceptual integrityBy documenting a design the designer exposes himself to the criticisms of everyone and he must be able to defend everything he writes If the organizational structure is threatening in any way nothing is going to be documented until it is completely defensibleAll repairs tend to destroy the structure to increase the entropy and disorder of the system Less and less effort is spent on fixing original design flaws; and is spent on fixing flaws introduced by earlier fixes As time passes the system becomes less and less well ordered Sooner or later the fixing ceases to gain any ground Each forward step is matched by a backward one Although in principle usable forever the system has worn out as a base for progress

Frederick P. Brooks Jr. ↠ 3 read

The Mythical Man Month Essays on Software Engineering review é eBook or Kindle ePUB õ ➽ [Reading] ➿ The Mythical Man Month Essays on Software Engineering By Frederick P. Brooks Jr. ➲ – Few books on software project management have been as influentialFew books on software project management have Man Month PDF #206 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 System computer family and then for OS its massive software system Now years after the in. As far as I can tell the core tenets of this book aren't really even up for dispute any I don't mean to sound like the grumpy reader mentioned in the epilogue complaining that the book offered nothing I didn't know already know however experienced he might have been I still doubt it but whether from my limited experience in the industry first hand or second hand through the various managers I've had over the years the tenet that developers and time aren't interchangeable resources felt both familiar and self evident So in a certain sense I don't feel like I have any business critiuing this as a book than I do Relativity The Special and General Theory Still another part of my brain is content to separate a critiue of the book ua book from any kind of dispute with the actual arguments and share some petty little snipes that made this less enjoyable of a read than it could have been1 His stubborn refusal to ever acknowledge the reality of female programmers This frustrating trend starts with the title what the hell is a man month Does your project need beards to get grown or code to get written and just never Lets Up Except for a grammatically necessary she when mentioning Frances Spence on the final page I'm not sure that female pronouns show up once in this entire book Sure they didn't have the same legitimacy as a gender neutral singular pronoun then that it does today but this thing was reissued in 1995 a time when they might have been cutting edge but he or she was standard practice even in elementary school grammar It's not just developers either system architects managers everyone on the surgical team; hell even USERS at least the ones with any amount of initiative in testing the limits of the software are all male by default Wait I just remembered women DO come up To paraphrase you can't make nine women pregnant and expect a baby in a monthUgh I'm sure this isn't a new point to make and I'm sure he's responded with grace and candor about how the standard of writing he grew up with used male pronouns as a convenience to refer to EVERYONE and of COURSE he's had the pleasure of working with plenty of competent even visionary women throughout the years and such and such and such If making the original text even a little bit gender inclusive was an innocent oversight on Brooks' part his editor for the reissue gets less of a free pass Women code As a courtesy to them please update your grammar 2 The gratuitous religious overtonesDon't get me wrong I still vividly remember the almost spiritual ecstasy of that first day when I really got recursion and I completely understand how someone might position the beauty of software design within their existing framework of spirituality Christianity Unfortunately a conseuence of building your whole cosmology around a being like the Western monotheistic God is that it necessarily consumes anything and everything else; it then becomes almost impossible to write about the beauty or nobility of some pursuit or principle except to the extent that it supposedly emanates from the nature of this supposed entity A connection between good software design and Christian ideas of holiness pop up again and again and they grate on me not just because they come across as a bit sanctimonious but because oftentimes the Christian lens actually distorts the content Two examples spring to mind the first comes in the chapter Aristocracy Democracy and System Design which argues for conceptual integrity as the supreme virtue of a software system I'll grant that the book predates all of the advances that made true open source systems possible or the achievement of GNULinux to prove it was a viable model but Brooks seems so wrapped up in the analogy of the God like software architect that he never gives the heathen bazaar model fair consideration the cathedral is self evidently superior to anyone who sincerely believes the entire world represents a unified intentional design by a single entity The second is in the chapter Why Did the Tower of Babel Fail and my objection boils down to this the Tower of Babel didn't fail because the builders lacked organization and communication It failed because an omnipotent being intervened to make it impossible to have organization and communication; this happened in turn because the Christian God and especially the Old Testament God is an angry spiteful and sometimes downright petty being and that the organized human enterprise of building this tower represented a challenge to his authority The interpretation Brooks chose to go with confuses proximate and final causes which made it hard for me to buy any of what followed no matter how legitimate the points themselves might have been