|
||||||||||||||||||||
|
||||||||||||||||||||
|
||||||||||||||||||||
 Gutschein erhalten
Tauschen Sie jetzt 97 Things Every Programmer Should Know gegen einen Amazon-Gutschein in Höhe von EUR 8,40 ein - einlösbar für Tausende von Artikeln bei Amazon.de. Entdecken Sie mehr eintauschbare Bücher im Bücher Trade-In Shop. Bitte beachten Sie die Teilnahmebedingungen.
 Jetzt für Amazon Student anmelden und um 20% erhöhten Eintauschwert sichern. |
Wird oft zusammen gekauft
Produktinformation
|
Produktbeschreibungen
Kurzbeschreibung
Tap into the wisdom of experts to learn what every programmer should know, no matter what language you use. With the 97 short and extremely useful tips for programmers in this book, you'll expand your skills by adopting new approaches to old problems, learning appropriate best practices, and honing your craft through sound advice. With contributions from some of the most experienced and respected practitioners in the industry--including Michael Feathers, Pete Goodliffe, Diomidis Spinellis, Cay Horstmann, Verity Stob, and many more--this book contains practical knowledge and principles that you can apply to all kinds of projects. A few of the 97 things you should know: * "Code in the Language of the Domain" by Dan North * "Write Tests for People" by Gerard Meszaros * "Convenience Is Not an -ility" by Gregor Hohpe * "Know Your IDE" by Heinz Kabutz * "A Message to the Future" by Linda Rising * "The Boy Scout Rule" by Robert C. Martin (Uncle Bob) * "Beware the Share" by Udi Dahan
Über den Autor
Kevlin Henney is an independent consultant and trainer. His work focuses on patterns and architecture, programming techniques and languages, and development process and practice. He has been a columnist for various magazines and online publications, including The Register, Better Software, Java Report, CUJ, and C++ Report. Kevlin is co-author of two volumes in the Pattern-Oriented Software Architecture series: A Pattern Language for Distributed Computing and On Patterns and Pattern Languages. He also contributed to '97 Things Every Software Architect Should Know'.
Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?
In diesem Buch
(Mehr dazu)
Ausgewählte Seiten ansehen
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis | Rückseite
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis | Rückseite
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
4 von 4 Kunden fanden die folgende Rezension hilfreich
Format:Taschenbuch
Ein großartiges, sehr kurzweiliges Buch, das sehr viele interessante Aspekte beleuchtet.
Enthält 97 2-seitige Beiträge, die kompakt versuchen, einen relevanten Aspekt deutlich zu machen. Besonders nachdem man weiss, was sich dahinter verbirgt, reicht auch der Index mit den zumeist sehr aussagekräftigen Titeln als Erinnerungsstütze.
Besonders wegen der Vielseitigkeit kann ich mir denken, dass für viele Leser etwas dabei ist.
Enthält 97 2-seitige Beiträge, die kompakt versuchen, einen relevanten Aspekt deutlich zu machen. Besonders nachdem man weiss, was sich dahinter verbirgt, reicht auch der Index mit den zumeist sehr aussagekräftigen Titeln als Erinnerungsstütze.
Besonders wegen der Vielseitigkeit kann ich mir denken, dass für viele Leser etwas dabei ist.
Format:Taschenbuch|Von Amazon bestätigter Kauf
Dieses hervorragende Buch ist eine Sammlung von Erfahrungen und Ratschlägen, kurzweilig und bisweilen sogar vergnüglich.
Besonders hat mir die strikte Begrenzung einer Story auf eine Doppelseite gefallen. Die Kapitel sind unabhängig
und somit einzeln konsumierbar (ein gutes ÖPNV-Buch :-) ).
Selbst die (wenigen) Beiträge, mit denen ich mich gar nicht anfreunden konnte, haben mich zumindest zum Nachdenken angeregt.
Den Untertitel "should know" hätte ich allerdings durch "should think about" ersetzt. Das Buch ist nämlich kein Gesetzbuch
sondern mehr eine Erfahrungsschatzkiste.
Besonders hat mir die strikte Begrenzung einer Story auf eine Doppelseite gefallen. Die Kapitel sind unabhängig
und somit einzeln konsumierbar (ein gutes ÖPNV-Buch :-) ).
Selbst die (wenigen) Beiträge, mit denen ich mich gar nicht anfreunden konnte, haben mich zumindest zum Nachdenken angeregt.
Den Untertitel "should know" hätte ich allerdings durch "should think about" ersetzt. Das Buch ist nämlich kein Gesetzbuch
sondern mehr eine Erfahrungsschatzkiste.
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
Amazon.com:
25 Rezensionen
22 von 22 Kunden fanden die folgende Rezension hilfreich
Great bathroom or bus commute reading for programming beginners
22. März 2010
Format:Taschenbuch
I have read programming books for years. There was a time when I could write a "Hello World" program in each of seven or eight languages. That time has passed, mainly because I haven't been intimately involved in any specific software project for many years. Still, I have this habit of reading programming books and enjoying them, perhaps in the hope or expectation that one of these days I'll find myself with a project in front of me, time to work on it, and motivation to learn a new language or tool to make the project's vision a reality. Well, here's the newest book of programming foundational tips that I have read.
97 Things Every Programmer Should Know is a collection of short, two page essays, each by an experienced programmer. The book is a collection of tips and tricks for writing code that works, that is maintainable both by the author and by others, and that will best fit the situation. While the book doesn't measure up to some of my all time favorites in the genre like The Art of Unix Programming or The Pragmatic Programmer, it wasn't meant to. This is not an in depth guide to underlying philosophies of coding practices and standards, but quick hit and run articles that would be easy to fully grasp and absorb in short five minute bursts, such as during work or study breaks (which is how I read the book).
Some of the topics included in this book will seem obvious such as "Don't Ignore That Error" and "Comment Only What The Code Cannot Say," and some tips are going to serve only as reminders to best practices that are sometimes ignored (to our own peril) like "Check Your Code First Before Looking To Blame Others" and "Make Interfaces Easy To Use Correctly And Difficult To Use Incorrectly," there are some real gems in the book that aren't so obvious like one author's instruction to "Read the Humanities" because they are a great tool to help programmers learn to effectively interact with people and not just software and the advice that says "Don't Just Learn the Language, Understand Its Culture" so that you will write effectively and idiomatically within each language, rather than writing the same thing using different words.
I can't say that this is a must-have book for experienced programmers, but anyone at the novice to intermediate levels would certainly benefit from what the book contains. I've enjoyed reading it.
97 Things Every Programmer Should Know is a collection of short, two page essays, each by an experienced programmer. The book is a collection of tips and tricks for writing code that works, that is maintainable both by the author and by others, and that will best fit the situation. While the book doesn't measure up to some of my all time favorites in the genre like The Art of Unix Programming or The Pragmatic Programmer, it wasn't meant to. This is not an in depth guide to underlying philosophies of coding practices and standards, but quick hit and run articles that would be easy to fully grasp and absorb in short five minute bursts, such as during work or study breaks (which is how I read the book).
Some of the topics included in this book will seem obvious such as "Don't Ignore That Error" and "Comment Only What The Code Cannot Say," and some tips are going to serve only as reminders to best practices that are sometimes ignored (to our own peril) like "Check Your Code First Before Looking To Blame Others" and "Make Interfaces Easy To Use Correctly And Difficult To Use Incorrectly," there are some real gems in the book that aren't so obvious like one author's instruction to "Read the Humanities" because they are a great tool to help programmers learn to effectively interact with people and not just software and the advice that says "Don't Just Learn the Language, Understand Its Culture" so that you will write effectively and idiomatically within each language, rather than writing the same thing using different words.
I can't say that this is a must-have book for experienced programmers, but anyone at the novice to intermediate levels would certainly benefit from what the book contains. I've enjoyed reading it.
41 von 47 Kunden fanden die folgende Rezension hilfreich
Abstract and aphoristic
21. Februar 2010
Format:Taschenbuch
If you're just entering the programming world, this collection of 2-page essays might be a useful resource. But if you've been reading programmer blogs for a while, or you've worked on a couple of projects, then there's little of value here. Very few of the essayists choose to tell stories; instead, they say things like "Remember that humans always make mistakes," "Read other people's code" and "Always leave the campground cleaner than you found it."
Speaking of which, where is the code? A book on programming without code is like a day without sunshine! To give one example: The second essay, "Apply Functional Programming Principles" by Edward Garson, assures you that you'll write cleaner, clearer code after working with a functional programming language, but his assurances feel awfully airy without any examples. Maybe this is inevitable in a book that's language-agnostic. Books like Code Complete and Clean Code are hopping with code samples (in C++ and Java, respectively); as a result, they do a far better job of engaging the reader and making abstract concepts stick.
A notable exception is "Code in the Language of the Domain" by Dan North, which uses code to illustrate a concept and uses it well. You might want to read that one, but you don't need to buy the book to do so: All of the essays in this book are Creative Commons-licensed and can be read on the book's official website.
Here is why Joel Spolsky's books are so good: He tells stories. He gives examples. He restrains himself from bombarding the reader with familiar aphorisms. You're imbibing his experiences, not just listening to him ramble. If you haven't already read Joel on Software and More Joel on Software, definitely do so. Also check out the deep interview collection Coders at Work. It's the 98th thing every programmer should know.
Speaking of which, where is the code? A book on programming without code is like a day without sunshine! To give one example: The second essay, "Apply Functional Programming Principles" by Edward Garson, assures you that you'll write cleaner, clearer code after working with a functional programming language, but his assurances feel awfully airy without any examples. Maybe this is inevitable in a book that's language-agnostic. Books like Code Complete and Clean Code are hopping with code samples (in C++ and Java, respectively); as a result, they do a far better job of engaging the reader and making abstract concepts stick.
A notable exception is "Code in the Language of the Domain" by Dan North, which uses code to illustrate a concept and uses it well. You might want to read that one, but you don't need to buy the book to do so: All of the essays in this book are Creative Commons-licensed and can be read on the book's official website.
Here is why Joel Spolsky's books are so good: He tells stories. He gives examples. He restrains himself from bombarding the reader with familiar aphorisms. You're imbibing his experiences, not just listening to him ramble. If you haven't already read Joel on Software and More Joel on Software, definitely do so. Also check out the deep interview collection Coders at Work. It's the 98th thing every programmer should know.
2 von 2 Kunden fanden die folgende Rezension hilfreich
A Starting Point For Your Conversations
17. März 2010
Format:Taschenbuch|Von Amazon bestätigter Kauf
This book is a compilation of short essays ranging on topics as diverse as Bugs, Error Handling, Customers, Refactoring, and Expertise. The purpose of the short essay is not to answer all your questions or be a definitive guide to programming. Rather the purpose is to provide a starting point for a conversation. To this end, I think a practical way to use this book whether in academia or a development team would be to assign groups of essays to be read ahead of time to stimulate classroom or team meeting discussions. Read my full review of the book here,
[...].
[...].
Waren diese Rezensionen hilfreich?
Wir wollen von Ihnen hören.
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?
|
