The Book
Information
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.
Created by: Andreas.en on May 20th 2006, 17:21.
Editing privileges: Any pro user.
How to learn? Read once.
Being studied by: Andreas.en, FAM, go888, osmijam, bohulu and 44 other persons.
Rating: 
Autoren: Andrew Hunt, David Thomas
ISBN: 020161622X
Publication date: 1999-10-20
Edition: Paperback
Publisher: Addison-Wesley Professional
Number of Pages: 352
Price: From $29.48 at Amazon (on February 19th 2007, 04:25)
Reviews
Invaluable nuggets
Read
A collaborative work worthy of a top-ten ranking for software development "bible".
This book distills everything pertinent to real-world "rubber-hits-the-road" software development. Given that there isn't really another type, save that which is embraced in the dank halls of academia, go to this book first. Yes, even before "Code Complete".
The style is refreshingly unassuming and devoid of religious side-taking (bar a modest but controlled bent towards a unixy philosophy). All sides are presented, and a final "we feel ..." proffering a very soundly backed up opinion on the subject in discussion. It's written for the reader--easy-going and coloured with industry anecdotes and graceful humour.
References are ubiquitous, indicating a well-balanced text from true field professionals.
Andy and Dave regularly re-inforce their modus operandi, that of pragmatic professional. Especially noteworthy is the no-nonsense style--unlike other books in this category, lip-service to the "fashion of the day" is avoided--accepted norms are questioned, but done so gracefully, and with respect.
The entire book resonated with me, and I regularly found myself nodding in silent agreement. I would have to say that the most significant thing I got out of this book though was the relentless philosophy of "do it right", from uncomprisingly implementing "don't-repeat-yourself" to choosing the most appropriate tool for the job (rid yourself of those emotional attachments), all communicated in a wonderfully modest manner.
A concise and practical book
Read
I like how concise this book is. It hits important points in two pages. It's like a cliff a notes to good programming practices. You will need deeper resources to implement the recomendations in this book but it is full of very good practices. I recomend it for any programmer.
A Classic--In Any Technology
Read
This is one of those classics that belong beside Fred Brooks "The Mythical Man-Month" in your library. (And your mind)
The examples are in Java and C++ (ick--I am a .Net programmer), but the generic nature of the material in the book has made it useful to me in the .Net camp. In some ways, reading it from a .Net background has helped since it forces thought. This book is packed with great tips--most of which apply in any language.
I highly recommend this to any software developer regardless of technology leanings. I recently recommended it in our area .Net User's Group meeting--which for a book that contains Java is HIGHLY unusual!
This book triggered an inflextion point
Read
When I first read this book in 2001 I was burnt out. I had just spend the dot com years on a profitable, for me, death march. This book provided me with the perspective I needed to get my love of creating software back on track. I highly recommend this book.
Good checklist of tips, falls short
Read
I like this book for the most part. I find it falls short in describing a good (appropriate) use of Architecture Specifications, Design Plans, etc. This is especially true for those who are self-taught or went to school years ago and may not have been exposed to this kind of development process. While the author's approach may be great for some, experience has shown me that whether I'm working in a large team environment or by myself, having good requirements, architecture specifications, and development plans do a lot to kill programming bugs before they occur, and more importantly, serve as a compass for the code-writing portion of the development process, no matter what the size of the coding team. I think readers will probably benefit more by reading "Code Complete" 2nd Ed. (2004) by Steve McConnell.
Comments
No comments yet.
Write comment
Only signed in users may write comments. Sign in now!