|
The Pragmatic Programmer: From Journeyman to Master |  | Authors: Andrew Hunt, David Thomas Publisher: Addison-Wesley Professional Category: Book
List Price: $49.99 Buy New: $28.57 as of 3/20/2010 22:51 MDT details You Save: $21.42 (43%)
New (35) Used (21) from $27.43
Seller: the_book_depository_ Rating: 147 reviews Sales Rank: 5481
Media: Paperback Pages: 352 Number Of Items: 1 Shipping Weight (lbs): 1.2 Dimensions (in): 9.1 x 7.3 x 0.8
ISBN: 020161622X Dewey Decimal Number: 005.1 UPC: 785342616224 EAN: 9780201616224 ASIN: 020161622X
Publication Date: October 30, 1999 Availability: Usually ships in 1-2 business days
| |
| Features:
| • | ISBN13: 9780201616224 | | • | Condition: NEW | | • | Notes: Brand New from Publisher. No Remainder Mark. |
|
| Also Available In:
|
| Accessories:
|
| Similar Items:
| |
| Editorial Reviews:
Amazon.com Review 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.
Product Description
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.
|
| Customer Reviews:
Showing reviews 1-5 of 147
Great book for team book study January 21, 2010 Peter B. Marsden (Charlotte, NC) I have used this book for two book studies with teams mixed with developers and QA. It stimulates great conversations and has memorable examples that come up in meetings years later. It is a fun and easy read. I recommend it highly.
I hate it. November 8, 2009 123 12 out of 21 found this review helpful
99% of this book is talking from a business perspective. Do this if you want to be profitable do that if you want to be profitable. I'm a hobby programmer (sometimes I do freelance but not often). The professional tone of the book was a bit of a put-off. I'm not interested in becoming a master of business.
I've invested quite a bit of time learning C++. According to this book it was a waste. According to this book you're supposed to learn a new language every year! Learn a new language every year! How incredible. I challenge anyone to learn C++ in a year. I've read that most people never learn C++ in its entirety, so it might take a *long* time to learn it. I think to learn most languages (to the point where you could be said to be good for fluent with that language) it will take a year or more.
Another bit of garbage in this book was right in the beginning. It lists bullet points for what a pragmatic programmer should be. One points says "be an early adopter of new technology". A few bullet points later it says "be a critical thinker". I have met a lot of early adopters, and a lot of critical thinkers, and the two are almost if not completely opposite. A critical thinker might decide that if a system should be adopted, it should pass the test of time. A good personal example of this would be my decision to see how people liked Windows Vista before buying it for my machine. As it turned out Vista was a bit of a flop, so I kept XP Pro for a bit longer. Now that Windows 7 is out, and I've heard good things, I will probably install it on my machine. In this case I'm not being an early adopter, I'm biding my time and learning from others experiences.
What can I say I guess I'm not very pragmatic :P
As far as recommendations goes, the last good book I've read in this type of genre would have been Code Craft (No Starch Press).
Definitely a Classic October 25, 2009 D. Nascimbeni (Manchester, CT) I found the book to be worth a read (which doesn't take long). Filled with lots of lessons most programmers learn with time/experience. It's not a book on design patterns or anything. It's more of a book explaining things like planning, how to be most productive, the difference between a prototype and tracer bullets, why code generation is powerful/how to do it, the benefits of decoupling...etc. It's quite a little gem in many ways... and best of all, easy to read.
A Guide to better life - as a programer October 18, 2009 E. Golan (Israel) 0 out of 4 found this review helpful
I started reading the book a few days ago and enjoy it every minute.
I haven't finished reading it, but feel confident to review it.
I recommend this book to any person who wants to be a better programmer.
When I first tried to describe what this book is about, I made an analogy to the kinds of books the gives you 'good advices for better life'.
One of the rules to have better life is, if you read these kinds of books, at least try to follow what they suggest.
Well, since starting reading Pragmatic, I keep trying to follow the advices I've read.
I was happy to see that some of the advices, I kept even before.
I feel that in the subjects that I read and started following, I became better.
Following the advices made me better in the small and nuance steps. Al and all, a much better developer.
Some of the advices are not applicable for my field and what I do, so I just read the background of them.
I do read this book cover to cover for the first time, bu after that I plan to read each advice when needed.
I even started explaining some of the advices to my colleagues. They were very happy with them.
Go buy it!
A mile wide and an inch deep June 23, 2009 Jason Axtell 8 out of 9 found this review helpful
As an experienced software developer, I was looking for a book that I could recommend to more junior members of my team to help them improve their skills. This book wasn't it. Although this book has a lot of very good advice in it, it's mostly a mile wide and an inch deep. For a junior developer not already familiar with these ideas, there isn't enough meat here for them to gain any real appreciation or understanding of the material.
In contrast, take Code Complete. It's *only* a book about code construction, a small portion of what Pragmatic Programmer tries to cover. And yet, Code Complete weighs in at nearly 900 pages, versus Pragmatic's 300 or so. The difference is detail. Code Complete really digs into each topic, explaining it completely and giving examples. It's a bigger read to be sure, but when you're done, you have truly learned something. When you finish Pragmatic Programmer, you're left wanting another book that actually explains everything you just read.
Showing reviews 1-5 of 147
|
|
|
CERTAIN CONTENT THAT APPEARS ON THIS SITE COMES FROM AMAZON SERVICES LLC. THIS CONTENT IS PROVIDED ‘AS IS’ AND IS SUBJECT TO CHANGE OR REMOVAL AT ANY TIME. Working Dogs | |