Möchten Sie verkaufen? Hier verkaufen
Der Artikel ist in folgender Variante leider nicht verfügbar
Keine Abbildung vorhanden für
Keine Abbildung vorhanden

Den Verlag informieren!
Ich möchte dieses Buch auf dem Kindle lesen.

Sie haben keinen Kindle? Hier kaufen oder eine gratis Kindle Lese-App herunterladen.

The Pragmatic Programmer, from journeyman to master [Taschenbuch]

4.5 von 5 Sternen  Alle Rezensionen anzeigen (35 Kundenrezensionen)

Erhältlich bei diesen Anbietern.

Weitere Ausgaben

Amazon-Preis Neu ab Gebraucht ab
Taschenbuch EUR 32,95  
Taschenbuch, 2000 --  

Hinweise und Aktionen

  • Amazon Trade-In: Tauschen Sie Ihre gebrauchten Bücher gegen einen Amazon.de Gutschein ein - wir übernehmen die Versandkosten. Mehr erfahren


  • Taschenbuch
  • ISBN-10: 020161622X
  • ISBN-13: 978-0201616224
  • Größe und/oder Gewicht: 23,4 x 18,5 x 1,8 cm
  • Durchschnittliche Kundenbewertung: 4.5 von 5 Sternen  Alle Rezensionen anzeigen (35 Kundenrezensionen)
  • Amazon Bestseller-Rang: Nr. 4.626.919 in Bücher (Siehe Top 100 in Bücher)
  • Komplettes Inhaltsverzeichnis ansehen

Mehr über die Autoren

Entdecken Sie Bücher, lesen Sie über Autoren und mehr

Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?

In diesem Buch (Mehr dazu)
Nach einer anderen Ausgabe dieses Buches suchen.
Ausgewählte Seiten ansehen
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis
Hier reinlesen und suchen:


