<?xml version="1.0" encoding="UTF-8"?>
<GoodreadsResponse>
	<Request>
		<authentication>false</authentication>
		    <method><![CDATA[]]></method>
	</Request>
	
<book>
  <id>86379</id>
  <title><![CDATA[Perl Best Practices]]></title>
  <isbn><![CDATA[0596001738]]></isbn>
  <isbn13><![CDATA[9780596001735]]></isbn13>
  <image_url>http://photo.goodreads.com/books/1171067732m/86379.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1171067732s/86379.jpg</small_image_url>
  <description><![CDATA[&lt;DIV&gt;Many programmers code by instinct, relying on convenient habits or a &quot;style&quot; they picked up early on. They aren't conscious of all the choices they make, like how they format their source, the names they use for variables, or the kinds of loops they use. They're focused entirely on problems they're solving, solutions they're creating, and algorithms they're implementing. So they write code in the way that seems natural, that happens intuitively, and that feels good. <p> But if you're serious about your profession, intuition isn't enough. &quot;Perl Best Practices&quot; author Damian Conway explains that rules, conventions, standards, and practices not only help programmers communicate and coordinate with one another, they also provide a reliable framework for thinking about problems, and a common language for expressing solutions. This is especially critical in Perl, because the language is designed to offer many ways to accomplish the same task, and consequently it supports many incompatible dialects. <p> With a good dose of Aussie humor, Dr. Conway (familiar to many in the Perl community) offers 256 guidelines on the art of coding to help you write better Perl code--in fact, the best Perl code you possibly can. The guidelines cover code layout, naming conventions, choice of data and control structures, program decomposition, interface design and implementation, modularity, object orientation, error handling, testing, and debugging. <p> They're designed to work together to produce code that is clear, robust, efficient, maintainable, and concise, but Dr. Conway doesn't pretend that this is the one true universal and unequivocal set of best practices. Instead, &quot;Perl Best Practices&quot; offerscoherent and widely applicable suggestions based on real-world experience of how code is actually written, rather than on someone's ivory-tower theories on how<p> software ought to be created. <p> Most of all, &quot;Perl Best Practices&quot; offers guidelines that actually work, and that many developers around the world are already using. Much like Perl itself, these guidelines are about helping you to get your job done, without getting in the way. <p> Praise for &quot;Perl Best Practices&quot; from Perl community members: <p> &quot;As a manager of a large Perl project, I'd ensure that every member of my team has a copy of &quot;Perl Best Practices&quot; on their desk, and use it as the basis for an in-house style guide.&quot; <p> -- Randal Schwartz <p> &quot;There are no more excuses for writing bad Perl programs. All levels of Perl programmer will be more productive after reading this book.&quot; <p> -- Peter Scott <p> &quot;&quot;Perl Best Practices&quot; will be the next big important book in the evolution of Perl. The ideas and practices Damian lays down will help bring Perl out from under the embarrassing heading of &quot;scripting languages.&quot; Many of us have known Perl is a real programming language, worthy of all the tasks normally delegated to Java and C++. With Perl Best Practices, Damian shows specifically how and why, so everyone else can see, too.&quot; <p> -- Andy Lester <p> &quot;Damian's done what many thought impossible: show how to build large, maintainable Perl applications, while still letting Perl be the powerful, expressive language that programmers have loved for years.&quot; <p> -- Bill Odom <p> &quot;Finally, a means to bring lasting order to the process and product of real Perl development teams.&quot; <p> -- Andrew Sundstrom <p>&quot;&quot;Perl Best Practices&quot; provides a valuable education in how to write robust, maintainable Perl, and is a definitive citation source when coaching other programmers.&quot; <p> -- Bennett Todd <p> &quot;I've been teaching Perl for years, and find the same question keeps being asked: Where can I find a reference for writing reusable, maintainable Perl code? Finally I have a decent answer.&quot; <p> -- Paul Fenwick &lt;p&gt; &quot;At last a well researched, well thought-out, comprehensive guide to Perl style. Instead of each of us developing our own, we can learn good practices from one of Perl's most prolific and experienced authors. I recommend this book to anyone who prefers getting on with the job rather than going back and fixing errors caused by syntax and poor style issues.&quot; &lt;p&gt; -- Jacinta Richardson &lt;p&gt; &quot;If you care about programming in any language read this book. Even if you don't intend to follow all of the practices, thinking through your style will improve it.&quot;&lt;p&gt; -- Steven Lembark &lt;p&gt; &quot;The Perl community's best author is back with another outstanding book. There has never been a comprehensive reference on high quality Perl coding and style until &quot;Perl Best Practices,&quot; This book fills a large gap in every Perl bookshelf.&quot; &lt;p&gt; -- Uri Guttman</p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p>]]></description>
  <work>
  <best_book_id type="integer">86379</best_book_id>
  <books_count type="integer">1</books_count>
  <desc_user_id type="integer" nil="true"></desc_user_id>
  <id type="integer">83362</id>
  <media_type nil="true"></media_type>
  <original_language_id type="integer" nil="true"></original_language_id>
  <original_publication_day type="integer">12</original_publication_day>
  <original_publication_month type="integer">7</original_publication_month>
  <original_publication_year type="integer">2005</original_publication_year>
  <original_title>Perl Best Practices</original_title>
  <rating_dist>total:41|5:20|4:15|3:6|2:0|1:0|</rating_dist>
  <ratings_count type="integer">41</ratings_count>
  <ratings_sum type="integer">178</ratings_sum>
  <reviews_count type="integer">62</reviews_count>
  <text_reviews_count type="integer">4</text_reviews_count>
