- Taschenbuch: 256 Seiten
- Verlag: Microsoft Press Corp. (Mai 1993)
- Sprache: Englisch
- ISBN-10: 1556155514
- ISBN-13: 978-1556155512
- Größe und/oder Gewicht: 23,1 x 18,5 x 2,3 cm
- Durchschnittliche Kundenbewertung: 3.8 von 5 Sternen Alle Rezensionen anzeigen (22 Kundenrezensionen)
- Amazon Bestseller-Rang: Nr. 19.957 in Englische Bücher (Siehe Top 100 in Englische Bücher)
|
||||||||||||||||||||
|
||||||||||||||||||||
|
||||||||||||||||||||
Produktinformation |
Mehr über den Autor
Entdecken Sie Bücher, lesen Sie über Autoren und mehr
› Besuchen Sie die Seite von Steve Maguire auf Amazon
› Besuchen Sie die Seite von Steve Maguire auf Amazon
Produktbeschreibungen
Amazon.co.uk
Writing Solid Code is one of the best books for developing a proactive attitude towards electronic entomology. Any programmer worth their silicon knows that it is wiser to invest time preventing bugs from hatching than to try to exterminate them afterwards. Follow Maguire's advice, and your testers, supervisors and customers will love you. --Jake Bond
Amazon.com
Any programmer worth their silicon knows that it is wiser to invest time preventing bugs from hatching than to try to exterminate them afterwards. And this is one of the best books for developing a proactive attitude towards electronic entomology. Follow Maguire's advice, and your testers, supervisors and customers will love you. Recommended.
Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?
Vorgeschlagene Tags zu ähnlichen Produkten(Was ist das?)Setzen Sie den ersten relevanten Tag hinzu (ein Schlüsselwort, das mit diesem Produkt in engem Zusammenhang steht).
|
Eine digitale Version dieses Buchs im Kindle-Shop verkaufen
Wenn Sie ein Verleger oder Autor sind und die digitalen Rechte an einem Buch haben, können Sie die digitale Version des Buchs in unserem Kindle-Shop verkaufen.
Weitere Informationen
Kundenrezensionen
Die hilfreichsten Kundenrezensionen
45 von 50 Kunden fanden die folgende Rezension hilfreich
Format:Taschenbuch
I've never written a review here before, but I feel I should warn people against this book. I bought it myself, because of the positive reviews here. This book will NOT teach you to write solid code, at least not the way I see it. For one thing, it's dated, the examples are written in C, not C++ or some other object-oriented language. That wouldn't matter if it was good advice as sound design can be language-independent. However, in my opinion, it isn't. To start with naming, he uses Hungarian notation (which is a way of putting the type of the variable in the variable name (which doesn't give much meaning in C++, with user-defined types)), like "pchFrom", which means "pointer to char," which gives cryptic variable names, reminiscent of much C code. If you get past that, he offers among other things, the following suggestions. The first ones are about the compiler. He suggests that the compiler should be able to catch the following "mistake":
while(size-- > 0); // ";" should not be here, in this case.
*pchTo++=*pchFrom++;
I don't want an infantilizing compiler telling me I shouldn't have an empty statement following a "while," thank you very much.
Other advice is (with my comments after the quotes):
"Maintain both ship and debug versions of your program." - Don't. Don't duplicate code. He actually means having separate code for both versions. That means having to maintain both, and even if you fixed it in the debug version, it's not in the ship version.
He advocates using comments to explain unclear things. I prefer to have code self-documenting. That way, it's always up to date, too. If the code is unclear, rewrite it.
But the really bad advice, the one that compelled me to write this, is in the last chapter (before the Epilogue), in the section entitled "Are you a code meddeler?", and the advice is "Don't clean up code unless the cleanup is critical to the product's success." My advice is "Don't even think about it." If you don't clean up messy code, you almost guaranteed have a bug waiting to happen there. Nuff said. Not to mention the problem of maintaining such code. His intent is, don't mess with code you don't understand. But again, if it's not understandable, make it understandable.
This _would_ explain some of Microsoft's products.
There are some good advice there, but it's buried in the bad ones, making it dangerous.
I would return this book, if I could.
I have many programming books. If you want to write good code, I rcommend "Extreme Programming Explained" by Beck, "Refactoring" by Fowler, and "Design Patterns" by Gamma et. al. Highly recommended. "Effective C++" and "More Effective C++" are also good.
6 von 7 Kunden fanden die folgende Rezension hilfreich
Format:Taschenbuch
I'm posting this mostly to counteract the buffoons who obviously gave this book a poor rating only because it was published by Microsoft Press. That's like criticizing Core Java 2 because you don't like Sun.
MS Press actually has an enviable stable of writers, and publishes many fine books. Ever heard of Steve McConnell? Jeff Prosise? Charles Petzold?
Anyway, this book is a very good source of advice on preventing C bugs on any platform. At one company where I worked, the VP of Engineering used to loan it to many programmers fresh out of college. Like Practice of Programming, it helps you get from what you learn in school to what will help you write production code in the real world.
I don't give it 5 stars because it's just not really a classic. You should give it a read if you program C or C++, though.
2 von 2 Kunden fanden die folgende Rezension hilfreich
Format:Taschenbuch
This book contains practical advice on how to write bug-free code. It covers a large number of guidelines which are generally applicable to all software development projects.
My only caution is that these techniques, when applied by novice programmers, is no doubt the source of much of Microsoft's code bloat. Also, encouraging the programmer to rely heavily on the source-level debugger can prevent developers from getting a real sense of the program's performance on user-level hardware.
Otherwise, a very good book and very useful advice, much of which I've been applying in my own projects.
Möchten Sie weitere Rezensionen zu diesem Artikel anzeigen?
Waren diese Rezensionen hilfreich?
Wir wollen von Ihnen hören.
Die neuesten Kundenrezensionen
Just brilliant
That book is brilliant. Read it, keep an open mind to understand the _principles_ behind solid coding which to author tries to communicate, such as: use all toolchain support you... Lesen Sie weiter...
Veröffentlicht am 23. Juli 2008 von xurg
Just because its printed by the Microsoft press...
Mr. Maguire is an experienced programmer, and this shows in his book. You'll find a lot of his advice useful. Lesen Sie weiter...
Veröffentlicht am 2. Juli 2000 von Vishal G Soni
Who are you kidding?
Is Microsoft really the one to write a book on how to write solid code? Is this some kind of perverse oxymoron?
Veröffentlicht am 24. Juni 2000 von "i104800"
Excellent Content
The presentation of the content - as noted by other reviews - may not be 5 star, but the content definitely makes up for any failings of the book. Lesen Sie weiter...
Veröffentlicht am 15. Juni 2000 von "bbcben"
Exellent book for the experienced developer
As a software developer with 18 years of experience, I didn't expect to get much out of this book at all. Silly me. It changed the way I write code. Lesen Sie weiter...
Veröffentlicht am 2. Mai 2000 von Miguel A. Munoz
Microsoft writes bug-free code?
Well sorry to say it folks but this is just another way to get our users; money.
Am 6. Oktober 1999 veröffentlicht
I really want it!
I read the second book of Magurie. I like it
Am 23. September 1999 veröffentlicht
Should be required reading!
This book should be required reading for every college graduate. It teaches real world programming techniques which should be in every C/C++ programmers bag of techniques. Lesen Sie weiter...
Am 18. März 1999 veröffentlicht
Great book on how good software is developed
This book is not a programmer's desk reference. Those looking for a how-to tome should look elsewhere. Lesen Sie weiter...
Veröffentlicht am 7. Januar 1999 von cbulgin@ndcgroup.com
no no no no no no no no!!!
Just think about the title!!! Microsoft - Bug free.... I don't think so!?!?!
Am 6. Dezember 1998 veröffentlicht
Kunden diskutieren
|
Das Forum zu diesem Produkt
Fragen stellen, Meinungen austauschen, Einblicke gewinnen Aktive Diskussionen in ähnlichen Foren
Kundendiskussionen durchsuchen
|
Ähnliche Foren
|
||||||||||||||||||||||||||||||||||
Lieblingslisten
|
|
Ähnliche Artikel finden
Anhand des Sachgebietes nach ähnlichen Produkten suchen:
Ihr Kommentar
Möchten Sie die Produktinformationen aktualisieren oder Feedback zu den Produktabbildungen geben?
