weddingedit Hier klicken muttertagvatertag Cloud Drive Photos Kamera16 Learn More hama Hier klicken Fire Shop Kindle Sparpaket Autorip GC FS16
Profil für grappone@acsu.buffalo.edu > Rezensionen

Persönliches Profil

Beiträge von grappone@acsu....
Top-Rezensenten Rang: 5.643.813
Hilfreiche Bewertungen: 7

Richtlinien: Erfahren Sie mehr über die Regeln für "Meine Seite@Amazon.de".

Rezensionen verfasst von
grappone@acsu.buffalo.edu (Buffalo, New York)

Anzeigen:  
Seite: 1
pixel
The Deadline: A Novel About Project Management
The Deadline: A Novel About Project Management
von Tom DeMarco
  Taschenbuch

1 von 1 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen Very Entertaining, and Educational, 2. Mai 1998
"The Deadline: A Novel about Project Management", is a delightful book especially when compared to the dry, heavy feel of a text. I think that DeMarco uses a technique that more teachers and professors should use, as opposed to a straight lecture style.
He lightly touches on most of the key aspects of project management. The story makes it easy to read without stopping to say, "Hey, I deal with this all day at work, why would I want to read about it."
Another interesting and useful feature of the book, is the journal kept by the main character. DeMarco cleverly sums up each chapter, and hence each lesson, by having the main character write entries in a journal. These lessons are generally found at the end of each chapter making them easy to find and reread at one's leisure, or as needed.


The Mythical Man-Month. Essays on Software Engineering
The Mythical Man-Month. Essays on Software Engineering
von Frederick P. Brooks
  Taschenbuch
Preis: EUR 31,95

6 von 7 Kunden fanden die folgende Rezension hilfreich
4.0 von 5 Sternen An eye opening look into the world of software engineering., 20. März 1998
In 1975, Frederick P. Brooks, Jr. wrote a ground breaking insightful book about computer science. He accurately captured someof its more esoteric aspects and relayed them in a colorful narrative. I especially liked his use of the illustrations and quotations as the opening of each chapter. Each was thoughtfully chosen and served to set the tone for the following text.
Also entertaining is Brooks' use of the analogy. In the section using the tar pit to describe the struggle faced during large system programming, one comes away saying, "Been there, seen that!" This technique draws you in and makes you want to read on.
Readers of this book will find themselves looking at computer science differently. No longer will it be just a science. The philosophical and artistic values will become clear. Brooks' holistic approach may very well sway some readers toward a more pensive view of computer science. At the very least, the reader should come away with a deeper appreciation for software engineering.
My only negative commentary would be with the added chapters. While the insight gained over twenty years is useful, it comes off as a little defensive. It's almost as if the passion which so beautifully captured the message in the 1975 version, was spent on defending twenty year old statements. I suspect that the author might argue that he was trying to be systemic and clear. In my opinion this came off as overkill. To borrow an old argument, maybe Dr. Brooks fell victim to the "Second-System Effect" of which he so vividly warns us.


Seite: 1