<![CDATA[The Pragmatic Programmer: From Journeyman to Master]]>

false <![CDATA[The Pragmatic Programmer: From Journeyman to Master]]>

4099

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.

7809

book

1999

The Pragmatic Programmer: From Journeyman to Master

total:373|5:198|4:134|3:31|2:7|1:3|

373

1636

692

3 5 false false Mon Feb 02 00:00:00 -0800 2009 Thu Oct 09 17:09:02 -0700 2008 Mon Feb 02 10:55:07 -0800 2009 more...]]> 5 0 false false Wed Apr 29 00:00:00 -0700 2009 Wed Apr 29 20:28:08 -0700 2009 Wed Apr 29 20:35:52 -0700 2009
Pragmatic Programmer really takes a lot of the important, high-level lessons that can only come from years of experience in the software industry and boils it...more...]]> 5 0 false false Sun Feb 01 00:00:00 -0800 2009 Sun Jan 11 08:38:13 -0800 2009 Sun Feb 01 09:05:20 -0800 2009
It's the kind of thing I unconsciously resist reading because I know of all the guilty feelings it could provoke. Well, one thing I can tell you is that it's not like that at all. Oh actually, yes it is. The first chapter starts off ge...more...]]> 5 0 false false Wed Oct 01 00:00:00 -0700 2008 Thu Sep 17 16:55:45 -0700 2009 Thu Sep 17 16:56:57 -0700 2009 more...]]> 4 0 false false Thu Nov 01 00:00:00 -0700 2007 Mon Jan 07 06:37:16 -0800 2008 Mon Jan 07 07:03:13 -0800 2008
The premise of the book is that software development is a craft. The subtitle of the book is, "From jou...more...]]> 4 0 false false Wed Nov 01 00:00:00 -0800 2006 Thu Oct 18 13:41:14 -0700 2007 Thu Oct 18 13:41:54 -0700 2007
From Amazon.com's review:

Programmers are craftspeople trained to use a certain set of tools (editors, object managers, version trackers) to generate a ce...

more...]]> 4 0 false false Sat Nov 01 00:00:00 -0700 2008 Mon Nov 03 13:50:13 -0800 2008 Mon Nov 03 14:17:54 -0800 2008 more...]]> 3 0 false false Mon Apr 07 14:53:05 -0700 2008 Fri Apr 25 12:49:57 -0700 2008 ...more...]]> 2 1 false false Sun Jan 01 00:00:00 -0800 2006 Fri Jun 05 10:30:53 -0700 2009 Mon Jun 08 01:30:20 -0700 2009 more...]]> 5 0 false false Wed Jan 28 13:25:47 -0800 2009 Wed Jan 28 13:27:26 -0800 2009 more...]]> 3 0 false false Sat Aug 01 00:00:00 -0700 2009 Tue Sep 01 11:32:19 -0700 2009 Tue Sep 01 11:36:19 -0700 2009 more...]]> 2 0 false false Tue Jun 30 05:48:55 -0700 2009 Tue Jun 30 05:50:46 -0700 2009 more...]]> 5 0 false false Wed Jan 01 00:00:00 -0800 2003 Tue Oct 20 20:00:20 -0700 2009 Tue Oct 20 20:05:59 -0700 2009 3 more...]]> 4 0 false false Tue Sep 29 00:00:00 -0700 2009 Tue Sep 29 20:19:07 -0700 2009 Tue Sep 29 20:20:47 -0700 2009 1 5 0 true false Wed Feb 01 00:00:00 -0800 2006 Sat Sep 26 22:38:59 -0700 2009 Sun Sep 27 13:16:57 -0700 2009 2 5 0 false false Thu Nov 05 00:00:00 -0800 2009 Sat Oct 03 06:31:14 -0700 2009 Thu Nov 05 05:53:17 -0800 2009 more...]]> 5 0 true false Wed Jan 28 13:31:39 -0800 2009 Wed Jan 28 13:32:24 -0800 2009 4 0 false false Tue Mar 17 00:00:00 -0700 2009 Sat Mar 28 07:11:49 -0700 2009 Sat Mar 28 08:34:54 -0700 2009
Automate everything.

Don't repeat yourself.]]> 4 0 false false Fri Dec 05 00:00:00 -0800 2008 Fri Nov 07 10:53:04 -0800 2008 Sun Dec 07 17:16:52 -0800 2008
Some of the specific suggestions for implementation are a bit dated (e.g. there are now many unit testing frameworks, CI servers, etc... that have come out since the book was written) but the principles are timeless.

Excelle...more...]]> 3 0 false false Mon Aug 31 01:56:58 -0700 2009 Mon Aug 31 01:58:07 -0700 2009