There's also an interesting-looking talk that he seems to have done on Idiotic Perl. I think it would be really interesting if that would be expanded into a book. The first few chapters might address really bad code (as he's already done), and later chapters could go on to address the kinds of things BastardOperator mentioned in Perl secrets. The middle bit would just be stolen from Ovid ;)

Some might wonder who would buy a book of bad programming practices instead of something like Effective Perl Programming. The answer, of course, is anyone who delights finding flaws: the people who talk about how something is historically inaccurate or against the laws of physics during a movie, the people who laugh at typos in books, the people who highlight all the spelling errors I've made...

Well, I'd buy a copy (I'm the one who points out historical inaccuracies in movies).

Update: Ovid, of course I meant your comments about showing the dangers of bad code! :P Just look at where the link is pointing...

---

---

• 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> <u> <ul>

• 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 intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.