![\"\"](\"https:\/\/osmeusapontamentos.com\/img\/125px-Mythical_man-month_(book_cover).jpg\")
cap\u00edtulo 9 – ten pounds in a five-pound sack\npag. 100
\n“Fostering a total-system, user-oriented attitude may well be the most important function of the programming manager.”<\/p>\n
cap\u00edtulo 9 – ten pounds in a five-pound sack
\npag. 100
\n“Fostering a total-system, user-oriented attitude may well be the most important function of the programming manager.”<\/p>\n
cap\u00edtulo 10 – the documentary hypothesis
\np\u00e1g. 111
\n“Why have formal documents?
\nFirst, writing the decisions down is essencial. Only when one writes do the gaps appear and the inconsistencies protrude. The act of writinh turns out to require hundreds of mini-decisions, and it is the existence of these that distinguishs clear, exact policies from fuzzy ones.”<\/p>\n
cap\u00edtulo 11 – plan to throw one away
\npag. 117
\n“… both the actual need and user’s perception of that need will change as programs are build, tested and used.”
\npag. 118
\n“Quantization of change is an essential technique. Every product should have numbered versions, and each version must have its own schedule and a freeze date, after which changes go into the next version.”
\n“…the reluctance to document designs is not due merely to laziness or time pressure. Instead it comes from the designer’s reluctance to commit himself to the defense of decisions which he knows to be tentative.”
\npag. 121
\n“Program maintenance involves no cleaning, lubrication, or repair of deterioration. It consists chiefly of changes that repair design defets.”
\npag. 122
\n“… the total number of module increases linearly with release number, but that number of modules affected increases exponentially witn release number. All repairs tend to destroy the structure, to increase the entropy and disorder of the system…”
\npag.123
\n“Systems program building is an entropy-decreasing process, hence inherently metastable. Program maintenance is as entropy-increasing process, and even its most skillful execution only delays the subsidence of the system into unfixable obsolescence.”<\/p>\n
capitulo 13 – the whole and the parts
\npag. 142
\n“… conceptual integrity of the product not only makes it easier to use, it also makes it easier to build and less subject to bugs.”
\npag. 144
\n“Many poor systems come from an attempt to salvage a bad basic design and patch it with all kinds of cosmetic relief”
\npag. 147
\n“The unexpectedly hard part of building a programming system is system teste. (…) one should be convinced of two things: system debugging will take longer than one expects, and its difficulty justifies a thoroughly sysematic and planned approach.”<\/p>\n
Nome: The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition) cap\u00edtulo 9 – ten pounds in a five-pound sack pag. 100 “Fostering a total-system, user-oriented attitude may well be the most important function of the programming manager.” cap\u00edtulo 10 – the documentary hypothesis p\u00e1g. 111 “Why have formal documents? First, writing the decisions down is essencial. Only when one writes do the gaps appear and […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[266,363,538,605],"class_list":["post-528","post","type-post","status-publish","format-standard","hentry","category-ler-ver-ouvir-passear","tag-frederick-p-brooks","tag-ler","tag-programar","tag-software"],"yoast_head":"\n![\"\"](\"https:\/\/osmeusapontamentos.com\/img\/amazon_icon.gif\"){kind=icon}
<\/a>
\nAutor: Frederick P. Brooks ![\"\"](\"https:\/\/osmeusapontamentos.com\/img\/wikipedia_icon.gif\"){kind=icon}
<\/a>
\nEditora: Addison-Wesley Professional<\/a>; 2 edition (August 12, 1995)
\nISBN-13: 978-0201835953<\/p>\n","protected":false},"excerpt":{"rendered":"