I was going to go through all 256 and state briefly what I thought of each one. In many cases, of course, I would heartily agree. There were some trivial errors that I wanted to point out. And there were some that I disagreed with. I thought it would be interesting to be able to give a concrete illustration of what Damian was talking about in the introduction.
But, given that the point of the book is the set of 256 best practices that Damian put quite a bit of thought into, quoting all of them seems to me to be a little more than fair use would allow. You might disagree, but TheDamian and Allison Randal both thought that reasonable, and both said that I needed to ask firstname.lastname@example.org for permission because O'Reilly is the copyright holder.
The permission that I got from O'Reilly was to be allowed to quote 20 publically. Which suggests that the copyright holder, as well, would consider 256 to be copyright infringement, and would definitely be unhappy about it.
Before I got that permission Allison had suggested that I write the article I wanted to write, and send that to email@example.com. Because with a concrete idea of what I would write, it would be easier for them to decide to say, "Yes." I'm still debating doing that, but it is harder to get motivated now that I know that there is a good chance that I'll get a "no" in the end.
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link or
or How to display code and escape characters
are good places to start.