Die hilfreichsten Kundenrezensionen
5 von 5 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen The wisest book about programming I have read 23. Juli 2000
I think almost any programmer can benefit from reading this book. The book is extremely well written and inspiring. Readers of Kent Beck and Martin Fowler will recognize much of their philosophy (see xprogramming.com). Much of the wisdom in the book is condensed into a set of rules listed at the end which makes a very good summary. So even if you have only 20 minutes you will probably walk away inspired and with new insights. What distinguishes this book from other books about programming that I have read (like the Refactoring book by Martin Fowler) is that this book generalizes principles about coding in a very convincing way (many of the principles could probably be helpful for any engineer, not only programmers). Take for example the well known principle of not duplicating code. The authors generalize this principle and say that information should never be duplicated. This means for example that you should write documentation, but the documentation should not duplicate information that is easy to extract from the code (the documentation could for example present the purpose of code and give an overview). Check out the book for many other equally interesting principles!
War diese Rezension für Sie hilfreich?
71 von 82 Kunden fanden die folgende Rezension hilfreich
2.0 von 5 Sternen Disappointing: Shallow and Old School 7. November 2005
Format:Taschenbuch|Verifizierter Kauf
As most other reviewers, I was drawn in by the glowing commentaries here on Amazon.
As background, I've been programming professionally for nine years now, on a variety of projects, but generally high-performance embedded stuff. I'm interested in improving my software development & management skills, and have read a number of other, better books (listed later) about these topics.
My first criticism is that the collection of 50-odd tips are simply too shallowly presented to be very interesting. Generally, if you agree, you say, "yeah, duh," and if you don't, there's no discussion of the point, and no attempt to address known difficulties with "good" practices. There also seemed to be no attempt to balance some of the points. For example, the authors repeatedly talk about writing your code so it's flexible. In general, a good idea. On the other hand, they really seem to think you should be writing everything, regardless of what sort of application it is, to run on different machines, under different operating systems, with and without concurrency, etc. This, to me, just seems foolish, extra work, extra code, extra bugs. The estimates I've seen (in other, better, books) say that just writing re-usable code takes three times more work than "normal" code, ignoring multi-platform complexities.
The old school comment (and I consider myself fairly old school) is there because they very obviously come from a Unix/command line environment. I will admit, they motivated me to improve my scripting skills, something I've been planning on doing for a while. But then they have inane advice, like "use only one editor *for everything*". This is perhaps nice, if you can, but on larger projects or organizations, this probably isn't possible.
Lesen Sie weiter... ›
War diese Rezension für Sie hilfreich?
4 von 4 Kunden fanden die folgende Rezension hilfreich
I bought this on a friend's recommendation, but expected yet another book rehashing the same standard rules: write comments, don't duplicate code, have plans for your projects, eat your vegetables.
Hunt and Thomas vastly exceeded my expectations. This book is never dry, often humorous, and always educational. They don't always say what you expect them to say (e.g., about commenting code), and I didn't always agree with them, but every sentence is full of thoughtful analysis.
One of the best features is their incredibly practical advice -- while yes, this book does teach philosophy and encourages thought, it also provides many immediately-implementable suggestions.
If you aren't a programmer with 10 years experience, buy it anyway -- it is not just for experienced programmers. While you will absorb less of the book, there is still enough to learn, and it's a great book to keep and re-read.
The book includes a pull-out card of the pithy sayings the authors use to sum up each section. Perhaps my mind just doesn't work the way theirs does, but I didn't find their summations to be helpful all the time -- I found myself frequently having to flip back to the section to remember what a particular phrase meant. But it's still useful.
War diese Rezension für Sie hilfreich?
8 von 9 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen Are you programming or hacking? 3. Juni 2000
...and what's the difference? I've often felt that the difference was attitude. Programmers (or "professionals" if you prefer) were continually thinking about what they did, why they did it and how they could do it better. And I don't just mean searching for a new language ("maybe I should learn Java this week?").The rest of us are just tooling around doing the best we can and wondering why it sometimes doesn't work.
"The Pragmatic Programmer" is clearly written by and for professional programmers. Reading it with attention will force you to think deeply about the way you develop software. If your first response is "but this isn't pragmatic" or "I don't have time to do these things" then I encourage you to think again. Perhaps the barrier is change itself. Sure, applying the practices in this book may slow you down in the short term (you always go slower when you're learning a new skill) but the benefits to establishing these practices as habits are enormous.
We are working through this book as part of a weekly study group at our office. This seems to be a great way to investigate things you're uncomfortable. And I don't agree with every practice in this book, but please think about them as deeply as you can before you reject them!
Whenever I interview someone I ask them what book has most influenced the way they develop software. If they answer "The Pragmatic Programmer" (or "Zen and the Art of Motorcycle Maintenance") then they have the job!
War diese Rezension für Sie hilfreich?
Die neuesten Kundenrezensionen
5.0 von 5 Sternen Great delivery
Everything is fine, book is great package is great. Delivery time to another county is also great. Thank you very much
Vor 6 Monaten von Danica Gilic veröffentlicht
5.0 von 5 Sternen Pragmatic Programmer
Sehr geehrte Damen und Herren,
das Buch ist ein Geschenk und kam bei meinem Bekannten sehr gut an.
Ein gesundes neues Jahr
Vor 19 Monaten von Axel Jaworski veröffentlicht
3.0 von 5 Sternen Good basics, but really outdated
Given it's age, this book is not bad, it is just plain old.

However, at least two groups of people might benefit from the book:
1. Lesen Sie weiter...
Veröffentlicht am 7. November 2011 von Hans-Peter Jacobs
5.0 von 5 Sternen Hervorragende Darstellung wichtiger Prinzipien und Methoden
Eine ganze Reihe der hier dargestellten Sachverhalte, Methoden, Prinzipien und Vorgehensweisen waren mir nicht neu - sind aber durchaus in der Mehrzahl der Projekte und bei einer... Lesen Sie weiter...
Veröffentlicht am 30. Mai 2009 von Amazon Customer
3.0 von 5 Sternen Excels in nothing
This book is neither actually bad or good. It makes nothing wrong but could do much better. If you count it up, is has it tells everything a good book for programmers should tell. Lesen Sie weiter...
Veröffentlicht am 26. Mai 2009 von Anonym
5.0 von 5 Sternen A "must" for every programmer
I found the book very intuitive and helpful, with a lot of real tips about software thinking and programming. Lesen Sie weiter...
Veröffentlicht am 27. November 2006 von Razvan Harsan
4.0 von 5 Sternen Ein Votum für guten Programmcode
Pragmatic Programmer sind eine eigene Stilrichtung der leichtgewichtigen Entwicklungsmethoden und eng mit den Extreme Programmern verwandt. Lesen Sie weiter...
Veröffentlicht am 10. März 2004 von M. Mueller-Rohde
3.0 von 5 Sternen Good but shallow advice
The book is full of small pieces of good advice. I kept reading them, noding my head sagely at most of them and thought 'yep, I do that, but how can I do it better?'. Lesen Sie weiter...
Am 17. November 2003 veröffentlicht
5.0 von 5 Sternen Must have
Das Buch beschreibt allgemein und nicht auf eine Sprache festgelegt Herangehensweisen, Verhaltensweisen und Ansichten, die ein Pragmatic Programmer sich zu eigen machen sollte. Lesen Sie weiter...
Am 1. September 2003 veröffentlicht
5.0 von 5 Sternen Mein Programmierbuch des Jahres
Wenn man die rein technischen Fähigkeiten des Programmierens in sich aufgesaugt hat und schon erste größere Projekte hinter sich hat ist es Zeit sich auf den Weg zu... Lesen Sie weiter...
Veröffentlicht am 5. April 2003 von Richard Lippmann
Kundenrezensionen suchen
Nur in den Rezensionen zu diesem Produkt suchen

Kunden diskutieren

Das Forum zu diesem Produkt
Diskussion Antworten Jüngster Beitrag
Noch keine Diskussionen

Fragen stellen, Meinungen austauschen, Einblicke gewinnen
Neue Diskussion starten
Erster Beitrag:
Eingabe des Log-ins

Kundendiskussionen durchsuchen
Alle Amazon-Diskussionen durchsuchen

Ähnliche Artikel finden

Ihr Kommentar