- Taschenbuch: 484 Seiten
- Verlag: Real Media Llc (27. November 2006)
- Sprache: Englisch
- ISBN-10: 0977213315
- ISBN-13: 978-0977213313
- Größe und/oder Gewicht: 19,1 x 2,5 x 23,5 cm
- Durchschnittliche Kundenbewertung: Schreiben Sie die erste Bewertung
Nr. 555.307 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)
- Nr. 305 in Fremdsprachige Bücher > Computer & Internet > Informatik > Softwareentwicklung > Informationssysteme
- Nr. 525 in Fremdsprachige Bücher > Freizeit, Haus & Garten > Handwerk & Hobbies > Dekorieren
- Nr. 2521 in Fremdsprachige Bücher > Computer & Internet > Programmieren > Software-Design & Entwicklung > Softwareentwicklung
Andere Verkäufer auf Amazon
+ EUR 3,00 Versandkosten
+ EUR 3,00 Versandkosten
+ kostenlose Lieferung
Software Creativity 2.0 (Englisch) Taschenbuch – 20. Oktober 2006
|Neu ab||Gebraucht ab|
Es wird kein Kindle Gerät benötigt. Laden Sie eine der kostenlosen Kindle Apps herunter und beginnen Sie, Kindle-Bücher auf Ihrem Smartphone, Tablet und Computer zu lesen.
Geben Sie Ihre Mobiltelefonnummer ein, um die kostenfreie App zu beziehen.
Wenn Sie dieses Produkt verkaufen, möchten Sie über Seller Support Updates vorschlagen?
"This book is written from a powerfully felt, personal perspective: that software construction is primarily a problem-solving activity; that all problem-solving requires creativity; that software problem-solving is deeply complex, perhaps more deeply complex than any other activity; and that, therefore, software problem-solving requires the ultimate in creativity." --Robert L. Glass, from the Preface In Software Creativity 2.0, acclaimed author Robert L. Glass explores a critical, yet strangely neglected, question: What is the role of creativity in software engineering and computer programming? With his trademark easy-to-read style and practical approach, backed by research and personal experience, Glass takes on a wide range of related angles and implications. To name only a few: * Are discipline and formality at odds with flexibility and agility? * When are control-driven vs. experimentation-driven approaches most effective? * Can we "make creativity happen" in a software organization? * Which is more important, process or product? * How do theory and practice interact in the software field? Can practitioners and academe complement each other more effectively? * Is there a missing link between creativity and software design? * What is the balance of "intellectual" and "clerical" tasks in software work? * Can we still find a place for plain old fun? Revised, updated, and expanded, Software Creativity 2.0 also features a new Foreword by Tom DeMarco, author of Peopleware, and a new Preface by author Robert L. Glass.
|5 Sterne (0%)|
|4 Sterne (0%)|
|3 Sterne (0%)|
|2 Sterne (0%)|
|1 Stern (0%)|
Die hilfreichsten Kundenrezensionen auf Amazon.com
I think moreover that this should be compulsory reading for those thinking that software development is "easy". I definitely enjoy reading this book!
You may not walk away with any new ideas, but you'll definitely have a better understanding of what's running through people's minds (and that applies for coders, architects and even managers). The topics covered on business vs. academia are priceless in terms of examining the current state of affairs in the tech world.
Pick it up and give it a shot.
If you're writing any papers/essays on topics related to tech, this would also provide a great reference and has many entertaining and potent quotes.
This book is divided into four parts. The first part (and I feel the most important of the book) is the exploration of software creativity. Here he takes on nine dichotomous subjects (discipline vs. flexibility, formal methods vs. heuristics, optimizing vs. satisficing, quantitative vs. qualitative, process vs. product, intellectual vs. clerical, theory vs. practice and industry vs. academe, fun vs. serious) and explores the advocates on both sides and tries to find definitive answers (or at least raise more questions).
What I found fascinating about several of these chapters like quantitative vs. qualitative and industry vs. academe is that they can apply to many different industries and not just software. How many times has quantitative reasoning been used in business only to fail miserably in the hands of MBAs? How can academe differ so much from practice (like getting your Juris Doctorate compared to really practicing law)? These chapters are a plethora of interesting ideas that many of these chapters can be discussed at length (imagine the length of the review if we tried) and one fault (that has already been mentioned by several reviewers) is that some of the topics need more discussion.
The second part deals with making creativity happen. I feel this is such a difficult thing to do in large organizations since it involves a paradigm shift in thinking, but it is a must for small companies. The third part deals with creativity in other fields and the fourth is the conclusion. And to give away the ending his thoughts can be summed up as "...is that our one-size-fits-all approach is wrong. No, it is worse than that. It is WRONG!" The one question that remains is how do you change a practitioner's mind that already has all the answers?
I never read the original book; I did not get into Glass's writing until I received as a gift Glass's Facts and Fallacies of Software Engineering and became enthralled with his pragmatic point of view. That laconic work got me interested in his writings and when d.* brought out this book I bought it immediately. Software Creativity is not as well known as Frederick Brook Jr's masterpiece "Mythical Man Month" or Edward Yourdon's "Death March" (and many others) but it is such a great read that anyone involved in software can benefit from this book. I am biased though. After years of "software development" I have found it to be a very challenging and rewarding endeavor that does benefit from structured creativity. Apparently Robert Glass feels this way too.
To some, a good book will actually answer some of their questions, like the how to books or the academic ones, if you agree then Software Creativity 2.0 is not a good book, and you are the typical "engineer" I was talking about.
A great book will answer your questions with more questions, widening your perspective leaving the ultimate answer for you. The subjects turned in the book are very controversial, and no one, except fools, can claim to hold the correct answer for all contexts and situations. Most of the time the answer for these questions is context dependant, that is where Dr. Glass shines at his best, explaining the contexts of each possible answer for each question and the possible trade-offs, for many this is not a satisying answer, for me it's a good enough answer, and as good as it gets!
Golden rules don't exist in real life, they only exist in the minds of their holders. The book is based on the idea that if you want adopt a rule learn more about the exceptions of that rule than the rule itself, the "No silver Bullet" notion. Glass intentinally doesn't give answers, and he never actually meant to give answers in this book, read the last essay of the book when he intentially picks a "yes" answer for a multiple choice question. He only wanted to stir a conversation, a mental conversation between you and the book, you and yourself, you and and other programmers, even you and other non IT people, and hell yeah it worked for me, I have been thinking so hard since I started reading this book, and harder after I finished it.
All in all One of the best books I ever read.
IF you are the typical binary Engineer this book is not for you, you are better off reading academic or SEI articles which claim to hold the truth of it all.
It is sad that the body of engineering shifted from creative heurisitc context driven world to a world looking for silver bullers and golden rules. The reviewers comments, selling figures, and rating of this book prove my point. No wonder we why soceity looks down at us, and found the name "book smart" for us.
That being said, the answer for the question in the first paragraph is a BIG "YES".