|
Loading... The Pragmatic Programmerby Andrew Hunt
LibraryThing recommendationsMember recommendationsLoading...
won't like
will probably not like
will probably like
will like
will love Sign up for LibraryThing to find out whether you'll like this book. Excellent book -- provides suggestions and guidance. You will need to apply some thought and sense to apply ( )This book turned me into a professional programmer. Of course I had to work at it, but this book showed me the way. So I owe it a great debt. Like Extreme Programming, none of the techniques are new, they just work very well together. The book is short, some of the tips are strange (tracer bullets?), but most are exquisite, like Broken Windows (an abandoned house will be quickly vandalised if one broken window is not fixed immediately). Often compared to McConnell's [Code Complete], but this book is much broader, and barely touches on actual code or languages. The authors do prefer more dynamic languages, which is why they are now the Ruby champions, but they recognise that most programmers use more mainstream languages. I still follow much of their advice, like investing in my knowledge portfolio, taking time to learn New Stuff. The month I spent learning FORTH is chalked up to experience, and I will probably never get to use my inside knowledge of the Z39.50 protocol (which is how Library Thing talks to library catalogues worldwide), but I tried Python and I now use it every day. Some investments pay big dividends! Thank you, Pragmatic Programmers! programming Straight from the programming trenches, The Pragmatic Programmer: From Journeyman to Master 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, easy to adapt, and reuse. no reviews | add a review
References to this work on external resources.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Book description |
|
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.
(retrieved from Amazon Fri, 24 Apr 2009 07:57:53 -0400)
The first test round has been closed. Visit the Open Shelves Classification group for details.
Quick Links |