|
||||||||||||||||||||
|
||||||||||||||||||||
|
||||||||||||||||||||
The Productive Programmer (Theory in Practice (O'Reilly))
und über 1 Million weitere Bücher verfügbar für Amazon Kindle .
Erfahren Sie mehr
| |||||||||||||||
 Gutschein erhalten
Tauschen Sie jetzt The Productive Programmer (Theory in Practice (O'Reilly)) gegen einen Amazon-Gutschein in Höhe von EUR 6,60 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
|
Mehr über den Autor
Entdecken Sie Bücher, lesen Sie über Autoren und mehr
› Besuchen Sie die Seite von Neal Ford auf Amazon
› Besuchen Sie die Seite von Neal Ford auf Amazon
Produktbeschreibungen
Pressestimmen
"... Quer durch alle Systeme wandernd stellt Ford eine Fülle nützlicher Helfer und Tipps vor, die alltägliche Aufgaben vereinfachen, häufig sogar ohne menschliches Zutun. [...] Ford schließt mit einer bunten Mischung von Rezepten, die den Entwurf von Software von Beginn an verbessern. Typische zeitraubende Probleme sollen so gar nicht erst entstehen. ..." - c't, September 2008 "Wie für O'Reilly üblich, ist das Buch qualitätsvoll gestaltet, reich bebildert und leicht verständlich. Auch wer Englisch nicht perfekt beherrscht, wird also den Text ohne große Probleme verstehen." - Java Spectrum, Juli 2011
Kurzbeschreibung
Anyone who develops software for a living needs a proven way to produce it better, faster, and cheaper. The Productive Programmer offers critical timesaving and productivity tools that you can adopt right away, no matter what platform you use. Master developer Neal Ford not only offers advice on the mechanics of productivity-how to work smarter, spurn interruptions, get the most out your computer, and avoid repetition-he also details valuable practices that will help you elude common traps, improve your code, and become more valuable to your team. You'll learn to: * Write the test before you write the code * Manage the lifecycle of your objects fastidiously * Build only what you need now, not what you might need later * Apply ancient philosophies to software development * Question authority, rather than blindly adhere to standards * Make hard things easier and impossible things possible through meta-programming * Be sure all code within a method is at the same level of abstraction * Pick the right editor and assemble the best tools for the job This isn't theory, but the fruits of Ford's real-world experience as an Application Architect at the global IT consultancy ThoughtWorks. Whether you're a beginner or a pro with years of experience, you'll improve your work and your career with the simple and straightforward principles in The Productive Programmer.
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).
|
Kundenrezensionen
Die hilfreichsten Kundenrezensionen
2 von 3 Kunden fanden die folgende Rezension hilfreich
Format:Taschenbuch
Die ersten zwei Drittel des Buches halten, was der Titel verspricht. Der Autor erklärt wie man seine Produktivität (mehr schaffen in weniger Zeit) steigern kann. Ab und an werden einige Tools für meinen Geschmack zu ausführlich behandelt, aber das ist kein echter Kritikpunkt.
Was mich wirklich gestört hat war das letzte Drittel, in der es zum größten Teil um Software-Engineering geht. Der Autor weicht hier oft vom Thema Produktivität ab und redet über Programmierprinzipien, die nur entfernt mit Produktivität zu tun haben. Es scheint als ob der Inhalt die Seitenzahl erhöhen soll. Besser wäre eine konsequente Einhaltung des Themas gewesen.
Was mich wirklich gestört hat war das letzte Drittel, in der es zum größten Teil um Software-Engineering geht. Der Autor weicht hier oft vom Thema Produktivität ab und redet über Programmierprinzipien, die nur entfernt mit Produktivität zu tun haben. Es scheint als ob der Inhalt die Seitenzahl erhöhen soll. Besser wäre eine konsequente Einhaltung des Themas gewesen.
3 von 5 Kunden fanden die folgende Rezension hilfreich
Format:Taschenbuch
Dieses Buch bietet eine Vielzahl an Tipps & Tricks.
Der Autor verzichtet auf theoretische Herleitung und erläutert anhand von Stories und Beispielen, wie man in unterschiedlichen Umgebungen (Win, .*nix, Mac) seine Software-Entwicklungs-Produktivität deutlich steigern kann, ohne Frameworks oder komplexe Tools einsetzen zu müssen.
Eingefahrene Verhaltensweisen werden hinterfragt und praktische Beispiele gezeigt. Dadurch, dass mehrere Plattformen abgedeckt werden gibt es immer Bereiche, die einen nicht so interessieren (ich habe bspw. nichts mit Macs zu tuen), aber schon ein Tipp, der in der Praxis eingesetzt werden kann ist den Preis und die Lesezeit wert.
Und ich habe auch nach vielen Jahren professioneller Software-Entwicklung einige solcher Tipps gefunden.
Der Autor verzichtet auf theoretische Herleitung und erläutert anhand von Stories und Beispielen, wie man in unterschiedlichen Umgebungen (Win, .*nix, Mac) seine Software-Entwicklungs-Produktivität deutlich steigern kann, ohne Frameworks oder komplexe Tools einsetzen zu müssen.
Eingefahrene Verhaltensweisen werden hinterfragt und praktische Beispiele gezeigt. Dadurch, dass mehrere Plattformen abgedeckt werden gibt es immer Bereiche, die einen nicht so interessieren (ich habe bspw. nichts mit Macs zu tuen), aber schon ein Tipp, der in der Praxis eingesetzt werden kann ist den Preis und die Lesezeit wert.
Und ich habe auch nach vielen Jahren professioneller Software-Entwicklung einige solcher Tipps gefunden.
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
Amazon.com:
35 Rezensionen
18 von 18 Kunden fanden die folgende Rezension hilfreich
Concise work for productive, common sense development
13. September 2008
Format:Taschenbuch
This is a terrific book for boosting your productivity in two areas: how you work, and how you code.
The first section of the book, Mechanics, focuses on tools you can use to boost your productivity as you're working with your system. Ford launches off into an exploration of lots of little crazy tools that help you automate or ease repetitive tasks. You'll find lots of goodies from virtual desktops to shortcut tips/launchers, to using Ruby to script everything from splitting up SQL to automatically sorting your laundry and washing it for you.[1]
All these little tools and tricks add up to drastic decreases in the amount of friction you're forced to suffer through while doing your daily job. Cutting this friction lets you focus on the job at hand, instead of trying to bend your environment to your will.
The second section of the book, Practice, discusses ways to speed your development. There's an awful lot of goodness in this portion of the book, ranging from re-emphasizing critical aspects of object oriented programming, to object and method composition. Ford walks through a lot of great stories meant to get you to re-evaluate why you do things a certain way. The infamous Angry Monkeys story gets pulled out as an example, and Ford also concisely covers development principles like the Law of Demeter, Occam's Razon, and his Polyglot Programming meme.
The book's concise, amazingly well written, and a definite must-have for your bookshelf.
The first section of the book, Mechanics, focuses on tools you can use to boost your productivity as you're working with your system. Ford launches off into an exploration of lots of little crazy tools that help you automate or ease repetitive tasks. You'll find lots of goodies from virtual desktops to shortcut tips/launchers, to using Ruby to script everything from splitting up SQL to automatically sorting your laundry and washing it for you.[1]
All these little tools and tricks add up to drastic decreases in the amount of friction you're forced to suffer through while doing your daily job. Cutting this friction lets you focus on the job at hand, instead of trying to bend your environment to your will.
The second section of the book, Practice, discusses ways to speed your development. There's an awful lot of goodness in this portion of the book, ranging from re-emphasizing critical aspects of object oriented programming, to object and method composition. Ford walks through a lot of great stories meant to get you to re-evaluate why you do things a certain way. The infamous Angry Monkeys story gets pulled out as an example, and Ford also concisely covers development principles like the Law of Demeter, Occam's Razon, and his Polyglot Programming meme.
The book's concise, amazingly well written, and a definite must-have for your bookshelf.
21 von 24 Kunden fanden die folgende Rezension hilfreich
The Mechanics of a Pragmatic Programmers daily work
28. Juli 2008
Format:Taschenbuch
I've been reading Neal's blog for a while. So I've been looking forward to the book. (I even accidentally ordered it twice - one was the pre-buy at amazon, which I forgot about).
I spend the last two days reading the book and found it quite helpful. There are a lot of concrete tips and examples for immediate use and daily improvement of your mechanic skills. Many of the experiences regarding the effective use of the tools at hand that he describes are well known to me. I can't really understand how developers are not keen to improve their productivity.
Neal's book is a good addition to the PragProgs masterpiece. It concentrates more on the mechanics and on some principles of productive software development. So the triad of values-principles-patterns got a son named mechanics.
What I missed in the book was:
* a comprehensive list of the notes at the end.
* Christopher Alexanders appearance as one of the philosophers.
* the notion of cheat sheets/refcards
* references to Martin Odersky's Scala the scalable language
* references to Kent Becks "Implementation Patterns" (especially in the SLAP section)
As being a developer myself I was a bit disappointed by the quality of the examples (the solutions not the starting points) and a bit by the correctness of the text (typos). I spotted several errors, some bad designs and some uninformed choices even on the first read of the book. I'll post them to the errata page.
Neals suggestion of an online repository of productive programmers tools, tips and mechanics is a great idea. I'd really like to join this effort.
Michael
http://creating.passionate-developers.org
I spend the last two days reading the book and found it quite helpful. There are a lot of concrete tips and examples for immediate use and daily improvement of your mechanic skills. Many of the experiences regarding the effective use of the tools at hand that he describes are well known to me. I can't really understand how developers are not keen to improve their productivity.
Neal's book is a good addition to the PragProgs masterpiece. It concentrates more on the mechanics and on some principles of productive software development. So the triad of values-principles-patterns got a son named mechanics.
What I missed in the book was:
* a comprehensive list of the notes at the end.
* Christopher Alexanders appearance as one of the philosophers.
* the notion of cheat sheets/refcards
* references to Martin Odersky's Scala the scalable language
* references to Kent Becks "Implementation Patterns" (especially in the SLAP section)
As being a developer myself I was a bit disappointed by the quality of the examples (the solutions not the starting points) and a bit by the correctness of the text (typos). I spotted several errors, some bad designs and some uninformed choices even on the first read of the book. I'll post them to the errata page.
Neals suggestion of an online repository of productive programmers tools, tips and mechanics is a great idea. I'd really like to join this effort.
Michael
http://creating.passionate-developers.org
13 von 15 Kunden fanden die folgende Rezension hilfreich
Great book but not without faults
10. Januar 2009
Format:Taschenbuch
I saw Neal the first time at DLW Europe. I'd like to check out the speakers online before deciding which talks to attend - the results were not positive at all; IT consultant (we've had our share at work) + spending lots of time speaking on conferences, that's a combination not likely to give me warm feelings. I still ended up in attending his talk because of lack of alternatives and thank god I did. Neal isn't only a great speaker but he also had something to say and the necessary experience and war stories to back it up. I ended up by attending every presentation of Neal plus - back at work - giving a presentation of his talks to my fellow co-workers.
Finding out that he now has written a book - I instantly had to read it. And the book is certainly a valuable read that I'll keep around as reference at least for a while. There's lots of great tips about tools, automation, ... that will certainly find their way into my professional life. However, it did not blow me off my feet. I've read "Pragmatic Programmer - From Journeyman to Master" before (a perfect book in my opinion) and this book does not quite measure up to it. The style is not as perfect - the information not as well-presented. However what I miss most is that Neal sometimes present a topic but then does not follow up with "How to get started" - most notably with "Polyglot Programming" and "Test driven design". I know that both topics are maybe out of scope of the book but then at least a reference to another book, website, ... would have been great. So even if I'm all psyched to up try to apply this principles now at my current projects, I know from past experience that adding new languages in any mix more often result in time wasted time because of integration issues... and how to start TDD on a project that's been going on for 15 years without any unit tests is beyond my imagination.
Don't get me wrong - it's a great book and well worth the read; it just needs some polishing to get it to excellent...
Finding out that he now has written a book - I instantly had to read it. And the book is certainly a valuable read that I'll keep around as reference at least for a while. There's lots of great tips about tools, automation, ... that will certainly find their way into my professional life. However, it did not blow me off my feet. I've read "Pragmatic Programmer - From Journeyman to Master" before (a perfect book in my opinion) and this book does not quite measure up to it. The style is not as perfect - the information not as well-presented. However what I miss most is that Neal sometimes present a topic but then does not follow up with "How to get started" - most notably with "Polyglot Programming" and "Test driven design". I know that both topics are maybe out of scope of the book but then at least a reference to another book, website, ... would have been great. So even if I'm all psyched to up try to apply this principles now at my current projects, I know from past experience that adding new languages in any mix more often result in time wasted time because of integration issues... and how to start TDD on a project that's been going on for 15 years without any unit tests is beyond my imagination.
Don't get me wrong - it's a great book and well worth the read; it just needs some polishing to get it to excellent...
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?
|