</work>

  <average_rating><![CDATA[4.34]]></average_rating>
  <ratings_count><![CDATA[41]]></ratings_count>
  <text_reviews_count><![CDATA[4]]></text_reviews_count>
  
  <url><![CDATA[http://www.goodreads.com/book/show/86379.Perl_Best_Practices]]></url>
  <link><![CDATA[http://www.goodreads.com/book/show/86379.Perl_Best_Practices]]></link>
  <authors>
    <author>
    <id>49468</id>
        <name><![CDATA[Damian Conway]]></name>
    <image_url><![CDATA[http://www.goodreads.com/images/nophoto/nophoto-U-200x266.jpg]]></image_url>
    <small_image_url><![CDATA[http://www.goodreads.com/images/nophoto/nophoto-U-50x66.jpg]]></small_image_url>
    <link><![CDATA[http://www.goodreads.com/author/show/49468.Damian_Conway]]></link>
    <average_rating>4.34</average_rating>
    <ratings_count>61</ratings_count>
    <text_reviews_count>9</text_reviews_count>
  </author>
  </authors>
    <reviews start="1" end="20" total="62">
      <review>
  <id>12034971</id>
    <user>
    <id>746630</id>
    <name><![CDATA[Apple84]]></name>
    <location><![CDATA[Glen Carbon, IL]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/746630-apple84-wylie]]></link>
    <image_url><![CDATA[http://photo.goodreads.com/users/1199744051p3/746630.jpg]]></image_url>
    <small_image_url><![CDATA[http://photo.goodreads.com/users/1199744051p2/746630.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">86379</id>
  <isbn>0596001738</isbn>
  <isbn13>9780596001735</isbn13>
  <text_reviews_count type="integer">4</text_reviews_count>
  <title>
    <![CDATA[Perl Best Practices]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1171067732m/86379.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1171067732s/86379.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/86379.Perl_Best_Practices</link>
  <average_rating>4.34</average_rating>
  <ratings_count>41</ratings_count>
  <description>
    <![CDATA[&lt;DIV&gt;Many programmers code by instinct, relying on convenient habits or a &quot;style&quot; they picked up early on. They aren't conscious of all the choices they make, like how they format their source, the names they use for variables, or the kinds of loops they use. They're focused entirely on problems they're solving, solutions they're creating, and algorithms they're implementing. So they write code in the way that seems natural, that happens intuitively, and that feels good. <p> But if you're serious about your profession, intuition isn't enough. &quot;Perl Best Practices&quot; author Damian Conway explains that rules, conventions, standards, and practices not only help programmers communicate and coordinate with one another, they also provide a reliable framework for thinking about problems, and a common language for expressing solutions. This is especially critical in Perl, because the language is designed to offer many ways to accomplish the same task, and consequently it supports many incompatible dialects. <p> With a good dose of Aussie humor, Dr. Conway (familiar to many in the Perl community) offers 256 guidelines on the art of coding to help you write better Perl code--in fact, the best Perl code you possibly can. The guidelines cover code layout, naming conventions, choice of data and control structures, program decomposition, interface design and implementation, modularity, object orientation, error handling, testing, and debugging. <p> They're designed to work together to produce code that is clear, robust, efficient, maintainable, and concise, but Dr. Conway doesn't pretend that this is the one true universal and unequivocal set of best practices. Instead, &quot;Perl Best Practices&quot; offerscoherent and widely applicable suggestions based on real-world experience of how code is actually written, rather than on someone's ivory-tower theories on how<p> software ought to be created. <p> Most of all, &quot;Perl Best Practices&quot; offers guidelines that actually work, and that many developers around the world are already using. Much like Perl itself, these guidelines are about helping you to get your job done, without getting in the way. <p> Praise for &quot;Perl Best Practices&quot; from Perl community members: <p> &quot;As a manager of a large Perl project, I'd ensure that every member of my team has a copy of &quot;Perl Best Practices&quot; on their desk, and use it as the basis for an in-house style guide.&quot; <p> -- Randal Schwartz <p> &quot;There are no more excuses for writing bad Perl programs. All levels of Perl programmer will be more productive after reading this book.&quot; <p> -- Peter Scott <p> &quot;&quot;Perl Best Practices&quot; will be the next big important book in the evolution of Perl. The ideas and practices Damian lays down will help bring Perl out from under the embarrassing heading of &quot;scripting languages.&quot; Many of us have known Perl is a real programming language, worthy of all the tasks normally delegated to Java and C++. With Perl Best Practices, Damian shows specifically how and why, so everyone else can see, too.&quot; <p> -- Andy Lester <p> &quot;Damian's done what many thought impossible: show how to build large, maintainable Perl applications, while still letting Perl be the powerful, expressive language that programmers have loved for years.&quot; <p> -- Bill Odom <p> &quot;Finally, a means to bring lasting order to the process and product of real Perl development teams.&quot; <p> -- Andrew Sundstrom <p>&quot;&quot;Perl Best Practices&quot; provides a valuable education in how to write robust, maintainable Perl, and is a definitive citation source when coaching other programmers.&quot; <p> -- Bennett Todd <p> &quot;I've been teaching Perl for years, and find the same question keeps being asked: Where can I find a reference for writing reusable, maintainable Perl code? Finally I have a decent answer.&quot; <p> -- Paul Fenwick &lt;p&gt; &quot;At last a well researched, well thought-out, comprehensive guide to Perl style. Instead of each of us developing our own, we can learn good practices from one of Perl's most prolific and experienced authors. I recommend this book to anyone who prefers getting on with the job rather than going back and fixing errors caused by syntax and poor style issues.&quot; &lt;p&gt; -- Jacinta Richardson &lt;p&gt; &quot;If you care about programming in any language read this book. Even if you don't intend to follow all of the practices, thinking through your style will improve it.&quot;&lt;p&gt; -- Steven Lembark &lt;p&gt; &quot;The Perl community's best author is back with another outstanding book. There has never been a comprehensive reference on high quality Perl coding and style until &quot;Perl Best Practices,&quot; This book fills a large gap in every Perl bookshelf.&quot; &lt;p&gt; -- Uri Guttman</p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p>]]>
  </description>
  <published>2005</published>
</book>

    <rating>4</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
        <shelf name="read" />
            <shelf name="technical" />
      </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Tue Jan 08 21:31:16 -0800 2008</date_added>
  <date_updated>Wed Jan 09 12:35:30 -0800 2008</date_updated>
  <read_count></read_count>
    <body><![CDATA[Hardcore Perl programmers tend to be an audacious bunch. Damian Conway--a superstar and innovator among Perl coders--takes on  the audacious task of calling to arms his fellow programmers with a battle cry of &quot;We can do better!&quot;. Perl is a complex and highly flexible language that eschews ...<a href="http://www.goodreads.com/review/show/12034971">more...</a>]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/12034971]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/12034971]]></link>
</review>
      <review>
  <id>63621991</id>
    <user>
    <id>1377371</id>
    <name><![CDATA[John]]></name>
    <location><![CDATA[Emeryville, CA]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/1377371-john-landis]]></link>
    <image_url><![CDATA[http://photo.goodreads.com/users/1247593678p3/1377371.jpg]]></image_url>
    <small_image_url><![CDATA[http://photo.goodreads.com/users/1247593678p2/1377371.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">86379</id>
  <isbn>0596001738</isbn>
  <isbn13>9780596001735</isbn13>
  <text_reviews_count type="integer">4</text_reviews_count>
  <title>
    <![CDATA[Perl Best Practices]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1171067732m/86379.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1171067732s/86379.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/86379.Perl_Best_Practices</link>
  <average_rating>4.34</average_rating>
  <ratings_count>41</ratings_count>
  <description>
    <![CDATA[&lt;DIV&gt;Many programmers code by instinct, relying on convenient habits or a &quot;style&quot; they picked up early on. They aren't conscious of all the choices they make, like how they format their source, the names they use for variables, or the kinds of loops they use. They're focused entirely on problems they're solving, solutions they're creating, and algorithms they're implementing. So they write code in the way that seems natural, that happens intuitively, and that feels good. <p> But if you're serious about your profession, intuition isn't enough. &quot;Perl Best Practices&quot; author Damian Conway explains that rules, conventions, standards, and practices not only help programmers communicate and coordinate with one another, they also provide a reliable framework for thinking about problems, and a common language for expressing solutions. This is especially critical in Perl, because the language is designed to offer many ways to accomplish the same task, and consequently it supports many incompatible dialects. <p> With a good dose of Aussie humor, Dr. Conway (familiar to many in the Perl community) offers 256 guidelines on the art of coding to help you write better Perl code--in fact, the best Perl code you possibly can. The guidelines cover code layout, naming conventions, choice of data and control structures, program decomposition, interface design and implementation, modularity, object orientation, error handling, testing, and debugging. <p> They're designed to work together to produce code that is clear, robust, efficient, maintainable, and concise, but Dr. Conway doesn't pretend that this is the one true universal and unequivocal set of best practices. Instead, &quot;Perl Best Practices&quot; offerscoherent and widely applicable suggestions based on real-world experience of how code is actually written, rather than on someone's ivory-tower theories on how<p> software ought to be created. <p> Most of all, &quot;Perl Best Practices&quot; offers guidelines that actually work, and that many developers around the world are already using. Much like Perl itself, these guidelines are about helping you to get your job done, without getting in the way. <p> Praise for &quot;Perl Best Practices&quot; from Perl community members: <p> &quot;As a manager of a large Perl project, I'd ensure that every member of my team has a copy of &quot;Perl Best Practices&quot; on their desk, and use it as the basis for an in-house style guide.&quot; <p> -- Randal Schwartz <p> &quot;There are no more excuses for writing bad Perl programs. All levels of Perl programmer will be more productive after reading this book.&quot; <p> -- Peter Scott <p> &quot;&quot;Perl Best Practices&quot; will be the next big important book in the evolution of Perl. The ideas and practices Damian lays down will help bring Perl out from under the embarrassing heading of &quot;scripting languages.&quot; Many of us have known Perl is a real programming language, worthy of all the tasks normally delegated to Java and C++. With Perl Best Practices, Damian shows specifically how and why, so everyone else can see, too.&quot; <p> -- Andy Lester <p> &quot;Damian's done what many thought impossible: show how to build large, maintainable Perl applications, while still letting Perl be the powerful, expressive language that programmers have loved for years.&quot; <p> -- Bill Odom <p> &quot;Finally, a means to bring lasting order to the process and product of real Perl development teams.&quot; <p> -- Andrew Sundstrom <p>&quot;&quot;Perl Best Practices&quot; provides a valuable education in how to write robust, maintainable Perl, and is a definitive citation source when coaching other programmers.&quot; <p> -- Bennett Todd <p> &quot;I've been teaching Perl for years, and find the same question keeps being asked: Where can I find a reference for writing reusable, maintainable Perl code? Finally I have a decent answer.&quot; <p> -- Paul Fenwick &lt;p&gt; &quot;At last a well researched, well thought-out, comprehensive guide to Perl style. Instead of each of us developing our own, we can learn good practices from one of Perl's most prolific and experienced authors. I recommend this book to anyone who prefers getting on with the job rather than going back and fixing errors caused by syntax and poor style issues.&quot; &lt;p&gt; -- Jacinta Richardson &lt;p&gt; &quot;If you care about programming in any language read this book. Even if you don't intend to follow all of the practices, thinking through your style will improve it.&quot;&lt;p&gt; -- Steven Lembark &lt;p&gt; &quot;The Perl community's best author is back with another outstanding book. There has never been a comprehensive reference on high quality Perl coding and style until &quot;Perl Best Practices,&quot; This book fills a large gap in every Perl bookshelf.&quot; &lt;p&gt; -- Uri Guttman</p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p>]]>
  </description>
  <published>2005</published>
</book>

    <rating>5</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
        <shelf name="read" />
            <shelf name="computers" />
        <shelf name="nonfiction" />
        <shelf name="owned" />
      </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Wed Jul 15 13:20:57 -0700 2009</date_added>
  <date_updated>Wed Jul 15 13:23:24 -0700 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[This book perfectly describes the use of perl in concise and clear terms.  It is the best such description of a language I have seen.]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/63621991]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/63621991]]></link>
</review>
      <review>
  <id>16692850</id>
    <user>
    <id>702622</id>
    <name><![CDATA[Joshua]]></name>
    <location><![CDATA[Santa Monica, CA]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/702622-joshua]]></link>
    <image_url><![CDATA[http://photo.goodreads.com/users/1199076200p3/702622.jpg]]></image_url>
    <small_image_url><![CDATA[http://photo.goodreads.com/users/1199076200p2/702622.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">86379</id>
  <isbn>0596001738</isbn>
  <isbn13>9780596001735</isbn13>
  <text_reviews_count type="integer">4</text_reviews_count>
  <title>
    <![CDATA[Perl Best Practices]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1171067732m/86379.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1171067732s/86379.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/86379.Perl_Best_Practices</link>
  <average_rating>4.34</average_rating>
  <ratings_count>41</ratings_count>
  <description>
    <![CDATA[&lt;DIV&gt;Many programmers code by instinct, relying on convenient habits or a &quot;style&quot; they picked up early on. They aren't conscious of all the choices they make, like how they format their source, the names they use for variables, or the kinds of loops they use. They're focused entirely on problems they're solving, solutions they're creating, and algorithms they're implementing. So they write code in the way that seems natural, that happens intuitively, and that feels good. <p> But if you're serious about your profession, intuition isn't enough. &quot;Perl Best Practices&quot; author Damian Conway explains that rules, conventions, standards, and practices not only help programmers communicate and coordinate with one another, they also provide a reliable framework for thinking about problems, and a common language for expressing solutions. This is especially critical in Perl, because the language is designed to offer many ways to accomplish the same task, and consequently it supports many incompatible dialects. <p> With a good dose of Aussie humor, Dr. Conway (familiar to many in the Perl community) offers 256 guidelines on the art of coding to help you write better Perl code--in fact, the best Perl code you possibly can. The guidelines cover code layout, naming conventions, choice of data and control structures, program decomposition, interface design and implementation, modularity, object orientation, error handling, testing, and debugging. <p> They're designed to work together to produce code that is clear, robust, efficient, maintainable, and concise, but Dr. Conway doesn't pretend that this is the one true universal and unequivocal set of best practices. Instead, &quot;Perl Best Practices&quot; offerscoherent and widely applicable suggestions based on real-world experience of how code is actually written, rather than on someone's ivory-tower theories on how<p> software ought to be created. <p> Most of all, &quot;Perl Best Practices&quot; offers guidelines that actually work, and that many developers around the world are already using. Much like Perl itself, these guidelines are about helping you to get your job done, without getting in the way. <p> Praise for &quot;Perl Best Practices&quot; from Perl community members: <p> &quot;As a manager of a large Perl project, I'd ensure that every member of my team has a copy of &quot;Perl Best Practices&quot; on their desk, and use it as the basis for an in-house style guide.&quot; <p> -- Randal Schwartz <p> &quot;There are no more excuses for writing bad Perl programs. All levels of Perl programmer will be more productive after reading this book.&quot; <p> -- Peter Scott <p> &quot;&quot;Perl Best Practices&quot; will be the next big important book in the evolution of Perl. The ideas and practices Damian lays down will help bring Perl out from under the embarrassing heading of &quot;scripting languages.&quot; Many of us have known Perl is a real programming language, worthy of all the tasks normally delegated to Java and C++. With Perl Best Practices, Damian shows specifically how and why, so everyone else can see, too.&quot; <p> -- Andy Lester <p> &quot;Damian's done what many thought impossible: show how to build large, maintainable Perl applications, while still letting Perl be the powerful, expressive language that programmers have loved for years.&quot; <p> -- Bill Odom <p> &quot;Finally, a means to bring lasting order to the process and product of real Perl development teams.&quot; <p> -- Andrew Sundstrom <p>&quot;&quot;Perl Best Practices&quot; provides a valuable education in how to write robust, maintainable Perl, and is a definitive citation source when coaching other programmers.&quot; <p> -- Bennett Todd <p> &quot;I've been teaching Perl for years, and find the same question keeps being asked: Where can I find a reference for writing reusable, maintainable Perl code? Finally I have a decent answer.&quot; <p> -- Paul Fenwick &lt;p&gt; &quot;At last a well researched, well thought-out, comprehensive guide to Perl style. Instead of each of us developing our own, we can learn good practices from one of Perl's most prolific and experienced authors. I recommend this book to anyone who prefers getting on with the job rather than going back and fixing errors caused by syntax and poor style issues.&quot; &lt;p&gt; -- Jacinta Richardson &lt;p&gt; &quot;If you care about programming in any language read this book. Even if you don't intend to follow all of the practices, thinking through your style will improve it.&quot;&lt;p&gt; -- Steven Lembark &lt;p&gt; &quot;The Perl community's best author is back with another outstanding book. There has never been a comprehensive reference on high quality Perl coding and style until &quot;Perl Best Practices,&quot; This book fills a large gap in every Perl bookshelf.&quot; &lt;p&gt; -- Uri Guttman</p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p>]]>
  </description>
  <published>2005</published>
</book>

    <rating>5</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
        <shelf name="read" />
          </shelves>
  <recommended_for><![CDATA[Any perl programmer of any level]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at>Sat Apr 07 00:00:00 -0700 2007</read_at>
  <date_added>Fri Feb 29 09:30:28 -0800 2008</date_added>
  <date_updated>Fri Feb 29 09:34:13 -0800 2008</date_updated>
  <read_count></read_count>
    <body><![CDATA[This is a fantastic book that helps address many of the things that are negative about working with Perl in teams. Even through just beginning to standardize on a few of these principles, our group is sharing more code and spending less time discussing pros and cons of various approaches. In additio...<a href="http://www.goodreads.com/review/show/16692850">more...</a>]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/16692850]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/16692850]]></link>
</review>
      <review>
  <id>21256049</id>
    <user>
    <id>796692</id>
    <name><![CDATA[Chris]]></name>
    <location><![CDATA[Hamptonville, NC]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/796692-chris]]></link>
    <image_url><![CDATA[http://www.goodreads.com/images/nophoto-U-111x148.jpg]]></image_url>
    <small_image_url><![CDATA[http://www.goodreads.com/images/nophoto-U-50x66.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">86379</id>
  <isbn>0596001738</isbn>
  <isbn13>9780596001735</isbn13>
  <text_reviews_count type="integer">4</text_reviews_count>
  <title>
    <![CDATA[Perl Best Practices]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1171067732m/86379.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1171067732s/86379.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/86379.Perl_Best_Practices</link>
  <average_rating>4.34</average_rating>
  <ratings_count>41</ratings_count>
  <description>
    <![CDATA[&lt;DIV&gt;Many programmers code by instinct, relying on convenient habits or a &quot;style&quot; they picked up early on. They aren't conscious of all the choices they make, like how they format their source, the names they use for variables, or the kinds of loops they use. They're focused entirely on problems they're solving, solutions they're creating, and algorithms they're implementing. So they write code in the way that seems natural, that happens intuitively, and that feels good. <p> But if you're serious about your profession, intuition isn't enough. &quot;Perl Best Practices&quot; author Damian Conway explains that rules, conventions, standards, and practices not only help programmers communicate and coordinate with one another, they also provide a reliable framework for thinking about problems, and a common language for expressing solutions. This is especially critical in Perl, because the language is designed to offer many ways to accomplish the same task, and consequently it supports many incompatible dialects. <p> With a good dose of Aussie humor, Dr. Conway (familiar to many in the Perl community) offers 256 guidelines on the art of coding to help you write better Perl code--in fact, the best Perl code you possibly can. The guidelines cover code layout, naming conventions, choice of data and control structures, program decomposition, interface design and implementation, modularity, object orientation, error handling, testing, and debugging. <p> They're designed to work together to produce code that is clear, robust, efficient, maintainable, and concise, but Dr. Conway doesn't pretend that this is the one true universal and unequivocal set of best practices. Instead, &quot;Perl Best Practices&quot; offerscoherent and widely applicable suggestions based on real-world experience of how code is actually written, rather than on someone's ivory-tower theories on how<p> software ought to be created. <p> Most of all, &quot;Perl Best Practices&quot; offers guidelines that actually work, and that many developers around the world are already using. Much like Perl itself, these guidelines are about helping you to get your job done, without getting in the way. <p> Praise for &quot;Perl Best Practices&quot; from Perl community members: <p> &quot;As a manager of a large Perl project, I'd ensure that every member of my team has a copy of &quot;Perl Best Practices&quot; on their desk, and use it as the basis for an in-house style guide.&quot; <p> -- Randal Schwartz <p> &quot;There are no more excuses for writing bad Perl programs. All levels of Perl programmer will be more productive after reading this book.&quot; <p> -- Peter Scott <p> &quot;&quot;Perl Best Practices&quot; will be the next big important book in the evolution of Perl. The ideas and practices Damian lays down will help bring Perl out from under the embarrassing heading of &quot;scripting languages.&quot; Many of us have known Perl is a real programming language, worthy of all the tasks normally delegated to Java and C++. With Perl Best Practices, Damian shows specifically how and why, so everyone else can see, too.&quot; <p> -- Andy Lester <p> &quot;Damian's done what many thought impossible: show how to build large, maintainable Perl applications, while still letting Perl be the powerful, expressive language that programmers have loved for years.&quot; <p> -- Bill Odom <p> &quot;Finally, a means to bring lasting order to the process and product of real Perl development teams.&quot; <p> -- Andrew Sundstrom <p>&quot;&quot;Perl Best Practices&quot; provides a valuable education in how to write robust, maintainable Perl, and is a definitive citation source when coaching other programmers.&quot; <p> -- Bennett Todd <p> &quot;I've been teaching Perl for years, and find the same question keeps being asked: Where can I find a reference for writing reusable, maintainable Perl code? Finally I have a decent answer.&quot; <p> -- Paul Fenwick &lt;p&gt; &quot;At last a well researched, well thought-out, comprehensive guide to Perl style. Instead of each of us developing our own, we can learn good practices from one of Perl's most prolific and experienced authors. I recommend this book to anyone who prefers getting on with the job rather than going back and fixing errors caused by syntax and poor style issues.&quot; &lt;p&gt; -- Jacinta Richardson &lt;p&gt; &quot;If you care about programming in any language read this book. Even if you don't intend to follow all of the practices, thinking through your style will improve it.&quot;&lt;p&gt; -- Steven Lembark &lt;p&gt; &quot;The Perl community's best author is back with another outstanding book. There has never been a comprehensive reference on high quality Perl coding and style until &quot;Perl Best Practices,&quot; This book fills a large gap in every Perl bookshelf.&quot; &lt;p&gt; -- Uri Guttman</p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p>]]>
  </description>
  <published>2005</published>
</book>

    <rating>0</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
        <shelf name="read" />
            <shelf name="perl" />
      </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Tue Apr 29 10:58:35 -0700 2008</date_added>
  <date_updated>Tue Apr 29 10:59:35 -0700 2008</date_updated>
  <read_count></read_count>
    <body><![CDATA[Probably the most useful Perl book out there.  Not only educational, but amazingly helpful in dealing with Perl Written By Other People.]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/21256049]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/21256049]]></link>
</review>
      <review>
  <id>82072825</id>
    <user>
    <id>1445063</id>
    <name><![CDATA[Kaiser]]></name>
    <location><![CDATA[Shahrud, Iran, Islamic Republic of]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/1445063-kaiser]]></link>
    <image_url><![CDATA[http://photo.goodreads.com/users/1260226470p3/1445063.jpg]]></image_url>
    <small_image_url><![CDATA[http://photo.goodreads.com/users/1260226470p2/1445063.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">86379</id>
  <isbn>0596001738</isbn>
  <isbn13>9780596001735</isbn13>
  <text_reviews_count type="integer">4</text_reviews_count>
  <title>
    <![CDATA[Perl Best Practices]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1171067732m/86379.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1171067732s/86379.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/86379.Perl_Best_Practices</link>
  <average_rating>4.34</average_rating>
  <ratings_count>41</ratings_count>
  <description>
    <![CDATA[&lt;DIV&gt;Many programmers code by instinct, relying on convenient habits or a &quot;style&quot; they picked up early on. They aren't conscious of all the choices they make, like how they format their source, the names they use for variables, or the kinds of loops they use. They're focused entirely on problems they're solving, solutions they're creating, and algorithms they're implementing. So they write code in the way that seems natural, that happens intuitively, and that feels good. <p> But if you're serious about your profession, intuition isn't enough. &quot;Perl Best Practices&quot; author Damian Conway explains that rules, conventions, standards, and practices not only help programmers communicate and coordinate with one another, they also provide a reliable framework for thinking about problems, and a common language for expressing solutions. This is especially critical in Perl, because the language is designed to offer many ways to accomplish the same task, and consequently it supports many incompatible dialects. <p> With a good dose of Aussie humor, Dr. Conway (familiar to many in the Perl community) offers 256 guidelines on the art of coding to help you write better Perl code--in fact, the best Perl code you possibly can. The guidelines cover code layout, naming conventions, choice of data and control structures, program decomposition, interface design and implementation, modularity, object orientation, error handling, testing, and debugging. <p> They're designed to work together to produce code that is clear, robust, efficient, maintainable, and concise, but Dr. Conway doesn't pretend that this is the one true universal and unequivocal set of best practices. Instead, &quot;Perl Best Practices&quot; offerscoherent and widely applicable suggestions based on real-world experience of how code is actually written, rather than on someone's ivory-tower theories on how<p> software ought to be created. <p> Most of all, &quot;Perl Best Practices&quot; offers guidelines that actually work, and that many developers around the world are already using. Much like Perl itself, these guidelines are about helping you to get your job done, without getting in the way. <p> Praise for &quot;Perl Best Practices&quot; from Perl community members: <p> &quot;As a manager of a large Perl project, I'd ensure that every member of my team has a copy of &quot;Perl Best Practices&quot; on their desk, and use it as the basis for an in-house style guide.&quot; <p> -- Randal Schwartz <p> &quot;There are no more excuses for writing bad Perl programs. All levels of Perl programmer will be more productive after reading this book.&quot; <p> -- Peter Scott <p> &quot;&quot;Perl Best Practices&quot; will be the next big important book in the evolution of Perl. The ideas and practices Damian lays down will help bring Perl out from under the embarrassing heading of &quot;scripting languages.&quot; Many of us have known Perl is a real programming language, worthy of all the tasks normally delegated to Java and C++. With Perl Best Practices, Damian shows specifically how and why, so everyone else can see, too.&quot; <p> -- Andy Lester <p> &quot;Damian's done what many thought impossible: show how to build large, maintainable Perl applications, while still letting Perl be the powerful, expressive language that programmers have loved for years.&quot; <p> -- Bill Odom <p> &quot;Finally, a means to bring lasting order to the process and product of real Perl development teams.&quot; <p> -- Andrew Sundstrom <p>&quot;&quot;Perl Best Practices&quot; provides a valuable education in how to write robust, maintainable Perl, and is a definitive citation source when coaching other programmers.&quot; <p> -- Bennett Todd <p> &quot;I've been teaching Perl for years, and find the same question keeps being asked: Where can I find a reference for writing reusable, maintainable Perl code? Finally I have a decent answer.&quot; <p> -- Paul Fenwick &lt;p&gt; &quot;At last a well researched, well thought-out, comprehensive guide to Perl style. Instead of each of us developing our own, we can learn good practices from one of Perl's most prolific and experienced authors. I recommend this book to anyone who prefers getting on with the job rather than going back and fixing errors caused by syntax and poor style issues.&quot; &lt;p&gt; -- Jacinta Richardson &lt;p&gt; &quot;If you care about programming in any language read this book. Even if you don't intend to follow all of the practices, thinking through your style will improve it.&quot;&lt;p&gt; -- Steven Lembark &lt;p&gt; &quot;The Perl community's best author is back with another outstanding book. There has never been a comprehensive reference on high quality Perl coding and style until &quot;Perl Best Practices,&quot; This book fills a large gap in every Perl bookshelf.&quot; &lt;p&gt; -- Uri Guttman</p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p>]]>
  </description>
  <published>2005</published>
</book>

    <rating>3</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
        <shelf name="read" />
          </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Sat Dec 26 07:59:07 -0800 2009</date_added>
  <date_updated>Sat Dec 26 07:59:07 -0800 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/82072825]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/82072825]]></link>
</review>
      <review>
  <id>78616682</id>
    <user>
    <id>145699</id>
    <name><![CDATA[Mary]]></name>
    <location><![CDATA[Somerville, MA]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/145699-mary]]></link>
    <image_url><![CDATA[http://photo.goodreads.com/users/1248011479p3/145699.jpg]]></image_url>
    <small_image_url><![CDATA[http://photo.goodreads.com/users/1248011479p2/145699.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">86379</id>
  <isbn>0596001738</isbn>
  <isbn13>9780596001735</isbn13>
  <text_reviews_count type="integer">4</text_reviews_count>
  <title>
    <![CDATA[Perl Best Practices]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1171067732m/86379.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1171067732s/86379.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/86379.Perl_Best_Practices</link>
  <average_rating>4.34</average_rating>
  <ratings_count>41</ratings_count>
  <description>
    <![CDATA[&lt;DIV&gt;Many programmers code by instinct, relying on convenient habits or a &quot;style&quot; they picked up early on. They aren't conscious of all the choices they make, like how they format their source, the names they use for variables, or the kinds of loops they use. They're focused entirely on problems they're solving, solutions they're creating, and algorithms they're implementing. So they write code in the way that seems natural, that happens intuitively, and that feels good. <p> But if you're serious about your profession, intuition isn't enough. &quot;Perl Best Practices&quot; author Damian Conway explains that rules, conventions, standards, and practices not only help programmers communicate and coordinate with one another, they also provide a reliable framework for thinking about problems, and a common language for expressing solutions. This is especially critical in Perl, because the language is designed to offer many ways to accomplish the same task, and consequently it supports many incompatible dialects. <p> With a good dose of Aussie humor, Dr. Conway (familiar to many in the Perl community) offers 256 guidelines on the art of coding to help you write better Perl code--in fact, the best Perl code you possibly can. The guidelines cover code layout, naming conventions, choice of data and control structures, program decomposition, interface design and implementation, modularity, object orientation, error handling, testing, and debugging. <p> They're designed to work together to produce code that is clear, robust, efficient, maintainable, and concise, but Dr. Conway doesn't pretend that this is the one true universal and unequivocal set of best practices. Instead, &quot;Perl Best Practices&quot; offerscoherent and widely applicable suggestions based on real-world experience of how code is actually written, rather than on someone's ivory-tower theories on how<p> software ought to be created. <p> Most of all, &quot;Perl Best Practices&quot; offers guidelines that actually work, and that many developers around the world are already using. Much like Perl itself, these guidelines are about helping you to get your job done, without getting in the way. <p> Praise for &quot;Perl Best Practices&quot; from Perl community members: <p> &quot;As a manager of a large Perl project, I'd ensure that every member of my team has a copy of &quot;Perl Best Practices&quot; on their desk, and use it as the basis for an in-house style guide.&quot; <p> -- Randal Schwartz <p> &quot;There are no more excuses for writing bad Perl programs. All levels of Perl programmer will be more productive after reading this book.&quot; <p> -- Peter Scott <p> &quot;&quot;Perl Best Practices&quot; will be the next big important book in the evolution of Perl. The ideas and practices Damian lays down will help bring Perl out from under the embarrassing heading of &quot;scripting languages.&quot; Many of us have known Perl is a real programming language, worthy of all the tasks normally delegated to Java and C++. With Perl Best Practices, Damian shows specifically how and why, so everyone else can see, too.&quot; <p> -- Andy Lester <p> &quot;Damian's done what many thought impossible: show how to build large, maintainable Perl applications, while still letting Perl be the powerful, expressive language that programmers have loved for years.&quot; <p> -- Bill Odom <p> &quot;Finally, a means to bring lasting order to the process and product of real Perl development teams.&quot; <p> -- Andrew Sundstrom <p>&quot;&quot;Perl Best Practices&quot; provides a valuable education in how to write robust, maintainable Perl, and is a definitive citation source when coaching other programmers.&quot; <p> -- Bennett Todd <p> &quot;I've been teaching Perl for years, and find the same question keeps being asked: Where can I find a reference for writing reusable, maintainable Perl code? Finally I have a decent answer.&quot; <p> -- Paul Fenwick &lt;p&gt; &quot;At last a well researched, well thought-out, comprehensive guide to Perl style. Instead of each of us developing our own, we can learn good practices from one of Perl's most prolific and experienced authors. I recommend this book to anyone who prefers getting on with the job rather than going back and fixing errors caused by syntax and poor style issues.&quot; &lt;p&gt; -- Jacinta Richardson &lt;p&gt; &quot;If you care about programming in any language read this book. Even if you don't intend to follow all of the practices, thinking through your style will improve it.&quot;&lt;p&gt; -- Steven Lembark &lt;p&gt; &quot;The Perl community's best author is back with another outstanding book. There has never been a comprehensive reference on high quality Perl coding and style until &quot;Perl Best Practices,&quot; This book fills a large gap in every Perl bookshelf.&quot; &lt;p&gt; -- Uri Guttman</p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p>]]>
  </description>
  <published>2005</published>
</book>

    <rating>4</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
        <shelf name="read" />
          </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at>Mon Nov 23 00:00:00 -0800 2009</read_at>
  <date_added>Sun Nov 22 06:15:40 -0800 2009</date_added>
  <date_updated>Mon Nov 23 18:18:57 -0800 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/78616682]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/78616682]]></link>
</review>
      <review>
  <id>77128364</id>
    <user>
    <id>2922139</id>
    <name><![CDATA[LeSpocky]]></name>
    <location><![CDATA[Trondheim, Norway]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/2922139-lespocky]]></link>
    <image_url><![CDATA[http://photo.goodreads.com/users/1257704007p3/2922139.jpg]]></image_url>
    <small_image_url><![CDATA[http://photo.goodreads.com/users/1257704007p2/2922139.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">86379</id>
  <isbn>0596001738</isbn>
  <isbn13>9780596001735</isbn13>
  <text_reviews_count type="integer">4</text_reviews_count>
  <title>
    <![CDATA[Perl Best Practices]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1171067732m/86379.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1171067732s/86379.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/86379.Perl_Best_Practices</link>
  <average_rating>4.34</average_rating>
  <ratings_count>41</ratings_count>
  <description>
    <![CDATA[&lt;DIV&gt;Many programmers code by instinct, relying on convenient habits or a &quot;style&quot; they picked up early on. They aren't conscious of all the choices they make, like how they format their source, the names they use for variables, or the kinds of loops they use. They're focused entirely on problems they're solving, solutions they're creating, and algorithms they're implementing. So they write code in the way that seems natural, that happens intuitively, and that feels good. <p> But if you're serious about your profession, intuition isn't enough. &quot;Perl Best Practices&quot; author Damian Conway explains that rules, conventions, standards, and practices not only help programmers communicate and coordinate with one another, they also provide a reliable framework for thinking about problems, and a common language for expressing solutions. This is especially critical in Perl, because the language is designed to offer many ways to accomplish the same task, and consequently it supports many incompatible dialects. <p> With a good dose of Aussie humor, Dr. Conway (familiar to many in the Perl community) offers 256 guidelines on the art of coding to help you write better Perl code--in fact, the best Perl code you possibly can. The guidelines cover code layout, naming conventions, choice of data and control structures, program decomposition, interface design and implementation, modularity, object orientation, error handling, testing, and debugging. <p> They're designed to work together to produce code that is clear, robust, efficient, maintainable, and concise, but Dr. Conway doesn't pretend that this is the one true universal and unequivocal set of best practices. Instead, &quot;Perl Best Practices&quot; offerscoherent and widely applicable suggestions based on real-world experience of how code is actually written, rather than on someone's ivory-tower theories on how<p> software ought to be created. <p> Most of all, &quot;Perl Best Practices&quot; offers guidelines that actually work, and that many developers around the world are already using. Much like Perl itself, these guidelines are about helping you to get your job done, without getting in the way. <p> Praise for &quot;Perl Best Practices&quot; from Perl community members: <p> &quot;As a manager of a large Perl project, I'd ensure that every member of my team has a copy of &quot;Perl Best Practices&quot; on their desk, and use it as the basis for an in-house style guide.&quot; <p> -- Randal Schwartz <p> &quot;There are no more excuses for writing bad Perl programs. All levels of Perl programmer will be more productive after reading this book.&quot; <p> -- Peter Scott <p> &quot;&quot;Perl Best Practices&quot; will be the next big important book in the evolution of Perl. The ideas and practices Damian lays down will help bring Perl out from under the embarrassing heading of &quot;scripting languages.&quot; Many of us have known Perl is a real programming language, worthy of all the tasks normally delegated to Java and C++. With Perl Best Practices, Damian shows specifically how and why, so everyone else can see, too.&quot; <p> -- Andy Lester <p> &quot;Damian's done what many thought impossible: show how to build large, maintainable Perl applications, while still letting Perl be the powerful, expressive language that programmers have loved for years.&quot; <p> -- Bill Odom <p> &quot;Finally, a means to bring lasting order to the process and product of real Perl development teams.&quot; <p> -- Andrew Sundstrom <p>&quot;&quot;Perl Best Practices&quot; provides a valuable education in how to write robust, maintainable Perl, and is a definitive citation source when coaching other programmers.&quot; <p> -- Bennett Todd <p> &quot;I've been teaching Perl for years, and find the same question keeps being asked: Where can I find a reference for writing reusable, maintainable Perl code? Finally I have a decent answer.&quot; <p> -- Paul Fenwick &lt;p&gt; &quot;At last a well researched, well thought-out, comprehensive guide to Perl style. Instead of each of us developing our own, we can learn good practices from one of Perl's most prolific and experienced authors. I recommend this book to anyone who prefers getting on with the job rather than going back and fixing errors caused by syntax and poor style issues.&quot; &lt;p&gt; -- Jacinta Richardson &lt;p&gt; &quot;If you care about programming in any language read this book. Even if you don't intend to follow all of the practices, thinking through your style will improve it.&quot;&lt;p&gt; -- Steven Lembark &lt;p&gt; &quot;The Perl community's best author is back with another outstanding book. There has never been a comprehensive reference on high quality Perl coding and style until &quot;Perl Best Practices,&quot; This book fills a large gap in every Perl bookshelf.&quot; &lt;p&gt; -- Uri Guttman</p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p>]]>
  </description>
  <published>2005</published>
</book>

    <rating>5</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
        <shelf name="read" />
          </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Sun Nov 08 14:39:51 -0800 2009</date_added>
  <date_updated>Thu Nov 12 14:40:54 -0800 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/77128364]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/77128364]]></link>
</review>
      <review>
  <id>76137996</id>
    <user>
    <id>2884126</id>
    <name><![CDATA[Billy]]></name>
    <location><![CDATA[The United States]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/2884126-billy-conn]]></link>
    <image_url><![CDATA[http://www.goodreads.com/images/nophoto-M-111x148.jpg]]></image_url>
    <small_image_url><![CDATA[http://www.goodreads.com/images/nophoto-M-50x66.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">86379</id>
  <isbn>0596001738</isbn>
  <isbn13>9780596001735</isbn13>
  <text_reviews_count type="integer">4</text_reviews_count>
  <title>
    <![CDATA[Perl Best Practices]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1171067732m/86379.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1171067732s/86379.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/86379.Perl_Best_Practices</link>
  <average_rating>4.34</average_rating>
  <ratings_count>41</ratings_count>
  <description>
    <![CDATA[&lt;DIV&gt;Many programmers code by instinct, relying on convenient habits or a &quot;style&quot; they picked up early on. They aren't conscious of all the choices they make, like how they format their source, the names they use for variables, or the kinds of loops they use. They're focused entirely on problems they're solving, solutions they're creating, and algorithms they're implementing. So they write code in the way that seems natural, that happens intuitively, and that feels good. <p> But if you're serious about your profession, intuition isn't enough. &quot;Perl Best Practices&quot; author Damian Conway explains that rules, conventions, standards, and practices not only help programmers communicate and coordinate with one another, they also provide a reliable framework for thinking about problems, and a common language for expressing solutions. This is especially critical in Perl, because the language is designed to offer many ways to accomplish the same task, and consequently it supports many incompatible dialects. <p> With a good dose of Aussie humor, Dr. Conway (familiar to many in the Perl community) offers 256 guidelines on the art of coding to help you write better Perl code--in fact, the best Perl code you possibly can. The guidelines cover code layout, naming conventions, choice of data and control structures, program decomposition, interface design and implementation, modularity, object orientation, error handling, testing, and debugging. <p> They're designed to work together to produce code that is clear, robust, efficient, maintainable, and concise, but Dr. Conway doesn't pretend that this is the one true universal and unequivocal set of best practices. Instead, &quot;Perl Best Practices&quot; offerscoherent and widely applicable suggestions based on real-world experience of how code is actually written, rather than on someone's ivory-tower theories on how<p> software ought to be created. <p> Most of all, &quot;Perl Best Practices&quot; offers guidelines that actually work, and that many developers around the world are already using. Much like Perl itself, these guidelines are about helping you to get your job done, without getting in the way. <p> Praise for &quot;Perl Best Practices&quot; from Perl community members: <p> &quot;As a manager of a large Perl project, I'd ensure that every member of my team has a copy of &quot;Perl Best Practices&quot; on their desk, and use it as the basis for an in-house style guide.&quot; <p> -- Randal Schwartz <p> &quot;There are no more excuses for writing bad Perl programs. All levels of Perl programmer will be more productive after reading this book.&quot; <p> -- Peter Scott <p> &quot;&quot;Perl Best Practices&quot; will be the next big important book in the evolution of Perl. The ideas and practices Damian lays down will help bring Perl out from under the embarrassing heading of &quot;scripting languages.&quot; Many of us have known Perl is a real programming language, worthy of all the tasks normally delegated to Java and C++. With Perl Best Practices, Damian shows specifically how and why, so everyone else can see, too.&quot; <p> -- Andy Lester <p> &quot;Damian's done what many thought impossible: show how to build large, maintainable Perl applications, while still letting Perl be the powerful, expressive language that programmers have loved for years.&quot; <p> -- Bill Odom <p> &quot;Finally, a means to bring lasting order to the process and product of real Perl development teams.&quot; <p> -- Andrew Sundstrom <p>&quot;&quot;Perl Best Practices&quot; provides a valuable education in how to write robust, maintainable Perl, and is a definitive citation source when coaching other programmers.&quot; <p> -- Bennett Todd <p> &quot;I've been teaching Perl for years, and find the same question keeps being asked: Where can I find a reference for writing reusable, maintainable Perl code? Finally I have a decent answer.&quot; <p> -- Paul Fenwick &lt;p&gt; &quot;At last a well researched, well thought-out, comprehensive guide to Perl style. Instead of each of us developing our own, we can learn good practices from one of Perl's most prolific and experienced authors. I recommend this book to anyone who prefers getting on with the job rather than going back and fixing errors caused by syntax and poor style issues.&quot; &lt;p&gt; -- Jacinta Richardson &lt;p&gt; &quot;If you care about programming in any language read this book. Even if you don't intend to follow all of the practices, thinking through your style will improve it.&quot;&lt;p&gt; -- Steven Lembark &lt;p&gt; &quot;The Perl community's best author is back with another outstanding book. There has never been a comprehensive reference on high quality Perl coding and style until &quot;Perl Best Practices,&quot; This book fills a large gap in every Perl bookshelf.&quot; &lt;p&gt; -- Uri Guttman</p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p>]]>
  </description>
  <published>2005</published>
</book>

    <rating>3</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
        <shelf name="read" />
          </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Thu Oct 29 13:09:53 -0700 2009</date_added>
  <date_updated>Thu Oct 29 13:09:53 -0700 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/76137996]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/76137996]]></link>
</review>
      <review>
  <id>74533738</id>
    <user>
    <id>2787540</id>
    <name><![CDATA[Julian]]></name>
    <location><![CDATA[Sofia, 42, Bulgaria]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/2787540-julian]]></link>
    <image_url><![CDATA[http://www.goodreads.com/images/nophoto-U-111x148.jpg]]></image_url>
    <small_image_url><![CDATA[http://www.goodreads.com/images/nophoto-U-50x66.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">86379</id>
  <isbn>0596001738</isbn>
  <isbn13>9780596001735</isbn13>
  <text_reviews_count type="integer">4</text_reviews_count>
  <title>
    <![CDATA[Perl Best Practices]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1171067732m/86379.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1171067732s/86379.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/86379.Perl_Best_Practices</link>
  <average_rating>4.34</average_rating>
  <ratings_count>41</ratings_count>
  <description>
    <![CDATA[&lt;DIV&gt;Many programmers code by instinct, relying on convenient habits or a &quot;style&quot; they picked up early on. They aren't conscious of all the choices they make, like how they format their source, the names they use for variables, or the kinds of loops they use. They're focused entirely on problems they're solving, solutions they're creating, and algorithms they're implementing. So they write code in the way that seems natural, that happens intuitively, and that feels good. <p> But if you're serious about your profession, intuition isn't enough. &quot;Perl Best Practices&quot; author Damian Conway explains that rules, conventions, standards, and practices not only help programmers communicate and coordinate with one another, they also provide a reliable framework for thinking about problems, and a common language for expressing solutions. This is especially critical in Perl, because the language is designed to offer many ways to accomplish the same task, and consequently it supports many incompatible dialects. <p> With a good dose of Aussie humor, Dr. Conway (familiar to many in the Perl community) offers 256 guidelines on the art of coding to help you write better Perl code--in fact, the best Perl code you possibly can. The guidelines cover code layout, naming conventions, choice of data and control structures, program decomposition, interface design and implementation, modularity, object orientation, error handling, testing, and debugging. <p> They're designed to work together to produce code that is clear, robust, efficient, maintainable, and concise, but Dr. Conway doesn't pretend that this is the one true universal and unequivocal set of best practices. Instead, &quot;Perl Best Practices&quot; offerscoherent and widely applicable suggestions based on real-world experience of how code is actually written, rather than on someone's ivory-tower theories on how<p> software ought to be created. <p> Most of all, &quot;Perl Best Practices&quot; offers guidelines that actually work, and that many developers around the world are already using. Much like Perl itself, these guidelines are about helping you to get your job done, without getting in the way. <p> Praise for &quot;Perl Best Practices&quot; from Perl community members: <p> &quot;As a manager of a large Perl project, I'd ensure that every member of my team has a copy of &quot;Perl Best Practices&quot; on their desk, and use it as the basis for an in-house style guide.&quot; <p> -- Randal Schwartz <p> &quot;There are no more excuses for writing bad Perl programs. All levels of Perl programmer will be more productive after reading this book.&quot; <p> -- Peter Scott <p> &quot;&quot;Perl Best Practices&quot; will be the next big important book in the evolution of Perl. The ideas and practices Damian lays down will help bring Perl out from under the embarrassing heading of &quot;scripting languages.&quot; Many of us have known Perl is a real programming language, worthy of all the tasks normally delegated to Java and C++. With Perl Best Practices, Damian shows specifically how and why, so everyone else can see, too.&quot; <p> -- Andy Lester <p> &quot;Damian's done what many thought impossible: show how to build large, maintainable Perl applications, while still letting Perl be the powerful, expressive language that programmers have loved for years.&quot; <p> -- Bill Odom <p> &quot;Finally, a means to bring lasting order to the process and product of real Perl development teams.&quot; <p> -- Andrew Sundstrom <p>&quot;&quot;Perl Best Practices&quot; provides a valuable education in how to write robust, maintainable Perl, and is a definitive citation source when coaching other programmers.&quot; <p> -- Bennett Todd <p> &quot;I've been teaching Perl for years, and find the same question keeps being asked: Where can I find a reference for writing reusable, maintainable Perl code? Finally I have a decent answer.&quot; <p> -- Paul Fenwick &lt;p&gt; &quot;At last a well researched, well thought-out, comprehensive guide to Perl style. Instead of each of us developing our own, we can learn good practices from one of Perl's most prolific and experienced authors. I recommend this book to anyone who prefers getting on with the job rather than going back and fixing errors caused by syntax and poor style issues.&quot; &lt;p&gt; -- Jacinta Richardson &lt;p&gt; &quot;If you care about programming in any language read this book. Even if you don't intend to follow all of the practices, thinking through your style will improve it.&quot;&lt;p&gt; -- Steven Lembark &lt;p&gt; &quot;The Perl community's best author is back with another outstanding book. There has never been a comprehensive reference on high quality Perl coding and style until &quot;Perl Best Practices,&quot; This book fills a large gap in every Perl bookshelf.&quot; &lt;p&gt; -- Uri Guttman</p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p>]]>
  </description>
  <published>2005</published>
</book>

    <rating>4</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
        <shelf name="read" />
          </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Wed Oct 14 13:16:10 -0700 2009</date_added>
  <date_updated>Wed Oct 14 13:16:10 -0700 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/74533738]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/74533738]]></link>
</review>
      <review>
  <id>68443496</id>
    <user>
    <id>2654417</id>
    <name><![CDATA[Matt]]></name>
    <location><![CDATA[Melbourne, 07, Australia]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/2654417-matt-koscica]]></link>
    <image_url><![CDATA[http://photo.goodreads.com/users/1250952786p3/2654417.jpg]]></image_url>
    <small_image_url><![CDATA[http://photo.goodreads.com/users/1250952786p2/2654417.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">86379</id>
  <isbn>0596001738</isbn>
  <isbn13>9780596001735</isbn13>
  <text_reviews_count type="integer">4</text_reviews_count>
  <title>
    <![CDATA[Perl Best Practices]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1171067732m/86379.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1171067732s/86379.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/86379.Perl_Best_Practices</link>
  <average_rating>4.34</average_rating>
  <ratings_count>41</ratings_count>
  <description>
    <![CDATA[&lt;DIV&gt;Many programmers code by instinct, relying on convenient habits or a &quot;style&quot; they picked up early on. They aren't conscious of all the choices they make, like how they format their source, the names they use for variables, or the kinds of loops they use. They're focused entirely on problems they're solving, solutions they're creating, and algorithms they're implementing. So they write code in the way that seems natural, that happens intuitively, and that feels good. <p> But if you're serious about your profession, intuition isn't enough. &quot;Perl Best Practices&quot; author Damian Conway explains that rules, conventions, standards, and practices not only help programmers communicate and coordinate with one another, they also provide a reliable framework for thinking about problems, and a common language for expressing solutions. This is especially critical in Perl, because the language is designed to offer many ways to accomplish the same task, and consequently it supports many incompatible dialects. <p> With a good dose of Aussie humor, Dr. Conway (familiar to many in the Perl community) offers 256 guidelines on the art of coding to help you write better Perl code--in fact, the best Perl code you possibly can. The guidelines cover code layout, naming conventions, choice of data and control structures, program decomposition, interface design and implementation, modularity, object orientation, error handling, testing, and debugging. <p> They're designed to work together to produce code that is clear, robust, efficient, maintainable, and concise, but Dr. Conway doesn't pretend that this is the one true universal and unequivocal set of best practices. Instead, &quot;Perl Best Practices&quot; offerscoherent and widely applicable suggestions based on real-world experience of how code is actually written, rather than on someone's ivory-tower theories on how<p> software ought to be created. <p> Most of all, &quot;Perl Best Practices&quot; offers guidelines that actually work, and that many developers around the world are already using. Much like Perl itself, these guidelines are about helping you to get your job done, without getting in the way. <p> Praise for &quot;Perl Best Practices&quot; from Perl community members: <p> &quot;As a manager of a large Perl project, I'd ensure that every member of my team has a copy of &quot;Perl Best Practices&quot; on their desk, and use it as the basis for an in-house style guide.&quot; <p> -- Randal Schwartz <p> &quot;There are no more excuses for writing bad Perl programs. All levels of Perl programmer will be more productive after reading this book.&quot; <p> -- Peter Scott <p> &quot;&quot;Perl Best Practices&quot; will be the next big important book in the evolution of Perl. The ideas and practices Damian lays down will help bring Perl out from under the embarrassing heading of &quot;scripting languages.&quot; Many of us have known Perl is a real programming language, worthy of all the tasks normally delegated to Java and C++. With Perl Best Practices, Damian shows specifically how and why, so everyone else can see, too.&quot; <p> -- Andy Lester <p> &quot;Damian's done what many thought impossible: show how to build large, maintainable Perl applications, while still letting Perl be the powerful, expressive language that programmers have loved for years.&quot; <p> -- Bill Odom <p> &quot;Finally, a means to bring lasting order to the process and product of real Perl development teams.&quot; <p> -- Andrew Sundstrom <p>&quot;&quot;Perl Best Practices&quot; provides a valuable education in how to write robust, maintainable Perl, and is a definitive citation source when coaching other programmers.&quot; <p> -- Bennett Todd <p> &quot;I've been teaching Perl for years, and find the same question keeps being asked: Where can I find a reference for writing reusable, maintainable Perl code? Finally I have a decent answer.&quot; <p> -- Paul Fenwick &lt;p&gt; &quot;At last a well researched, well thought-out, comprehensive guide to Perl style. Instead of each of us developing our own, we can learn good practices from one of Perl's most prolific and experienced authors. I recommend this book to anyone who prefers getting on with the job rather than going back and fixing errors caused by syntax and poor style issues.&quot; &lt;p&gt; -- Jacinta Richardson &lt;p&gt; &quot;If you care about programming in any language read this book. Even if you don't intend to follow all of the practices, thinking through your style will improve it.&quot;&lt;p&gt; -- Steven Lembark &lt;p&gt; &quot;The Perl community's best author is back with another outstanding book. There has never been a comprehensive reference on high quality Perl coding and style until &quot;Perl Best Practices,&quot; This book fills a large gap in every Perl bookshelf.&quot; &lt;p&gt; -- Uri Guttman</p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p>]]>
  </description>
  <published>2005</published>
</book>

    <rating>0</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
        <shelf name="read" />
          </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Sat Aug 22 07:58:22 -0700 2009</date_added>
  <date_updated>Sat Aug 22 07:58:22 -0700 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/68443496]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/68443496]]></link>
</review>
      <review>
  <id>66098915</id>
    <user>
    <id>1470375</id>
    <name><![CDATA[Alec]]></name>
    <location><![CDATA[Australia]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/1470375-alec]]></link>
    <image_url><![CDATA[http://www.goodreads.com/images/nophoto-U-111x148.jpg]]></image_url>
    <small_image_url><![CDATA[http://www.goodreads.com/images/nophoto-U-50x66.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">86379</id>
  <isbn>0596001738</isbn>
  <isbn13>9780596001735</isbn13>
  <text_reviews_count type="integer">4</text_reviews_count>
  <title>
    <![CDATA[Perl Best Practices]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1171067732m/86379.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1171067732s/86379.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/86379.Perl_Best_Practices</link>
  <average_rating>4.34</average_rating>
  <ratings_count>41</ratings_count>
  <description>
    <![CDATA[&lt;DIV&gt;Many programmers code by instinct, relying on convenient habits or a &quot;style&quot; they picked up early on. They aren't conscious of all the choices they make, like how they format their source, the names they use for variables, or the kinds of loops they use. They're focused entirely on problems they're solving, solutions they're creating, and algorithms they're implementing. So they write code in the way that seems natural, that happens intuitively, and that feels good. <p> But if you're serious about your profession, intuition isn't enough. &quot;Perl Best Practices&quot; author Damian Conway explains that rules, conventions, standards, and practices not only help programmers communicate and coordinate with one another, they also provide a reliable framework for thinking about problems, and a common language for expressing solutions. This is especially critical in Perl, because the language is designed to offer many ways to accomplish the same task, and consequently it supports many incompatible dialects. <p> With a good dose of Aussie humor, Dr. Conway (familiar to many in the Perl community) offers 256 guidelines on the art of coding to help you write better Perl code--in fact, the best Perl code you possibly can. The guidelines cover code layout, naming conventions, choice of data and control structures, program decomposition, interface design and implementation, modularity, object orientation, error handling, testing, and debugging. <p> They're designed to work together to produce code that is clear, robust, efficient, maintainable, and concise, but Dr. Conway doesn't pretend that this is the one true universal and unequivocal set of best practices. Instead, &quot;Perl Best Practices&quot; offerscoherent and widely applicable suggestions based on real-world experience of how code is actually written, rather than on someone's ivory-tower theories on how<p> software ought to be created. <p> Most of all, &quot;Perl Best Practices&quot; offers guidelines that actually work, and that many developers around the world are already using. Much like Perl itself, these guidelines are about helping you to get your job done, without getting in the way. <p> Praise for &quot;Perl Best Practices&quot; from Perl community members: <p> &quot;As a manager of a large Perl project, I'd ensure that every member of my team has a copy of &quot;Perl Best Practices&quot; on their desk, and use it as the basis for an in-house style guide.&quot; <p> -- Randal Schwartz <p> &quot;There are no more excuses for writing bad Perl programs. All levels of Perl programmer will be more productive after reading this book.&quot; <p> -- Peter Scott <p> &quot;&quot;Perl Best Practices&quot; will be the next big important book in the evolution of Perl. The ideas and practices Damian lays down will help bring Perl out from under the embarrassing heading of &quot;scripting languages.&quot; Many of us have known Perl is a real programming language, worthy of all the tasks normally delegated to Java and C++. With Perl Best Practices, Damian shows specifically how and why, so everyone else can see, too.&quot; <p> -- Andy Lester <p> &quot;Damian's done what many thought impossible: show how to build large, maintainable Perl applications, while still letting Perl be the powerful, expressive language that programmers have loved for years.&quot; <p> -- Bill Odom <p> &quot;Finally, a means to bring lasting order to the process and product of real Perl development teams.&quot; <p> -- Andrew Sundstrom <p>&quot;&quot;Perl Best Practices&quot; provides a valuable education in how to write robust, maintainable Perl, and is a definitive citation source when coaching other programmers.&quot; <p> -- Bennett Todd <p> &quot;I've been teaching Perl for years, and find the same question keeps being asked: Where can I find a reference for writing reusable, maintainable Perl code? Finally I have a decent answer.&quot; <p> -- Paul Fenwick &lt;p&gt; &quot;At last a well researched, well thought-out, comprehensive guide to Perl style. Instead of each of us developing our own, we can learn good practices from one of Perl's most prolific and experienced authors. I recommend this book to anyone who prefers getting on with the job rather than going back and fixing errors caused by syntax and poor style issues.&quot; &lt;p&gt; -- Jacinta Richardson &lt;p&gt; &quot;If you care about programming in any language read this book. Even if you don't intend to follow all of the practices, thinking through your style will improve it.&quot;&lt;p&gt; -- Steven Lembark &lt;p&gt; &quot;The Perl community's best author is back with another outstanding book. There has never been a comprehensive reference on high quality Perl coding and style until &quot;Perl Best Practices,&quot; This book fills a large gap in every Perl bookshelf.&quot; &lt;p&gt; -- Uri Guttman</p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p>]]>
  </description>
  <published>2005</published>
</book>

    <rating>0</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
        <shelf name="read" />
          </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Mon Aug 03 21:35:43 -0700 2009</date_added>
  <date_updated>Mon Aug 03 21:35:43 -0700 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/66098915]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/66098915]]></link>
</review>
      <review>
  <id>65418520</id>
    <user>
    <id>2574219</id>
    <name><![CDATA[Victor]]></name>
    <location><![CDATA[Bellevue, WA]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/2574219-victor-grigoriu]]></link>
    <image_url><![CDATA[http://photo.goodreads.com/users/1248889534p3/2574219.jpg]]></image_url>
    <small_image_url><![CDATA[http://photo.goodreads.com/users/1248889534p2/2574219.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">86379</id>
  <isbn>0596001738</isbn>
  <isbn13>9780596001735</isbn13>
  <text_reviews_count type="integer">4</text_reviews_count>
  <title>
    <![CDATA[Perl Best Practices]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1171067732m/86379.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1171067732s/86379.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/86379.Perl_Best_Practices</link>
  <average_rating>4.34</average_rating>
  <ratings_count>41</ratings_count>
  <description>
    <![CDATA[&lt;DIV&gt;Many programmers code by instinct, relying on convenient habits or a &quot;style&quot; they picked up early on. They aren't conscious of all the choices they make, like how they format their source, the names they use for variables, or the kinds of loops they use. They're focused entirely on problems they're solving, solutions they're creating, and algorithms they're implementing. So they write code in the way that seems natural, that happens intuitively, and that feels good. <p> But if you're serious about your profession, intuition isn't enough. &quot;Perl Best Practices&quot; author Damian Conway explains that rules, conventions, standards, and practices not only help programmers communicate and coordinate with one another, they also provide a reliable framework for thinking about problems, and a common language for expressing solutions. This is especially critical in Perl, because the language is designed to offer many ways to accomplish the same task, and consequently it supports many incompatible dialects. <p> With a good dose of Aussie humor, Dr. Conway (familiar to many in the Perl community) offers 256 guidelines on the art of coding to help you write better Perl code--in fact, the best Perl code you possibly can. The guidelines cover code layout, naming conventions, choice of data and control structures, program decomposition, interface design and implementation, modularity, object orientation, error handling, testing, and debugging. <p> They're designed to work together to produce code that is clear, robust, efficient, maintainable, and concise, but Dr. Conway doesn't pretend that this is the one true universal and unequivocal set of best practices. Instead, &quot;Perl Best Practices&quot; offerscoherent and widely applicable suggestions based on real-world experience of how code is actually written, rather than on someone's ivory-tower theories on how<p> software ought to be created. <p> Most of all, &quot;Perl Best Practices&quot; offers guidelines that actually work, and that many developers around the world are already using. Much like Perl itself, these guidelines are about helping you to get your job done, without getting in the way. <p> Praise for &quot;Perl Best Practices&quot; from Perl community members: <p> &quot;As a manager of a large Perl project, I'd ensure that every member of my team has a copy of &quot;Perl Best Practices&quot; on their desk, and use it as the basis for an in-house style guide.&quot; <p> -- Randal Schwartz <p> &quot;There are no more excuses for writing bad Perl programs. All levels of Perl programmer will be more productive after reading this book.&quot; <p> -- Peter Scott <p> &quot;&quot;Perl Best Practices&quot; will be the next big important book in the evolution of Perl. The ideas and practices Damian lays down will help bring Perl out from under the embarrassing heading of &quot;scripting languages.&quot; Many of us have known Perl is a real programming language, worthy of all the tasks normally delegated to Java and C++. With Perl Best Practices, Damian shows specifically how and why, so everyone else can see, too.&quot; <p> -- Andy Lester <p> &quot;Damian's done what many thought impossible: show how to build large, maintainable Perl applications, while still letting Perl be the powerful, expressive language that programmers have loved for years.&quot; <p> -- Bill Odom <p> &quot;Finally, a means to bring lasting order to the process and product of real Perl development teams.&quot; <p> -- Andrew Sundstrom <p>&quot;&quot;Perl Best Practices&quot; provides a valuable education in how to write robust, maintainable Perl, and is a definitive citation source when coaching other programmers.&quot; <p> -- Bennett Todd <p> &quot;I've been teaching Perl for years, and find the same question keeps being asked: Where can I find a reference for writing reusable, maintainable Perl code? Finally I have a decent answer.&quot; <p> -- Paul Fenwick &lt;p&gt; &quot;At last a well researched, well thought-out, comprehensive guide to Perl style. Instead of each of us developing our own, we can learn good practices from one of Perl's most prolific and experienced authors. I recommend this book to anyone who prefers getting on with the job rather than going back and fixing errors caused by syntax and poor style issues.&quot; &lt;p&gt; -- Jacinta Richardson &lt;p&gt; &quot;If you care about programming in any language read this book. Even if you don't intend to follow all of the practices, thinking through your style will improve it.&quot;&lt;p&gt; -- Steven Lembark &lt;p&gt; &quot;The Perl community's best author is back with another outstanding book. There has never been a comprehensive reference on high quality Perl coding and style until &quot;Perl Best Practices,&quot; This book fills a large gap in every Perl bookshelf.&quot; &lt;p&gt; -- Uri Guttman</p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p>]]>
  </description>
  <published>2005</published>
</book>

    <rating>4</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
        <shelf name="read" />
          </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at>Mon Jun 01 00:00:00 -0700 2009</read_at>
  <date_added>Wed Jul 29 10:49:57 -0700 2009</date_added>
  <date_updated>Wed Jul 29 10:50:29 -0700 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/65418520]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/65418520]]></link>
</review>
      <review>
  <id>59720093</id>
    <user>
    <id>2409056</id>
    <name><![CDATA[Max]]></name>
    <location><![CDATA[Zephyr Cove, NV]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/2409056-max-lybbert]]></link>
    <image_url><![CDATA[http://www.goodreads.com/images/nophoto-U-111x148.jpg]]></image_url>
    <small_image_url><![CDATA[http://www.goodreads.com/images/nophoto-U-50x66.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">86379</id>
  <isbn>0596001738</isbn>
  <isbn13>9780596001735</isbn13>
  <text_reviews_count type="integer">4</text_reviews_count>
  <title>
    <![CDATA[Perl Best Practices]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1171067732m/86379.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1171067732s/86379.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/86379.Perl_Best_Practices</link>
  <average_rating>4.34</average_rating>
  <ratings_count>41</ratings_count>
  <description>
    <![CDATA[&lt;DIV&gt;Many programmers code by instinct, relying on convenient habits or a &quot;style&quot; they picked up early on. They aren't conscious of all the choices they make, like how they format their source, the names they use for variables, or the kinds of loops they use. They're focused entirely on problems they're solving, solutions they're creating, and algorithms they're implementing. So they write code in the way that seems natural, that happens intuitively, and that feels good. <p> But if you're serious about your profession, intuition isn't enough. &quot;Perl Best Practices&quot; author Damian Conway explains that rules, conventions, standards, and practices not only help programmers communicate and coordinate with one another, they also provide a reliable framework for thinking about problems, and a common language for expressing solutions. This is especially critical in Perl, because the language is designed to offer many ways to accomplish the same task, and consequently it supports many incompatible dialects. <p> With a good dose of Aussie humor, Dr. Conway (familiar to many in the Perl community) offers 256 guidelines on the art of coding to help you write better Perl code--in fact, the best Perl code you possibly can. The guidelines cover code layout, naming conventions, choice of data and control structures, program decomposition, interface design and implementation, modularity, object orientation, error handling, testing, and debugging. <p> They're designed to work together to produce code that is clear, robust, efficient, maintainable, and concise, but Dr. Conway doesn't pretend that this is the one true universal and unequivocal set of best practices. Instead, &quot;Perl Best Practices&quot; offerscoherent and widely applicable suggestions based on real-world experience of how code is actually written, rather than on someone's ivory-tower theories on how<p> software ought to be created. <p> Most of all, &quot;Perl Best Practices&quot; offers guidelines that actually work, and that many developers around the world are already using. Much like Perl itself, these guidelines are about helping you to get your job done, without getting in the way. <p> Praise for &quot;Perl Best Practices&quot; from Perl community members: <p> &quot;As a manager of a large Perl project, I'd ensure that every member of my team has a copy of &quot;Perl Best Practices&quot; on their desk, and use it as the basis for an in-house style guide.&quot; <p> -- Randal Schwartz <p> &quot;There are no more excuses for writing bad Perl programs. All levels of Perl programmer will be more productive after reading this book.&quot; <p> -- Peter Scott <p> &quot;&quot;Perl Best Practices&quot; will be the next big important book in the evolution of Perl. The ideas and practices Damian lays down will help bring Perl out from under the embarrassing heading of &quot;scripting languages.&quot; Many of us have known Perl is a real programming language, worthy of all the tasks normally delegated to Java and C++. With Perl Best Practices, Damian shows specifically how and why, so everyone else can see, too.&quot; <p> -- Andy Lester <p> &quot;Damian's done what many thought impossible: show how to build large, maintainable Perl applications, while still letting Perl be the powerful, expressive language that programmers have loved for years.&quot; <p> -- Bill Odom <p> &quot;Finally, a means to bring lasting order to the process and product of real Perl development teams.&quot; <p> -- Andrew Sundstrom <p>&quot;&quot;Perl Best Practices&quot; provides a valuable education in how to write robust, maintainable Perl, and is a definitive citation source when coaching other programmers.&quot; <p> -- Bennett Todd <p> &quot;I've been teaching Perl for years, and find the same question keeps being asked: Where can I find a reference for writing reusable, maintainable Perl code? Finally I have a decent answer.&quot; <p> -- Paul Fenwick &lt;p&gt; &quot;At last a well researched, well thought-out, comprehensive guide to Perl style. Instead of each of us developing our own, we can learn good practices from one of Perl's most prolific and experienced authors. I recommend this book to anyone who prefers getting on with the job rather than going back and fixing errors caused by syntax and poor style issues.&quot; &lt;p&gt; -- Jacinta Richardson &lt;p&gt; &quot;If you care about programming in any language read this book. Even if you don't intend to follow all of the practices, thinking through your style will improve it.&quot;&lt;p&gt; -- Steven Lembark &lt;p&gt; &quot;The Perl community's best author is back with another outstanding book. There has never been a comprehensive reference on high quality Perl coding and style until &quot;Perl Best Practices,&quot; This book fills a large gap in every Perl bookshelf.&quot; &lt;p&gt; -- Uri Guttman</p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p>]]>
  </description>
  <published>2005</published>
</book>

    <rating>5</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
        <shelf name="read" />
          </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Mon Jun 15 06:53:13 -0700 2009</date_added>
  <date_updated>Mon Jun 15 06:53:13 -0700 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/59720093]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/59720093]]></link>
</review>
      <review>
  <id>59663230</id>
    <user>
    <id>626358</id>
    <name><![CDATA[Damian]]></name>
    <location><![CDATA[San Francisco, CA]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/626358-damian]]></link>
    <image_url><![CDATA[http://www.goodreads.com/images/nophoto-M-111x148.jpg]]></image_url>
    <small_image_url><![CDATA[http://www.goodreads.com/images/nophoto-M-50x66.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">86379</id>
  <isbn>0596001738</isbn>
  <isbn13>9780596001735</isbn13>
  <text_reviews_count type="integer">4</text_reviews_count>
  <title>
    <![CDATA[Perl Best Practices]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1171067732m/86379.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1171067732s/86379.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/86379.Perl_Best_Practices</link>
  <average_rating>4.34</average_rating>
  <ratings_count>41</ratings_count>
  <description>
    <![CDATA[&lt;DIV&gt;Many programmers code by instinct, relying on convenient habits or a &quot;style&quot; they picked up early on. They aren't conscious of all the choices they make, like how they format their source, the names they use for variables, or the kinds of loops they use. They're focused entirely on problems they're solving, solutions they're creating, and algorithms they're implementing. So they write code in the way that seems natural, that happens intuitively, and that feels good. <p> But if you're serious about your profession, intuition isn't enough. &quot;Perl Best Practices&quot; author Damian Conway explains that rules, conventions, standards, and practices not only help programmers communicate and coordinate with one another, they also provide a reliable framework for thinking about problems, and a common language for expressing solutions. This is especially critical in Perl, because the language is designed to offer many ways to accomplish the same task, and consequently it supports many incompatible dialects. <p> With a good dose of Aussie humor, Dr. Conway (familiar to many in the Perl community) offers 256 guidelines on the art of coding to help you write better Perl code--in fact, the best Perl code you possibly can. The guidelines cover code layout, naming conventions, choice of data and control structures, program decomposition, interface design and implementation, modularity, object orientation, error handling, testing, and debugging. <p> They're designed to work together to produce code that is clear, robust, efficient, maintainable, and concise, but Dr. Conway doesn't pretend that this is the one true universal and unequivocal set of best practices. Instead, &quot;Perl Best Practices&quot; offerscoherent and widely applicable suggestions based on real-world experience of how code is actually written, rather than on someone's ivory-tower theories on how<p> software ought to be created. <p> Most of all, &quot;Perl Best Practices&quot; offers guidelines that actually work, and that many developers around the world are already using. Much like Perl itself, these guidelines are about helping you to get your job done, without getting in the way. <p> Praise for &quot;Perl Best Practices&quot; from Perl community members: <p> &quot;As a manager of a large Perl project, I'd ensure that every member of my team has a copy of &quot;Perl Best Practices&quot; on their desk, and use it as the basis for an in-house style guide.&quot; <p> -- Randal Schwartz <p> &quot;There are no more excuses for writing bad Perl programs. All levels of Perl programmer will be more productive after reading this book.&quot; <p> -- Peter Scott <p> &quot;&quot;Perl Best Practices&quot; will be the next big important book in the evolution of Perl. The ideas and practices Damian lays down will help bring Perl out from under the embarrassing heading of &quot;scripting languages.&quot; Many of us have known Perl is a real programming language, worthy of all the tasks normally delegated to Java and C++. With Perl Best Practices, Damian shows specifically how and why, so everyone else can see, too.&quot; <p> -- Andy Lester <p> &quot;Damian's done what many thought impossible: show how to build large, maintainable Perl applications, while still letting Perl be the powerful, expressive language that programmers have loved for years.&quot; <p> -- Bill Odom <p> &quot;Finally, a means to bring lasting order to the process and product of real Perl development teams.&quot; <p> -- Andrew Sundstrom <p>&quot;&quot;Perl Best Practices&quot; provides a valuable education in how to write robust, maintainable Perl, and is a definitive citation source when coaching other programmers.&quot; <p> -- Bennett Todd <p> &quot;I've been teaching Perl for years, and find the same question keeps being asked: Where can I find a reference for writing reusable, maintainable Perl code? Finally I have a decent answer.&quot; <p> -- Paul Fenwick &lt;p&gt; &quot;At last a well researched, well thought-out, comprehensive guide to Perl style. Instead of each of us developing our own, we can learn good practices from one of Perl's most prolific and experienced authors. I recommend this book to anyone who prefers getting on with the job rather than going back and fixing errors caused by syntax and poor style issues.&quot; &lt;p&gt; -- Jacinta Richardson &lt;p&gt; &quot;If you care about programming in any language read this book. Even if you don't intend to follow all of the practices, thinking through your style will improve it.&quot;&lt;p&gt; -- Steven Lembark &lt;p&gt; &quot;The Perl community's best author is back with another outstanding book. There has never been a comprehensive reference on high quality Perl coding and style until &quot;Perl Best Practices,&quot; This book fills a large gap in every Perl bookshelf.&quot; &lt;p&gt; -- Uri Guttman</p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p>]]>
  </description>
  <published>2005</published>
</book>

    <rating>5</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
        <shelf name="read" />
          </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at>Mon May 22 00:00:00 -0700 2006</read_at>
  <date_added>Sun Jun 14 17:45:13 -0700 2009</date_added>
  <date_updated>Sun Jun 14 17:45:31 -0700 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/59663230]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/59663230]]></link>
</review>
      <review>
  <id>59062782</id>
    <user>
    <id>2401314</id>
    <name><![CDATA[Kartik]]></name>
    <location><![CDATA[Newark, DE]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/2401314-kartik-subbarao]]></link>
    <image_url><![CDATA[http://photo.goodreads.com/users/1244596132p3/2401314.jpg]]></image_url>
    <small_image_url><![CDATA[http://photo.goodreads.com/users/1244596132p2/2401314.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">86379</id>
  <isbn>0596001738</isbn>
  <isbn13>9780596001735</isbn13>
  <text_reviews_count type="integer">4</text_reviews_count>
  <title>
    <![CDATA[Perl Best Practices]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1171067732m/86379.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1171067732s/86379.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/86379.Perl_Best_Practices</link>
  <average_rating>4.34</average_rating>
  <ratings_count>41</ratings_count>
  <description>
    <![CDATA[&lt;DIV&gt;Many programmers code by instinct, relying on convenient habits or a &quot;style&quot; they picked up early on. They aren't conscious of all the choices they make, like how they format their source, the names they use for variables, or the kinds of loops they use. They're focused entirely on problems they're solving, solutions they're creating, and algorithms they're implementing. So they write code in the way that seems natural, that happens intuitively, and that feels good. <p> But if you're serious about your profession, intuition isn't enough. &quot;Perl Best Practices&quot; author Damian Conway explains that rules, conventions, standards, and practices not only help programmers communicate and coordinate with one another, they also provide a reliable framework for thinking about problems, and a common language for expressing solutions. This is especially critical in Perl, because the language is designed to offer many ways to accomplish the same task, and consequently it supports many incompatible dialects. <p> With a good dose of Aussie humor, Dr. Conway (familiar to many in the Perl community) offers 256 guidelines on the art of coding to help you write better Perl code--in fact, the best Perl code you possibly can. The guidelines cover code layout, naming conventions, choice of data and control structures, program decomposition, interface design and implementation, modularity, object orientation, error handling, testing, and debugging. <p> They're designed to work together to produce code that is clear, robust, efficient, maintainable, and concise, but Dr. Conway doesn't pretend that this is the one true universal and unequivocal set of best practices. Instead, &quot;Perl Best Practices&quot; offerscoherent and widely applicable suggestions based on real-world experience of how code is actually written, rather than on someone's ivory-tower theories on how<p> software ought to be created. <p> Most of all, &quot;Perl Best Practices&quot; offers guidelines that actually work, and that many developers around the world are already using. Much like Perl itself, these guidelines are about helping you to get your job done, without getting in the way. <p> Praise for &quot;Perl Best Practices&quot; from Perl community members: <p> &quot;As a manager of a large Perl project, I'd ensure that every member of my team has a copy of &quot;Perl Best Practices&quot; on their desk, and use it as the basis for an in-house style guide.&quot; <p> -- Randal Schwartz <p> &quot;There are no more excuses for writing bad Perl programs. All levels of Perl programmer will be more productive after reading this book.&quot; <p> -- Peter Scott <p> &quot;&quot;Perl Best Practices&quot; will be the next big important book in the evolution of Perl. The ideas and practices Damian lays down will help bring Perl out from under the embarrassing heading of &quot;scripting languages.&quot; Many of us have known Perl is a real programming language, worthy of all the tasks normally delegated to Java and C++. With Perl Best Practices, Damian shows specifically how and why, so everyone else can see, too.&quot; <p> -- Andy Lester <p> &quot;Damian's done what many thought impossible: show how to build large, maintainable Perl applications, while still letting Perl be the powerful, expressive language that programmers have loved for years.&quot; <p> -- Bill Odom <p> &quot;Finally, a means to bring lasting order to the process and product of real Perl development teams.&quot; <p> -- Andrew Sundstrom <p>&quot;&quot;Perl Best Practices&quot; provides a valuable education in how to write robust, maintainable Perl, and is a definitive citation source when coaching other programmers.&quot; <p> -- Bennett Todd <p> &quot;I've been teaching Perl for years, and find the same question keeps being asked: Where can I find a reference for writing reusable, maintainable Perl code? Finally I have a decent answer.&quot; <p> -- Paul Fenwick &lt;p&gt; &quot;At last a well researched, well thought-out, comprehensive guide to Perl style. Instead of each of us developing our own, we can learn good practices from one of Perl's most prolific and experienced authors. I recommend this book to anyone who prefers getting on with the job rather than going back and fixing errors caused by syntax and poor style issues.&quot; &lt;p&gt; -- Jacinta Richardson &lt;p&gt; &quot;If you care about programming in any language read this book. Even if you don't intend to follow all of the practices, thinking through your style will improve it.&quot;&lt;p&gt; -- Steven Lembark &lt;p&gt; &quot;The Perl community's best author is back with another outstanding book. There has never been a comprehensive reference on high quality Perl coding and style until &quot;Perl Best Practices,&quot; This book fills a large gap in every Perl bookshelf.&quot; &lt;p&gt; -- Uri Guttman</p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p>]]>
  </description>
  <published>2005</published>
</book>

    <rating>0</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
        <shelf name="read" />
            <shelf name="perl" />
        <shelf name="programming" />
        <shelf name="technology" />
      </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Tue Jun 09 17:03:35 -0700 2009</date_added>
  <date_updated>Tue Jun 09 17:03:35 -0700 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/59062782]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/59062782]]></link>
</review>
      <review>
  <id>56957352</id>
    <user>
    <id>2344396</id>
    <name><![CDATA[Evan]]></name>
    <location><![CDATA[Seattle, WA]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/2344396-evan-dower]]></link>
    <image_url><![CDATA[http://photo.goodreads.com/users/1243005745p3/2344396.jpg]]></image_url>
    <small_image_url><![CDATA[http://photo.goodreads.com/users/1243005745p2/2344396.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">86379</id>
  <isbn>0596001738</isbn>
  <isbn13>9780596001735</isbn13>
  <text_reviews_count type="integer">4</text_reviews_count>
  <title>
    <![CDATA[Perl Best Practices]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1171067732m/86379.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1171067732s/86379.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/86379.Perl_Best_Practices</link>
  <average_rating>4.34</average_rating>
  <ratings_count>41</ratings_count>
  <description>
    <![CDATA[&lt;DIV&gt;Many programmers code by instinct, relying on convenient habits or a &quot;style&quot; they picked up early on. They aren't conscious of all the choices they make, like how they format their source, the names they use for variables, or the kinds of loops they use. They're focused entirely on problems they're solving, solutions they're creating, and algorithms they're implementing. So they write code in the way that seems natural, that happens intuitively, and that feels good. <p> But if you're serious about your profession, intuition isn't enough. &quot;Perl Best Practices&quot; author Damian Conway explains that rules, conventions, standards, and practices not only help programmers communicate and coordinate with one another, they also provide a reliable framework for thinking about problems, and a common language for expressing solutions. This is especially critical in Perl, because the language is designed to offer many ways to accomplish the same task, and consequently it supports many incompatible dialects. <p> With a good dose of Aussie humor, Dr. Conway (familiar to many in the Perl community) offers 256 guidelines on the art of coding to help you write better Perl code--in fact, the best Perl code you possibly can. The guidelines cover code layout, naming conventions, choice of data and control structures, program decomposition, interface design and implementation, modularity, object orientation, error handling, testing, and debugging. <p> They're designed to work together to produce code that is clear, robust, efficient, maintainable, and concise, but Dr. Conway doesn't pretend that this is the one true universal and unequivocal set of best practices. Instead, &quot;Perl Best Practices&quot; offerscoherent and widely applicable suggestions based on real-world experience of how code is actually written, rather than on someone's ivory-tower theories on how<p> software ought to be created. <p> Most of all, &quot;Perl Best Practices&quot; offers guidelines that actually work, and that many developers around the world are already using. Much like Perl itself, these guidelines are about helping you to get your job done, without getting in the way. <p> Praise for &quot;Perl Best Practices&quot; from Perl community members: <p> &quot;As a manager of a large Perl project, I'd ensure that every member of my team has a copy of &quot;Perl Best Practices&quot; on their desk, and use it as the basis for an in-house style guide.&quot; <p> -- Randal Schwartz <p> &quot;There are no more excuses for writing bad Perl programs. All levels of Perl programmer will be more productive after reading this book.&quot; <p> -- Peter Scott <p> &quot;&quot;Perl Best Practices&quot; will be the next big important book in the evolution of Perl. The ideas and practices Damian lays down will help bring Perl out from under the embarrassing heading of &quot;scripting languages.&quot; Many of us have known Perl is a real programming language, worthy of all the tasks normally delegated to Java and C++. With Perl Best Practices, Damian shows specifically how and why, so everyone else can see, too.&quot; <p> -- Andy Lester <p> &quot;Damian's done what many thought impossible: show how to build large, maintainable Perl applications, while still letting Perl be the powerful, expressive language that programmers have loved for years.&quot; <p> -- Bill Odom <p> &quot;Finally, a means to bring lasting order to the process and product of real Perl development teams.&quot; <p> -- Andrew Sundstrom <p>&quot;&quot;Perl Best Practices&quot; provides a valuable education in how to write robust, maintainable Perl, and is a definitive citation source when coaching other programmers.&quot; <p> -- Bennett Todd <p> &quot;I've been teaching Perl for years, and find the same question keeps being asked: Where can I find a reference for writing reusable, maintainable Perl code? Finally I have a decent answer.&quot; <p> -- Paul Fenwick &lt;p&gt; &quot;At last a well researched, well thought-out, comprehensive guide to Perl style. Instead of each of us developing our own, we can learn good practices from one of Perl's most prolific and experienced authors. I recommend this book to anyone who prefers getting on with the job rather than going back and fixing errors caused by syntax and poor style issues.&quot; &lt;p&gt; -- Jacinta Richardson &lt;p&gt; &quot;If you care about programming in any language read this book. Even if you don't intend to follow all of the practices, thinking through your style will improve it.&quot;&lt;p&gt; -- Steven Lembark &lt;p&gt; &quot;The Perl community's best author is back with another outstanding book. There has never been a comprehensive reference on high quality Perl coding and style until &quot;Perl Best Practices,&quot; This book fills a large gap in every Perl bookshelf.&quot; &lt;p&gt; -- Uri Guttman</p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p>]]>
  </description>
  <published>2005</published>
</book>

    <rating>0</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
            <shelf name="computer-science" />
        <shelf name="to-read" />
      </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Fri May 22 08:24:40 -0700 2009</date_added>
  <date_updated>Fri May 22 08:32:38 -0700 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/56957352]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/56957352]]></link>
</review>
      <review>
  <id>53835869</id>
    <user>
    <id>2253708</id>
    <name><![CDATA[Chris]]></name>
    <location><![CDATA[The United States]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/2253708-chris-n]]></link>
    <image_url><![CDATA[http://www.goodreads.com/images/nophoto-U-111x148.jpg]]></image_url>
    <small_image_url><![CDATA[http://www.goodreads.com/images/nophoto-U-50x66.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">86379</id>
  <isbn>0596001738</isbn>
  <isbn13>9780596001735</isbn13>
  <text_reviews_count type="integer">4</text_reviews_count>
  <title>
    <![CDATA[Perl Best Practices]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1171067732m/86379.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1171067732s/86379.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/86379.Perl_Best_Practices</link>
  <average_rating>4.34</average_rating>
  <ratings_count>41</ratings_count>
  <description>
    <![CDATA[&lt;DIV&gt;Many programmers code by instinct, relying on convenient habits or a &quot;style&quot; they picked up early on. They aren't conscious of all the choices they make, like how they format their source, the names they use for variables, or the kinds of loops they use. They're focused entirely on problems they're solving, solutions they're creating, and algorithms they're implementing. So they write code in the way that seems natural, that happens intuitively, and that feels good. <p> But if you're serious about your profession, intuition isn't enough. &quot;Perl Best Practices&quot; author Damian Conway explains that rules, conventions, standards, and practices not only help programmers communicate and coordinate with one another, they also provide a reliable framework for thinking about problems, and a common language for expressing solutions. This is especially critical in Perl, because the language is designed to offer many ways to accomplish the same task, and consequently it supports many incompatible dialects. <p> With a good dose of Aussie humor, Dr. Conway (familiar to many in the Perl community) offers 256 guidelines on the art of coding to help you write better Perl code--in fact, the best Perl code you possibly can. The guidelines cover code layout, naming conventions, choice of data and control structures, program decomposition, interface design and implementation, modularity, object orientation, error handling, testing, and debugging. <p> They're designed to work together to produce code that is clear, robust, efficient, maintainable, and concise, but Dr. Conway doesn't pretend that this is the one true universal and unequivocal set of best practices. Instead, &quot;Perl Best Practices&quot; offerscoherent and widely applicable suggestions based on real-world experience of how code is actually written, rather than on someone's ivory-tower theories on how<p> software ought to be created. <p> Most of all, &quot;Perl Best Practices&quot; offers guidelines that actually work, and that many developers around the world are already using. Much like Perl itself, these guidelines are about helping you to get your job done, without getting in the way. <p> Praise for &quot;Perl Best Practices&quot; from Perl community members: <p> &quot;As a manager of a large Perl project, I'd ensure that every member of my team has a copy of &quot;Perl Best Practices&quot; on their desk, and use it as the basis for an in-house style guide.&quot; <p> -- Randal Schwartz <p> &quot;There are no more excuses for writing bad Perl programs. All levels of Perl programmer will be more productive after reading this book.&quot; <p> -- Peter Scott <p> &quot;&quot;Perl Best Practices&quot; will be the next big important book in the evolution of Perl. The ideas and practices Damian lays down will help bring Perl out from under the embarrassing heading of &quot;scripting languages.&quot; Many of us have known Perl is a real programming language, worthy of all the tasks normally delegated to Java and C++. With Perl Best Practices, Damian shows specifically how and why, so everyone else can see, too.&quot; <p> -- Andy Lester <p> &quot;Damian's done what many thought impossible: show how to build large, maintainable Perl applications, while still letting Perl be the powerful, expressive language that programmers have loved for years.&quot; <p> -- Bill Odom <p> &quot;Finally, a means to bring lasting order to the process and product of real Perl development teams.&quot; <p> -- Andrew Sundstrom <p>&quot;&quot;Perl Best Practices&quot; provides a valuable education in how to write robust, maintainable Perl, and is a definitive citation source when coaching other programmers.&quot; <p> -- Bennett Todd <p> &quot;I've been teaching Perl for years, and find the same question keeps being asked: Where can I find a reference for writing reusable, maintainable Perl code? Finally I have a decent answer.&quot; <p> -- Paul Fenwick &lt;p&gt; &quot;At last a well researched, well thought-out, comprehensive guide to Perl style. Instead of each of us developing our own, we can learn good practices from one of Perl's most prolific and experienced authors. I recommend this book to anyone who prefers getting on with the job rather than going back and fixing errors caused by syntax and poor style issues.&quot; &lt;p&gt; -- Jacinta Richardson &lt;p&gt; &quot;If you care about programming in any language read this book. Even if you don't intend to follow all of the practices, thinking through your style will improve it.&quot;&lt;p&gt; -- Steven Lembark &lt;p&gt; &quot;The Perl community's best author is back with another outstanding book. There has never been a comprehensive reference on high quality Perl coding and style until &quot;Perl Best Practices,&quot; This book fills a large gap in every Perl bookshelf.&quot; &lt;p&gt; -- Uri Guttman</p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p>]]>
  </description>
  <published>2005</published>
</book>

    <rating>0</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
        <shelf name="read" />
          </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Fri Apr 24 11:31:10 -0700 2009</date_added>
  <date_updated>Fri Apr 24 11:31:10 -0700 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/53835869]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/53835869]]></link>
</review>
      <review>
  <id>53648833</id>
    <user>
    <id>2247101</id>
    <name><![CDATA[Ab]]></name>
    <location><![CDATA[Mountain View, CA]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/2247101-ab]]></link>
    <image_url><![CDATA[http://www.goodreads.com/images/nophoto-U-111x148.jpg]]></image_url>
    <small_image_url><![CDATA[http://www.goodreads.com/images/nophoto-U-50x66.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">86379</id>
  <isbn>0596001738</isbn>
  <isbn13>9780596001735</isbn13>
  <text_reviews_count type="integer">4</text_reviews_count>
  <title>
    <![CDATA[Perl Best Practices]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1171067732m/86379.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1171067732s/86379.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/86379.Perl_Best_Practices</link>
  <average_rating>4.34</average_rating>
  <ratings_count>41</ratings_count>
  <description>
    <![CDATA[&lt;DIV&gt;Many programmers code by instinct, relying on convenient habits or a &quot;style&quot; they picked up early on. They aren't conscious of all the choices they make, like how they format their source, the names they use for variables, or the kinds of loops they use. They're focused entirely on problems they're solving, solutions they're creating, and algorithms they're implementing. So they write code in the way that seems natural, that happens intuitively, and that feels good. <p> But if you're serious about your profession, intuition isn't enough. &quot;Perl Best Practices&quot; author Damian Conway explains that rules, conventions, standards, and practices not only help programmers communicate and coordinate with one another, they also provide a reliable framework for thinking about problems, and a common language for expressing solutions. This is especially critical in Perl, because the language is designed to offer many ways to accomplish the same task, and consequently it supports many incompatible dialects. <p> With a good dose of Aussie humor, Dr. Conway (familiar to many in the Perl community) offers 256 guidelines on the art of coding to help you write better Perl code--in fact, the best Perl code you possibly can. The guidelines cover code layout, naming conventions, choice of data and control structures, program decomposition, interface design and implementation, modularity, object orientation, error handling, testing, and debugging. <p> They're designed to work together to produce code that is clear, robust, efficient, maintainable, and concise, but Dr. Conway doesn't pretend that this is the one true universal and unequivocal set of best practices. Instead, &quot;Perl Best Practices&quot; offerscoherent and widely applicable suggestions based on real-world experience of how code is actually written, rather than on someone's ivory-tower theories on how<p> software ought to be created. <p> Most of all, &quot;Perl Best Practices&quot; offers guidelines that actually work, and that many developers around the world are already using. Much like Perl itself, these guidelines are about helping you to get your job done, without getting in the way. <p> Praise for &quot;Perl Best Practices&quot; from Perl community members: <p> &quot;As a manager of a large Perl project, I'd ensure that every member of my team has a copy of &quot;Perl Best Practices&quot; on their desk, and use it as the basis for an in-house style guide.&quot; <p> -- Randal Schwartz <p> &quot;There are no more excuses for writing bad Perl programs. All levels of Perl programmer will be more productive after reading this book.&quot; <p> -- Peter Scott <p> &quot;&quot;Perl Best Practices&quot; will be the next big important book in the evolution of Perl. The ideas and practices Damian lays down will help bring Perl out from under the embarrassing heading of &quot;scripting languages.&quot; Many of us have known Perl is a real programming language, worthy of all the tasks normally delegated to Java and C++. With Perl Best Practices, Damian shows specifically how and why, so everyone else can see, too.&quot; <p> -- Andy Lester <p> &quot;Damian's done what many thought impossible: show how to build large, maintainable Perl applications, while still letting Perl be the powerful, expressive language that programmers have loved for years.&quot; <p> -- Bill Odom <p> &quot;Finally, a means to bring lasting order to the process and product of real Perl development teams.&quot; <p> -- Andrew Sundstrom <p>&quot;&quot;Perl Best Practices&quot; provides a valuable education in how to write robust, maintainable Perl, and is a definitive citation source when coaching other programmers.&quot; <p> -- Bennett Todd <p> &quot;I've been teaching Perl for years, and find the same question keeps being asked: Where can I find a reference for writing reusable, maintainable Perl code? Finally I have a decent answer.&quot; <p> -- Paul Fenwick &lt;p&gt; &quot;At last a well researched, well thought-out, comprehensive guide to Perl style. Instead of each of us developing our own, we can learn good practices from one of Perl's most prolific and experienced authors. I recommend this book to anyone who prefers getting on with the job rather than going back and fixing errors caused by syntax and poor style issues.&quot; &lt;p&gt; -- Jacinta Richardson &lt;p&gt; &quot;If you care about programming in any language read this book. Even if you don't intend to follow all of the practices, thinking through your style will improve it.&quot;&lt;p&gt; -- Steven Lembark &lt;p&gt; &quot;The Perl community's best author is back with another outstanding book. There has never been a comprehensive reference on high quality Perl coding and style until &quot;Perl Best Practices,&quot; This book fills a large gap in every Perl bookshelf.&quot; &lt;p&gt; -- Uri Guttman</p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p>]]>
  </description>
  <published>2005</published>
</book>

    <rating>0</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
        <shelf name="read" />
          </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Wed Apr 22 16:36:00 -0700 2009</date_added>
  <date_updated>Wed Apr 22 16:36:00 -0700 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/53648833]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/53648833]]></link>
</review>
      <review>
  <id>53591858</id>
    <user>
    <id>760917</id>
    <name><![CDATA[Eugene]]></name>
    <location><![CDATA[Ukraine]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/760917-eugene]]></link>
    <image_url><![CDATA[http://www.goodreads.com/images/nophoto-U-111x148.jpg]]></image_url>
    <small_image_url><![CDATA[http://www.goodreads.com/images/nophoto-U-50x66.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">86379</id>
  <isbn>0596001738</isbn>
  <isbn13>9780596001735</isbn13>
  <text_reviews_count type="integer">4</text_reviews_count>
  <title>
    <![CDATA[Perl Best Practices]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1171067732m/86379.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1171067732s/86379.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/86379.Perl_Best_Practices</link>
  <average_rating>4.34</average_rating>
  <ratings_count>41</ratings_count>
  <description>
    <![CDATA[&lt;DIV&gt;Many programmers code by instinct, relying on convenient habits or a &quot;style&quot; they picked up early on. They aren't conscious of all the choices they make, like how they format their source, the names they use for variables, or the kinds of loops they use. They're focused entirely on problems they're solving, solutions they're creating, and algorithms they're implementing. So they write code in the way that seems natural, that happens intuitively, and that feels good. <p> But if you're serious about your profession, intuition isn't enough. &quot;Perl Best Practices&quot; author Damian Conway explains that rules, conventions, standards, and practices not only help programmers communicate and coordinate with one another, they also provide a reliable framework for thinking about problems, and a common language for expressing solutions. This is especially critical in Perl, because the language is designed to offer many ways to accomplish the same task, and consequently it supports many incompatible dialects. <p> With a good dose of Aussie humor, Dr. Conway (familiar to many in the Perl community) offers 256 guidelines on the art of coding to help you write better Perl code--in fact, the best Perl code you possibly can. The guidelines cover code layout, naming conventions, choice of data and control structures, program decomposition, interface design and implementation, modularity, object orientation, error handling, testing, and debugging. <p> They're designed to work together to produce code that is clear, robust, efficient, maintainable, and concise, but Dr. Conway doesn't pretend that this is the one true universal and unequivocal set of best practices. Instead, &quot;Perl Best Practices&quot; offerscoherent and widely applicable suggestions based on real-world experience of how code is actually written, rather than on someone's ivory-tower theories on how<p> software ought to be created. <p> Most of all, &quot;Perl Best Practices&quot; offers guidelines that actually work, and that many developers around the world are already using. Much like Perl itself, these guidelines are about helping you to get your job done, without getting in the way. <p> Praise for &quot;Perl Best Practices&quot; from Perl community members: <p> &quot;As a manager of a large Perl project, I'd ensure that every member of my team has a copy of &quot;Perl Best Practices&quot; on their desk, and use it as the basis for an in-house style guide.&quot; <p> -- Randal Schwartz <p> &quot;There are no more excuses for writing bad Perl programs. All levels of Perl programmer will be more productive after reading this book.&quot; <p> -- Peter Scott <p> &quot;&quot;Perl Best Practices&quot; will be the next big important book in the evolution of Perl. The ideas and practices Damian lays down will help bring Perl out from under the embarrassing heading of &quot;scripting languages.&quot; Many of us have known Perl is a real programming language, worthy of all the tasks normally delegated to Java and C++. With Perl Best Practices, Damian shows specifically how and why, so everyone else can see, too.&quot; <p> -- Andy Lester <p> &quot;Damian's done what many thought impossible: show how to build large, maintainable Perl applications, while still letting Perl be the powerful, expressive language that programmers have loved for years.&quot; <p> -- Bill Odom <p> &quot;Finally, a means to bring lasting order to the process and product of real Perl development teams.&quot; <p> -- Andrew Sundstrom <p>&quot;&quot;Perl Best Practices&quot; provides a valuable education in how to write robust, maintainable Perl, and is a definitive citation source when coaching other programmers.&quot; <p> -- Bennett Todd <p> &quot;I've been teaching Perl for years, and find the same question keeps being asked: Where can I find a reference for writing reusable, maintainable Perl code? Finally I have a decent answer.&quot; <p> -- Paul Fenwick &lt;p&gt; &quot;At last a well researched, well thought-out, comprehensive guide to Perl style. Instead of each of us developing our own, we can learn good practices from one of Perl's most prolific and experienced authors. I recommend this book to anyone who prefers getting on with the job rather than going back and fixing errors caused by syntax and poor style issues.&quot; &lt;p&gt; -- Jacinta Richardson &lt;p&gt; &quot;If you care about programming in any language read this book. Even if you don't intend to follow all of the practices, thinking through your style will improve it.&quot;&lt;p&gt; -- Steven Lembark &lt;p&gt; &quot;The Perl community's best author is back with another outstanding book. There has never been a comprehensive reference on high quality Perl coding and style until &quot;Perl Best Practices,&quot; This book fills a large gap in every Perl bookshelf.&quot; &lt;p&gt; -- Uri Guttman</p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p>]]>
  </description>
  <published>2005</published>
</book>

    <rating>0</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
        <shelf name="read" />
          </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Wed Apr 22 09:13:01 -0700 2009</date_added>
  <date_updated>Wed Apr 22 09:13:01 -0700 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/53591858]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/53591858]]></link>
</review>
      <review>
  <id>52215173</id>
    <user>
    <id>349649</id>
    <name><![CDATA[Jennifer]]></name>
    <location><![CDATA[The United States]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/349649-jennifer]]></link>
    <image_url><![CDATA[http://www.goodreads.com/images/nophoto-F-111x148.jpg]]></image_url>
    <small_image_url><![CDATA[http://www.goodreads.com/images/nophoto-F-50x66.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">86379</id>
  <isbn>0596001738</isbn>
  <isbn13>9780596001735</isbn13>
  <text_reviews_count type="integer">4</text_reviews_count>
  <title>
    <![CDATA[Perl Best Practices]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1171067732m/86379.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1171067732s/86379.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/86379.Perl_Best_Practices</link>
  <average_rating>4.34</average_rating>
  <ratings_count>41</ratings_count>
  <description>
    <![CDATA[&lt;DIV&gt;Many programmers code by instinct, relying on convenient habits or a &quot;style&quot; they picked up early on. They aren't conscious of all the choices they make, like how they format their source, the names they use for variables, or the kinds of loops they use. They're focused entirely on problems they're solving, solutions they're creating, and algorithms they're implementing. So they write code in the way that seems natural, that happens intuitively, and that feels good. <p> But if you're serious about your profession, intuition isn't enough. &quot;Perl Best Practices&quot; author Damian Conway explains that rules, conventions, standards, and practices not only help programmers communicate and coordinate with one another, they also provide a reliable framework for thinking about problems, and a common language for expressing solutions. This is especially critical in Perl, because the language is designed to offer many ways to accomplish the same task, and consequently it supports many incompatible dialects. <p> With a good dose of Aussie humor, Dr. Conway (familiar to many in the Perl community) offers 256 guidelines on the art of coding to help you write better Perl code--in fact, the best Perl code you possibly can. The guidelines cover code layout, naming conventions, choice of data and control structures, program decomposition, interface design and implementation, modularity, object orientation, error handling, testing, and debugging. <p> They're designed to work together to produce code that is clear, robust, efficient, maintainable, and concise, but Dr. Conway doesn't pretend that this is the one true universal and unequivocal set of best practices. Instead, &quot;Perl Best Practices&quot; offerscoherent and widely applicable suggestions based on real-world experience of how code is actually written, rather than on someone's ivory-tower theories on how<p> software ought to be created. <p> Most of all, &quot;Perl Best Practices&quot; offers guidelines that actually work, and that many developers around the world are already using. Much like Perl itself, these guidelines are about helping you to get your job done, without getting in the way. <p> Praise for &quot;Perl Best Practices&quot; from Perl community members: <p> &quot;As a manager of a large Perl project, I'd ensure that every member of my team has a copy of &quot;Perl Best Practices&quot; on their desk, and use it as the basis for an in-house style guide.&quot; <p> -- Randal Schwartz <p> &quot;There are no more excuses for writing bad Perl programs. All levels of Perl programmer will be more productive after reading this book.&quot; <p> -- Peter Scott <p> &quot;&quot;Perl Best Practices&quot; will be the next big important book in the evolution of Perl. The ideas and practices Damian lays down will help bring Perl out from under the embarrassing heading of &quot;scripting languages.&quot; Many of us have known Perl is a real programming language, worthy of all the tasks normally delegated to Java and C++. With Perl Best Practices, Damian shows specifically how and why, so everyone else can see, too.&quot; <p> -- Andy Lester <p> &quot;Damian's done what many thought impossible: show how to build large, maintainable Perl applications, while still letting Perl be the powerful, expressive language that programmers have loved for years.&quot; <p> -- Bill Odom <p> &quot;Finally, a means to bring lasting order to the process and product of real Perl development teams.&quot; <p> -- Andrew Sundstrom <p>&quot;&quot;Perl Best Practices&quot; provides a valuable education in how to write robust, maintainable Perl, and is a definitive citation source when coaching other programmers.&quot; <p> -- Bennett Todd <p> &quot;I've been teaching Perl for years, and find the same question keeps being asked: Where can I find a reference for writing reusable, maintainable Perl code? Finally I have a decent answer.&quot; <p> -- Paul Fenwick &lt;p&gt; &quot;At last a well researched, well thought-out, comprehensive guide to Perl style. Instead of each of us developing our own, we can learn good practices from one of Perl's most prolific and experienced authors. I recommend this book to anyone who prefers getting on with the job rather than going back and fixing errors caused by syntax and poor style issues.&quot; &lt;p&gt; -- Jacinta Richardson &lt;p&gt; &quot;If you care about programming in any language read this book. Even if you don't intend to follow all of the practices, thinking through your style will improve it.&quot;&lt;p&gt; -- Steven Lembark &lt;p&gt; &quot;The Perl community's best author is back with another outstanding book. There has never been a comprehensive reference on high quality Perl coding and style until &quot;Perl Best Practices,&quot; This book fills a large gap in every Perl bookshelf.&quot; &lt;p&gt; -- Uri Guttman</p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p></p>]]>
  </description>
  <published>2005</published>
</book>

    <rating>0</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
            <shelf name="computer" />
        <shelf name="perl" />
        <shelf name="to-read" />
        <shelf name="work-related" />
      </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Fri Apr 10 12:49:11 -0700 2009</date_added>
  <date_updated>Fri Apr 10 12:49:11 -0700 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/52215173]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/52215173]]></link>
</review>
    </reviews>
  <popular_shelves>
          <shelf name="to-read" />
          <shelf name="technical" />
          <shelf name="perl" />
          <shelf name="technology" />
          <shelf name="programming" />
          <shelf name="computers" />
          <shelf name="nonfiction" />
          <shelf name="college-university-textbooks" />
          <shelf name="sys-admin" />
      </popular_shelves>
  <book_links>
    <book_link>
  <id>8</id>
  <name><![CDATA[WorldCat]]></name>
  <link>http://www.goodreads.com/book_link/follow/8?book_id=86379</link>
</book_link>
  </book_links>
</book>
</GoodreadsResponse>