- Taschenbuch: 352 Seiten
- Verlag: Addison Wesley; Auflage: 01 (20. Oktober 1999)
- Sprache: Englisch
- ISBN-10: 020161622X
- ISBN-13: 978-0201616224
- Größe und/oder Gewicht: 18,7 x 2,7 x 23,4 cm
- Durchschnittliche Kundenbewertung: 36 Kundenrezensionen
- Amazon Bestseller-Rang: Nr. 11.996 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)
- Komplettes Inhaltsverzeichnis ansehen
Andere Verkäufer auf Amazon
+ EUR 3,00 Versandkosten
+ kostenlose Lieferung
The Pragmatic Programmer. From Journeyman to Master (Englisch) Taschenbuch – 20. Oktober 1999
|Neu ab||Gebraucht ab|
Wird oft zusammen gekauft
Kunden, die diesen Artikel gekauft haben, kauften auch
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?
Programmers are craftspeople trained to use a certain set of tools (editors, object managers, version trackers) to generate a certain kind of product (programs) that will operate in some environment (operating systems on hardware assemblies). Like any other craft, computer programming has spawned a body of wisdom, most of which isn't taught at universities or in certification classes. Most programmers arrive at the so-called tricks of the trade over time, through independent experimentation. In The Pragmatic Programmer, Andrew Hunt and David Thomas codify many of the truths they've discovered during their respective careers as designers of software and writers of code.
Some of the authors' nuggets of pragmatism are concrete, and the path to their implementation is clear. They advise readers to learn one text editor, for example, and use it for everything. They also recommend the use of version-tracking software for even the smallest projects, and promote the merits of learning regular expression syntax and a text-manipulation language. Other (perhaps more valuable) advice is more light-hearted. In the debugging section, it is noted that, "if you see hoof prints think horses, not zebras." That is, suspect everything, but start looking for problems in the most obvious places. There are recommendations for making estimates of time and expense, and for integrating testing into the development process. You'll want a copy of The Pragmatic Programmer for two reasons: it displays your own accumulated wisdom more cleanly than you ever bothered to state it, and it introduces you to methods of work that you may not yet have considered. Working programmers will enjoy this book. --David Wall
Topics covered: A useful approach to software design and construction that allows for efficient, profitable development of high-quality products. Elements of the approach include specification development, customer relations, team management, design practices, development tools, and testing procedures. This approach is presented with the help of anecdotes and technical problems.
What others in the trenches say about The Pragmatic Programmer..."The cool thing about this book is that it's great for keeping the programming process fresh. The book helps you to continue to grow and clearly comes from people who have been there." --Kent Beck, author of Extreme Programming Explained: Embrace Change "I found this book to be a great mix of solid advice and wonderful analogies!" --Martin Fowler, author of Refactoring and UML Distilled "I would buy a copy, read it twice, then tell all my colleagues to run out and grab a copy. This is a book I would never loan because I would worry about it being lost." --Kevin Ruland, Management Science, MSG-Logistics "The wisdom and practical experience of the authors is obvious. The topics presented are relevant and useful...By far its greatest strength for me has been the outstanding analogies--tracer bullets, broken windows, and the fabulous helicopter-based explanation of the need for orthogonality, especially in a crisis situation. I have little doubt that this book will eventually become an excellent source of useful information for journeymen programmers and expert mentors alike."--John Lakos, author of Large-Scale C++ Software Design "This is the sort of book I will buy a dozen copies of when it comes out so I can give it to my clients." --Eric Vought, Software Engineer "Most modern books on software development fail to cover the basics of what makes a great software developer, instead spending their time on syntax or technology where in reality the greatest leverage possible for any software team is in having talented developers who really know their craft well. An excellent book." --Pete McBreen, Independent Consultant "Since reading this book, I have implemented many of the practical suggestions and tips it contains. Across the board, they have saved my company time and money while helping me get my job done quicker! This should be a desktop reference for everyone who works with code for a living." --Jared Richardson, Senior Software Developer, iRenaissance, Inc. "I would like to see this issued to every new employee at my company..." --Chris Cleeland, Senior Software Engineer, Object Computing, Inc. "If I'm putting together a project, it's the authors of this book that I want...And failing that I'd settle for people who've read their book."--Ward Cunningham Straight from the programming trenches, The Pragmatic Programmer cuts through the increasing specialization and technicalities of modern software development to examine the core process--taking a requirement and producing working, maintainable code that delights its users.It covers topics ranging from personal responsibility and career development to architectural techniques for keeping your code flexible and easy to adapt and reuse. Read this book, and you'll learn how to *Fight software rot; *Avoid the trap of duplicating knowledge; *Write flexible, dynamic, and adaptable code; *Avoid programming by coincidence; *Bullet-proof your code with contracts, assertions, and exceptions; *Capture real requirements; *Test ruthlessly and effectively; *Delight your users; *Build teams of pragmatic programmers; and *Make your developments more precise with automation. Written as a series of self-contained sections and filled with entertaining anecdotes, thoughtful examples, and interesting analogies, The Pragmatic Programmer illustrates the best practices and major pitfalls of many different aspects of software development.Whether you're a new coder, an experienced programmer, or a manager responsible for software projects, use these lessons daily, and you'll quickly see improvements in personal productivity, accuracy, and job satisfaction. You'll learn skills and develop habits and attitudes that form the foundation for long-term success in your career.You'll become a Pragmatic Programmer. Alle Produktbeschreibungen
Kunden, die diesen Artikel angesehen haben, haben auch angesehen
Derzeit tritt ein Problem beim Filtern der Rezensionen auf. Bitte versuchen Sie es später noch einmal.
If The Pragmatic Programmer could be condensed into half the words, it might get 4 or even 5 stars but not this way.
I'm 2/3 through and I don't know whether I should finish it. I'd say read Clean Code instead. It covers almost everything this book does, but much better.
Experience it yourself.
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. I use the IDE required by the project, a different editor for documentation (also required) and a third one for doing hex & advanced search and replace. Perhaps with emacs and 47 scripts this wouldn't be necessary, but I'm not convinced it would be efficient either.
All in all, the advice is generally good, but I think there are better books out there (e.g. Code Complete, Writing Solid Code, Rapid Development, The Mythical Man-Month, C++ Coding Standards). As a light book to get you thinking about your craft, it's not bad, but that's the best I can say about it.
I can't emphasize this point enough. This book isn't a collection of stories that support the author's methodology or design technique. It isn't a book designed to sell his software tools. It is a book that will teach you to work more effectively. It talks about practical tips for prototyping projects (different ways to prototype, which is appropriate when, how to justify the time and expense to your manager), how to deal with and communicate effectively with customers, co-workers and managers.... if it sounds like The Pragmatic Programmer covers a lot of topics, that's because it does.
If you work with software or manage people who do, you owe it to yourself to read this book! I've been writing code (and reading these types of books) for nearly 10 years, and this is the best one I've ever read.
Möchten Sie weitere Rezensionen zu diesem Artikel anzeigen?
Die neuesten Kundenrezensionen
However, at least two groups of people might benefit from the book:
1.Lesen Sie weiter