- Amazon Student members save an additional 10% on Textbooks with promo code TEXTBOOK10. Enter code TEXTBOOK10 at checkout. Here's how (restrictions apply)
The Pragmatic Programmer: From Journeyman to Master Paperback – Oct 20 1999
|New from||Used from|
Special Offers and Product Promotions
Frequently Bought Together
Customers Who Bought This Item Also Bought
To get the free app, enter your e-mail address or mobile phone number.
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.
From the Publisher
As a reviewer I got an early opportunity to read the book you are holding. It was great, even in draft form. Dave Thomas and Andy Hunt have something to say, and they know how to say it. I saw what they were doing and I knew it would work. I asked to write this foreword so that I could explain why.
Simply put, this book tells you how to program in a way that you can follow. You wouldn't think that that would be a hard thing to do, but it is. Why? For one thing, not all programming books are written by programmers. Many are compiled by language designers, or the journalists who work with them to promote their creations. Those books tell you how to talk in a programming language---which is certainly important, but that is only a small part of what a programmer does.
What does a programmer do besides talk in programming language? Well, that is a deeper issue. Most programmers would have trouble explaining what they do. Programming is a job filled with details, and keeping track of those details requires focus. Hours drift by and the code appears. You look up and there are all of those statements. If you don't think carefully, you might think that programming is just typing statements in a programming language. You would be wrong, of course, but you wouldn't be able to tell by looking around the programming section of the bookstore.
In The Pragmatic Programmer Dave and Andy tell us how to program in a way that we can follow. How did they get so smart? Aren't they just as focused on details as other programmers? The answer is that they paid attention to what they were doing while they were doing it---and then they tried to do it better.
Imagine that you are sitting in a meeting. Maybe you are thinking that the meeting could go on forever and that you would rather be programming. Dave and Andy would be thinking about why they were having the meeting, and wondering if there is something else they could do that would take the place of the meeting, and deciding if that something could be automated so that the work of the meeting just happens in the future. Then they would do it.
That is just the way Dave and Andy think. That meeting wasn't something keeping them from programming. It was programming. And it was programming that could be improved. I know they think this way because it is tip number two: Think About Your Work.
So imagine that these guys are thinking this way for a few years. Pretty soon they would have a collection of solutions. Now imagine them using their solutions in their work for a few more years, and discarding the ones that are too hard or don't always produce results. Well, that approach just about defines pragmatic. Now imagine them taking a year or two more to write their solutions down. You might think, That information would be a gold mine. And you would be right.
The authors tell us how they program. And they tell us in a way that we can follow. But there is more to this second statement than you might think. Let me explain.
The authors have been careful to avoid proposing a theory of software development. This is fortunate, because if they had they would be obliged to warp each chapter to defend their theory. Such warping is the tradition in, say, the physical sciences, where theories eventually become laws or are quietly discarded. Programming on the other hand has few (if any) laws. So programming advice shaped around wanna-be laws may sound good in writing, but it fails to satisfy in practice. This is what goes wrong with so many methodology books.
I've studied this problem for a dozen years and found the most promise in a device called a pattern language. In short, a pattern is a solution, and a pattern language is a system of solutions that reinforce each other. A whole community has formed around the search for these systems.
This book is more than a collection of tips. It is a pattern language in sheep's clothing. I say that because each tip is drawn from experience, told as concrete advice, and related to others to form a system. These are the characteristics that allow us to learn and follow a pattern language. They work the same way here.
You can follow the advice in this book because it is concrete. You won't find vague abstractions. Dave and Andy write directly for you, as if each tip was a vital strategy for energizing your programming career. They make it simple, they tell a story, they use a light touch, and then they follow that up with answers to questions that will come up when you try.
And there is more. After you read ten or fifteen tips you will begin to see an extra dimension to the work. We sometimes call it QWAN, short for the quality without a name. The book has a philosophy that will ooze into your consciousness and mix with your own. It doesn't preach. It just tells what works. But in the telling more comes through. That's the beauty of the book: It embodies its philosophy, and it does so unpretentiously.
So here it is: an easy to read---and use---book about the whole practice of programming. I've gone on and on about why it works. You probably only care that it does work. It does. You will see. --Ward CunninghamSee all Product Description
Inside This Book(Learn More)
What Other Items Do Customers Buy After Viewing This Item?
Top Customer Reviews
The authors dole out a lot of solid advice, which is the book's strength. I found myself disagreeing with very little. There are memorable tips and some good stories. The writing style is also very accessible and conducive to diving in at any page.
The book seems a bit lightweight. The exercises are a little simple and I don't think you'll find yourself going back to this book a lot. Also, the typeface is annoyingly large.
I'd recommend this to someone who has done some programming and understands the syntax and fundamentals but hasn't gotten into programming larger pieces of software. I think that if you have programmed anything significant you won't find much new in here.
if you're looking for something interesting, "the mythical man month" is a lot better, even though its dated. "inmates are running the asylum" by alan cooper is also great in that it creatively and productively challenges many of the old saws that books like "pragmatic programmer" trot out time and time again (i particularly like Cooper's rant against letting customers dictate design decisions and product paths).
All the tips are covered superficially, but with enough depth that you understand the what and the why, and can still go to the next one quickly. Further chapters don't depend on previous ones, so you can jump in at any topic that interests you. As such, it makes a good a-tip-a-day read.
While the main advice it provides is simply "care about your craft", it is advice I wish more would follow and this book just might convince some and teach the beginners some of what that actually entails. In the end, the simplicity of this book is what makes it such an interesting read.
The font is indeed a bit too big to be comfortable on the eyes, but the chapters are short enough that you aren't forced to strain for hours. The layout of the chapters also seems a bit random.
1. Much of what the authors espouse is just common sense and would be picked up or developed by most bright developers on their own.
2. Some of what the authors espouse is just wrong...we have suggestions that if your code is correct then it will take little effort to make it run on Win16, Win 32 , and different flavors of Unix or whatever environment. I disagree. This would only be true for the most trivial programs. Even using a factory pattern, as opposed to the usual compiler switches, one could build such a losely coupled and modern system to run on different environments...but it would hardly be easy to do because the different environments require separate (and hardwon!) skillsets/knowledge...not easy to find in one developer...Perhaps the authors should try their hand on some cross-browser, cross operating system DHTML...and make sure it runs on all versions of Netscape to boot.
3. The authors elevating of the text editor and command line over IDE is just non-sense...and again wrong...they say you cannot configure the IDEs...anyone who has written an add-in for VB knows it is indeed possible.
4. I could go on, but I will conclude with their total lack of understanding of Physics which they quote wrongly...the Universe does not split(Shroedinger's cat) after a measurement and Heisenberg said it was ,IN PRINCIPAL, impossible to perform certain measurements without disturbing the system...On the other hand, it is perfectly possible to perform debugging without disturbing the code...
5. And they have the audacity to call their book "...Read more ›
Most recent customer reviews
In a nutshell, this book explains a great many things that all software professionals should know and practice. Read morePublished 8 months ago by John Jensen
This book is a must ready for all software developers. We are reading this book as a team at work. It's suggestions are invaluable to improving my work.Published 23 months ago by Allan Caine
Very good book for software engineers caring about their craft!
Manage to put into words stuff that most competent already feel, but have trouble phrasing.
What a bore! I got this book in hopes of acquiring something that would forever change my coding style, and introduce me to the many deeper concepts of programming that I didn't... Read morePublished on Aug. 13 2011 by JB
Many experienced programmers will have already learned many of the lessons in this book and will be frustrated by the lack of depth. Read morePublished on May 22 2009 by Brent Knowles
This need to be read. Re-read and Re-Re-read every once in a while.
Those are great type that only experience gives you.
Pragmatic Programmer: From Journeyman to Master is a book that every developer should have in their book shelves. Read morePublished on Nov. 17 2007 by Adriano N. Oliveira
The Pragmatic Programmer: From Journeyman to Master, is a must-read for everyone involved in the software industry. Read morePublished on April 2 2006 by Adam Kahtava