<?xml version='1.0' encoding='utf-8' ?>
<!--  If you are running a bot please visit this policy page outlining rules you must respect. http://www.livejournal.com/bots/  -->
<rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/'>
<channel>
  <title>The Perl Review</title>
  <link>http://perl-review.livejournal.com/</link>
  <description>The Perl Review - LiveJournal.com</description>
  <lastBuildDate>Thu, 20 Mar 2008 12:11:51 GMT</lastBuildDate>
  <generator>LiveJournal / LiveJournal.com</generator>
  <lj:journal>perl_review</lj:journal>
  <lj:journaltype>personal</lj:journaltype>
<item>
  <guid isPermaLink='true'>http://perl-review.livejournal.com/22545.html</guid>
  <pubDate>Thu, 20 Mar 2008 12:11:51 GMT</pubDate>
  <title>The Perl Review, Spring 2008</title>
  <link>http://perl-review.livejournal.com/22545.html</link>
  <description>&lt;table&gt;
&lt;tr&gt;
&lt;td class=&quot;v1i3&quot; valign=&quot;bottom&quot; align=&quot;center&quot; style=&quot;vertical-align: middle; align: center&quot;&gt;
&lt;b&gt;Issue 4.2 (Spring 2008)&lt;/b&gt; &lt;br /&gt;

&lt;a href=&quot;http://www.theperlreview.com/Subscribers/ThePerlReview-v4i2.pdf&quot;&gt;&lt;img src=&quot;http://www.theperlreview.com/Images/covers/v4i2-cover.png&quot; border=&quot;0&quot; width=&quot;126&quot; height=&quot;165&quot;&gt;&lt;/a&gt;&lt;/td&gt;
&lt;td valign=&quot;bottom&quot; align=&quot;center&quot; style=&quot;vertical-align: middle; align: center&quot;&gt;

	&lt;p&gt;&lt;a href=&quot;http://www.theperlreview.com/SamplePages/ThePerlReview-v4i2.toc.pdf&quot;&gt;Table of Contents&lt;/a&gt;&lt;/p&gt;

	&lt;p&gt;	
	Compiling My Own perl&amp;mdash;brian d foy (&lt;a href=&quot;http://www.theperlreview.com/SamplePages/ThePerlReview-v4i2.p8.pdf&quot;&gt;first page&lt;/a&gt;)&lt;br /&gt;
	FMTIEWTK About Closures&amp;mdash;Johan Lodin (&lt;a href=&quot;http://www.theperlreview.com/SamplePages/ThePerlReview-v4i2.p11.pdf&quot;&gt;first page&lt;/a&gt;)&lt;br /&gt;

	Expecting Perl&amp;mdash;Mark Schoonover (&lt;a href=&quot;/http://www.theperlreview.comSamplePages/ThePerlReview-v4i2.p18.pdf&quot;&gt;first page&lt;/a&gt;)&lt;br /&gt;
	Perl and Undecidability&amp;mdash;Jeffrey Kegler (&lt;a href=&quot;http://www.theperlreview.com/SamplePages/ThePerlReview-v4i2.p21.pdf&quot;&gt;first page&lt;/a&gt;)&lt;br /&gt;
	The Year in Perl, 2007&amp;mdash;brian d foy (&lt;a href=&quot;http://www.theperlreview.com/SamplePages/ThePerlReview-v4i2.p26.pdf&quot;&gt;first page&lt;/a&gt;)&lt;br /&gt;

	&lt;/p&gt;

	&lt;/td&gt;
&lt;/tr&gt;
&lt;/table&gt;</description>
  <comments>http://perl-review.livejournal.com/22545.html</comments>
  <lj:security>public</lj:security>
</item>
<item>
  <guid isPermaLink='true'>http://perl-review.livejournal.com/22493.html</guid>
  <pubDate>Thu, 20 Mar 2008 12:05:35 GMT</pubDate>
  <title>The Perl Review, Fall 2007</title>
  <link>http://perl-review.livejournal.com/22493.html</link>
  <description>&lt;table&gt;
&lt;tr&gt;
&lt;td class=&quot;v1i3&quot; valign=&quot;bottom&quot; align=&quot;center&quot; style=&quot;vertical-align: middle; align: center&quot;&gt;
&lt;b&gt;Issue 4.0 (Fall 2007)&lt;/b&gt; &lt;br /&gt;
&lt;a href=&quot;http://www.theperlreview.com/Subscribers/ThePerlReview-v4i0.pdf&quot;&gt;&lt;img src=&quot;http://www.theperlreview.com/Images/covers/v4i0-cover.png&quot; border=&quot;0&quot; width=&quot;126&quot; height=&quot;165&quot;&gt;&lt;/a&gt;&lt;/td&gt;
&lt;td valign=&quot;bottom&quot; align=&quot;center&quot; style=&quot;vertical-align: middle; align: center&quot;&gt;

	&lt;p&gt;&lt;a href=&quot;http://www.theperlreview.com/SamplePages/ThePerlReview-v4i0.toc.pdf&quot;&gt;Table of Contents&lt;/a&gt;&lt;/p&gt;

	&lt;p&gt;	
	Templating My Output&amp;mdash;Alberto Manuel Sim&amp;otilde;es (&lt;a href=&quot;http://www.theperlreview.com/SamplePages/ThePerlReview-v4i0.p5.pdf&quot;&gt;first page&lt;/a&gt;)&lt;br /&gt;
	Making My Own CPAN&amp;mdash;brian d foy (&lt;a href=&quot;http://www.theperlreview.com/SamplePages/ThePerlReview-v4i0.p9.pdf&quot;&gt;first page&lt;/a&gt;)&lt;br /&gt;
	Programming Parrot&amp;mdash;Jonathan Scott Duff (&lt;a href=&quot;http://www.theperlreview.com/SamplePages/ThePerlReview-v4i0.p18.pdf&quot;&gt;first page&lt;/a&gt;)&lt;br /&gt;

	Komodo Test Drive&amp;mdash;Jim Brandt (&lt;a href=&quot;http://www.theperlreview.com/SamplePages/ThePerlReview-v4i0.p24.pdf&quot;&gt;first page&lt;/a&gt;)&lt;br /&gt;
	Named Captures in Perl 5.9.5&amp;mdash;brian d foy (&lt;a href=&quot;http://www.theperlreview.com/SamplePages/ThePerlReview-v4i0.p30.pdf&quot;&gt;first page&lt;/a&gt;)&lt;br /&gt;
	&lt;/p&gt;

	&lt;/td&gt;

&lt;/tr&gt;
&lt;/table&gt;</description>
  <comments>http://perl-review.livejournal.com/22493.html</comments>
  <lj:security>public</lj:security>
</item>
<item>
  <guid isPermaLink='true'>http://perl-review.livejournal.com/22208.html</guid>
  <pubDate>Thu, 20 Mar 2008 12:03:08 GMT</pubDate>
  <title>The Perl Review, Winter 2007</title>
  <link>http://perl-review.livejournal.com/22208.html</link>
  <description>&lt;table&gt;
&lt;tr&gt;
&lt;td class=&quot;v1i3&quot; valign=&quot;bottom&quot; align=&quot;center&quot; style=&quot;vertical-align: middle; align: center&quot;&gt;
&lt;b&gt;Issue 4.1 (Winter 2007)&lt;/b&gt; &lt;br /&gt;
&lt;a href=&quot;http://www.theperlreview.com/Subscribers/ThePerlReview-v4i1.pdf&quot;&gt;&lt;img src=&quot;http://www.theperlreview.com/Images/covers/v4i1-cover.png&quot; border=&quot;0&quot; width=&quot;126&quot; height=&quot;165&quot;&gt;&lt;/a&gt;&lt;/td&gt;
&lt;td valign=&quot;bottom&quot; align=&quot;center&quot; style=&quot;vertical-align: middle; align: center&quot;&gt;

	&lt;p&gt;&lt;a href=&quot;http://www.theperlreview.com/SamplePages/ThePerlReview-v4i1.toc.pdf&quot;&gt;Table of Contents&lt;/a&gt;&lt;/p&gt;

	&lt;p&gt;	
	Simple Web Access&amp;mdash;Alberto Manuel Sim&amp;otilde;es (&lt;a href=&quot;http://www.theperlreview.com/SamplePages/ThePerlReview-v4i1.p5.pdf&quot;&gt;first page&lt;/a&gt;)&lt;br /&gt;
	Parrot Status Report&amp;mdash;Jonathan Scott Duff (&lt;a href=&quot;http://www.theperlreview.com/SamplePages/ThePerlReview-v4i1.p7.pdf&quot;&gt;first page&lt;/a&gt;)&lt;br /&gt;
	Mapping Op Codes&amp;mdash;Eric Maki (&lt;a href=&quot;http://www.theperlreview.com/SamplePages/ThePerlReview-v4i1.p10.pdf&quot;&gt;first page&lt;/a&gt;)&lt;br /&gt;

	CPANdeps&amp;mdash;David Cantrell (&lt;a href=&quot;http://www.theperlreview.com/SamplePages/ThePerlReview-v4i1.p18.pdf&quot;&gt;first page&lt;/a&gt;)&lt;br /&gt;
	HTML Slides&amp;mdash;Grant McLean (&lt;a href=&quot;http://www.theperlreview.com/SamplePages/ThePerlReview-v4i1.p22.pdf&quot;&gt;first page&lt;/a&gt;)&lt;br /&gt;
	Alter Egos&amp;mdash;Anno Siegel (&lt;a href=&quot;http://www.theperlreview.com/SamplePages/ThePerlReview-v4i1.p27.pdf&quot;&gt;first page&lt;/a&gt;)&lt;br /&gt;

	&lt;/p&gt;

	&lt;/td&gt;
&lt;/tr&gt;
&lt;/table&gt;</description>
  <comments>http://perl-review.livejournal.com/22208.html</comments>
  <lj:security>public</lj:security>
</item>
<item>
  <guid isPermaLink='true'>http://perl-review.livejournal.com/20665.html</guid>
  <pubDate>Mon, 13 Aug 2007 08:55:59 GMT</pubDate>
  <title>Perlcast interviews brian d foy about TPR 2.3</title>
  <link>http://perl-review.livejournal.com/20665.html</link>
  <description>&lt;a href=&quot;http://www.perlcast.com&quot;&gt;Perlcast&lt;/a&gt; interviews brian d foy about &lt;a href=&quot;http://perlcast.com/2006/06/09/brian-d-foy-on-tpr-23/&quot;&gt;The Perl Review version 2.3&lt;/a&gt;.</description>
  <comments>http://perl-review.livejournal.com/20665.html</comments>
  <lj:security>public</lj:security>
</item>
<item>
  <guid isPermaLink='true'>http://perl-review.livejournal.com/18693.html</guid>
  <pubDate>Mon, 13 Aug 2007 07:51:54 GMT</pubDate>
  <title>Found Perl, now a Flickr Photo Pool</title>
  <link>http://perl-review.livejournal.com/18693.html</link>
  <description>&lt;a href=&quot;http://www.theperlreview.com/Found/&quot;&gt;Found Perl&lt;/a&gt; is section of &lt;a href=&quot;http://www.theperlreview.com&quot;&gt;The Perl Review&apos;s website&lt;/a&gt; where we posted pictures of Perl paraphernalia or the word &quot;Perl&quot; in the wild. We started it a long time ago, and were very slow in updating it when people would send in photos.&lt;br /&gt;&lt;br /&gt;Now &quot;Found Perl&quot; is a &lt;a href=&quot;http://www.flickr.com/groups/492831@N22/pool/&quot;&gt;photo pool on Flickr&lt;/a&gt;. Instead of sending them to TPR, just add them to the pool.</description>
  <comments>http://perl-review.livejournal.com/18693.html</comments>
  <category>&quot;found perl&quot; &quot;the perl review&quot;</category>
  <lj:security>public</lj:security>
</item>
<item>
  <guid isPermaLink='true'>http://perl-review.livejournal.com/18648.html</guid>
  <pubDate>Mon, 13 Aug 2007 07:46:34 GMT</pubDate>
  <title>Schwern&apos;s Shirt, now on Flickr</title>
  <link>http://perl-review.livejournal.com/18648.html</link>
  <description>&lt;a href=&quot;http://www.theperlreview.com/&quot;&gt;The Perl Review&apos;s website&lt;/a&gt; has had a section on &lt;a href=&quot;http://www.theperlreview.com/Shirt&quot;&gt;Schwern&apos;s Shirt&lt;/a&gt;, the orange monstrosity that brian d foy bought at the charity auction for The Perl Foundation at the 2004 Open Source Convention.&lt;br /&gt;&lt;br /&gt;Now we&apos;ve moved the section of the website to a &lt;a href=&quot;http://www.flickr.com/groups/492853@N22/pool/&quot;&gt;Flickr group for Schwern&apos;s shirt&lt;/a&gt;. This way, anyone can add their photos of Schwern&apos;s shirt to the group. Instead of being infrequently updated on the website, people can add them as soon as they upload them to Flickr.&lt;br /&gt;&lt;br /&gt;If you don&apos;t have a Flickr account and don&apos;t want to create one, you can still send them to The Perl Review by mailing them to &lt;a href=&quot;mailto:editors@theperlreview.com&quot;&gt;editors@theperlreview.com&lt;/a&gt;.</description>
  <comments>http://perl-review.livejournal.com/18648.html</comments>
  <category>schwern&apos;s shirt</category>
  <category>the perl review</category>
  <lj:security>public</lj:security>
</item>
<item>
  <guid isPermaLink='true'>http://perl-review.livejournal.com/18403.html</guid>
  <pubDate>Tue, 04 Apr 2006 23:56:51 GMT</pubDate>
  <title>The Perl Review Date Format Challenge</title>
  <link>http://perl-review.livejournal.com/18403.html</link>
  <description>&lt;a href=&quot;http://www.perlmonks.org/index.pl?node_id=541244&quot;&gt;I just posted this challenge to Perlmonks&lt;/a&gt;, and it&apos;s the first TPR code challenge, I guess:&lt;br /&gt;&lt;br /&gt;&lt;blockquote&gt;&lt;br /&gt;David Pogue had a momentary lapse of judgement when he proclaims in his blog that &lt;a href=&quot;http://www.nytimes.com/2006/04/04/technology/poguesposts/04pogues-posts.html&quot;&gt;the date sequence 01:02:03 04/05/06&lt;/a&gt; will only happen once in all of human history.&lt;br /&gt;&lt;br /&gt;Besides the obvious gaffes of date formatting (which one is the month and which one is the year?), the red herring of leading zeros (to make the minute and second stand out), and so on, no one who&apos;s seen this has made the comment that calendars say whatever we want them to say and the numbers are only special because we set the calendar up that way in this one case. What about the Chinese, Hebrew, and Muslim calendars?&lt;br /&gt;&lt;br /&gt;So this seems like a good challenge to publish in &lt;a href=&quot;http://www.theperlreview.com&quot;&gt;The Perl Review&lt;/a&gt;: using the Perl Date modules (or not, I guess), in how many different calendars and formats can you make this sequence? What else is special about those days (are they a weekend, fall on a full moon, have a solar eclipse, etc.)?&lt;br /&gt;&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href=&quot;http://www.perlmonks.org/index.pl?node_id=541244&quot;&gt;Read more about it on Perlmonks&lt;/a&gt;...</description>
  <comments>http://perl-review.livejournal.com/18403.html</comments>
  <lj:security>public</lj:security>
</item>
<item>
  <guid isPermaLink='true'>http://perl-review.livejournal.com/18171.html</guid>
  <pubDate>Mon, 27 Mar 2006 08:35:59 GMT</pubDate>
  <title>The Economics of Newsstands</title>
  <link>http://perl-review.livejournal.com/18171.html</link>
  <description>Powell&apos;s Technical Books in Portland (that&apos;s the one on  33 NW Park Avenue) is going to carry &lt;i&gt;The Perl Review&lt;/i&gt;. It&apos;s our first newsstand distribution. &lt;br /&gt;&lt;br /&gt;I had to set a newstand price. The deal basically works like this: bookstores keep most of the profit. Magazines make money when the single-issue buyers turn into subscribers. After Powell&apos;s cut, which we set at 40%, and my costs, $2 an issue, I have to figure out a price that also motivates people to give the money to &lt;b&gt;The Perl Review&lt;/b&gt; directly instead of the book store. That&apos;s why you see big discounts for magazines when you subscribe: that&apos;s the real price, and everything else is markup. The Powell&apos;s price ends up being $5, which is 50 cents more than the subscription price.&lt;br /&gt;&lt;br /&gt;That&apos;s not to say that newsstands are bad. It&apos;s like better-than-free advertising since it sits on the shelf and I cover my costs plus a little more for every issue sold. &lt;br /&gt;&lt;br /&gt;Forget about absolute numbers for a moment. At my price point, if they sell 75% of the copies, I break even. That would be fine with me because any copy sitting on the actual magazine display means people see that issue. Some might subscribe later even if they don&apos;t buy it. Now that I have a price point, I have to figure out the right number of issues. That&apos;s something I just have to guess. &lt;br /&gt;&lt;br /&gt;I left 16 copies of the Spring 2005 issue, but I also have to consider that I sold about 10 at the &lt;i&gt;Intermediate Perl&lt;/i&gt; book signing. We&apos;ll see how that goes.&lt;br /&gt;&lt;br /&gt;Now, a good magazine accountant has to keep track of the actual number of newsstand sales too. As much as I&apos;d like to pretend that we sell every single copy, the Post Office wants to know where all the issues went to verfiy that we abide by all the periodical rules. It&apos;s not enough for the newsstand to simply tell me what they sold. They certainly aren&apos;t going to tell me they sold everything when they didn&apos;t since that&apos;s money out of their pocket. They can&apos;t really tell me they sold nothing because that&apos;s money out of my pocket. &lt;br /&gt;&lt;br /&gt;If you&apos;re a late night person living in a city, you might have seen a bunch of guys tearing off the front pages of newspapers and magazines. Instead of sending back the unused copies, they send back the cover (and they do that for books too). Every cover they don&apos;t send back is a sale that they owe me money for.&lt;br /&gt;&lt;br /&gt;You might think those unsold issues represent lost money, but they really don&apos;t. They are a &lt;i&gt;sunk cost&lt;/i&gt;, meaning that I would have spent that money regardless of the sales. That starts way back at the printers when I have to decide how many issues I want. That number includes all subscriptions, complimentary copies, samples to user groups, and all the issues I&apos;ll need to fulfill orders for back issues. Not only that, but the more copies I print, the lower the incremental cost (the cost per each copy). Each printing job has a fixed overhead for the job preparation, machine set-up, and so on. That&apos;s the &lt;i&gt;make ready&lt;/i&gt;. I end up printing many more copies than I need, partly to amoritize the make ready. Not selling at the newsstand is slightly better than not selling while sitting in boxes in the office. At least people see them at the newsstand.&lt;br /&gt;&lt;br /&gt;Remember that magazines make money on subscriptions, so that&apos;s the goal. I don&apos;t care about selling more at the newsstands. If someone subscribes because they see an issue on the newsstand, the profit from the subscription pays for about three unsold newsstand copies, so five subscriptions from people seeing the issue at Powell&apos;s would make up for no sells. That&apos;s just breaking even, and nobody makes any money. That also means I&apos;m spending $6 to get a new subscriber.&lt;br /&gt;&lt;br /&gt;If you&apos;re already despondent, you don&apos;t want to read about distributors. Most bookstores don&apos;t want to deal with every individual publisher. They&apos;d have to keep track of a separate deal for every magazine. Instead, they want to deal with a single source in the same way they deal with books. I know my costs, and I know the newsstands cut, and I have a price point that I can&apos;t change to much because people won&apos;t buy it at too high a price. If I use a distributor, perhaps to get into the big chain book stores, they are going to want a big cut too. I&apos;ll end up either breaking even or losing money on every newsstand copy, and I&apos;ll want to convert that to a subscription as soon as possible. That&apos;s why you see so many wonderful subscription cards in the magazines.&lt;br /&gt;&lt;br /&gt;So far I&apos;ve just talked about money from sales. We can also sell advertising, which we do for the special friends of the Perl community. Since magazines know they are going to lose money at the newsstand, they make up the difference with paid advertising. Ever wonder why magazines such as &lt;i&gt;Wired&lt;/i&gt; are mostly advertisements? That&apos;s making up for the money they&apos;ll lose on the newsstands. Remember when I talked about keeping track of the number of copies sold? Advertisers want to know those numbers. They don&apos;t care how many copies the newsstand bought. They care about the number of copies that shoppers bought. That sets the rate at which the magazines can sell ads. More eyeballs equal more dollars. There&apos;s a separate industry of companies that audit magazines to verify the numbers. That&apos;s even more money that gets sucked away.&lt;br /&gt;&lt;br /&gt;The short story? Subscribe to the magazines you like. It&apos;s the only way they can survive.</description>
  <comments>http://perl-review.livejournal.com/18171.html</comments>
  <lj:security>public</lj:security>
</item>
<item>
  <guid isPermaLink='true'>http://perl-review.livejournal.com/17828.html</guid>
  <pubDate>Mon, 16 Jan 2006 17:48:03 GMT</pubDate>
  <title>RSS for interviews</title>
  <link>http://perl-review.livejournal.com/17828.html</link>
  <description>Last year, I started including interviews with Perl people on The Perl Review website, but I didn&apos;t add a feed for that. Now I have and it&apos;s on &lt;a href=&quot;http://www.theperlreview.com/RSS/&quot;&gt;RSS page&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;It was actually &lt;a href=&quot;http://use.perl.org/~Aristotle/journal/28340&quot;&gt;Aristotle over at use.perl who pointed out the missing feed&lt;/a&gt; by scraping the site and creating his own.&lt;br /&gt;&lt;br /&gt;The web site is actually a directory processed by Template Toolkit, so what I really need to do is add indexing support as ttree goes through the directories, then spit out pages as it does that. That sounds like a magazine article...</description>
  <comments>http://perl-review.livejournal.com/17828.html</comments>
  <lj:security>public</lj:security>
</item>
<item>
  <guid isPermaLink='true'>http://perl-review.livejournal.com/17625.html</guid>
  <pubDate>Wed, 04 Jan 2006 23:31:21 GMT</pubDate>
  <title>New book review news; guideline links</title>
  <link>http://perl-review.livejournal.com/17625.html</link>
  <description>Every issue I get a couple of book reviews that don&apos;t quite cut it. Techies tend to present too many sides of the story: rather than express their opinion, they equivocate by pointing out all the holes in their own opinion. In short, they are entirely too nice.&lt;br /&gt;&lt;br /&gt;Being nice isn&apos;t a bad thing, but what people really want out a book review is a recommendation. &quot;Should I buy this book?&quot; It doesn&apos;t matter if people agree with you as long as you are fair to the book. After that, people want to know the particulars: who, what, when, where, and how.&lt;br /&gt;&lt;br /&gt;So far, The Perl Review has taken reviews from several different people, and very few people have provided multiple reviews. That worked when we were first getting started, but now I think we need something different. Since book reviews are about opinions, and the reader doesn&apos;t have to agree with the reviewer, I think readers need to know the reputation and leaning of the reviewer to make their own decision. For instance, my wife doesn&apos;t agree with movie-reviewer Roger Ebert, but based on his negative reviews she knows which movies she will like. At the same time, she knows the certain people on LiveJournal likes the same sorts of movies she does, so she can trust them.&lt;br /&gt;&lt;br /&gt;In line with all that, I think I&apos;m going to move towards recurring book reviewers, and do more to establish their reputation. That also means that I want to get a couple of reviewers who think about books differently so I can give more readers someone that thinks like them. I&apos;ve approached a couple of people, and we&apos;ll see how it turns out.&lt;br /&gt;&lt;br /&gt;I&apos;ve added two guides I hadn&apos;t run across previously:&lt;br /&gt;&lt;br /&gt;&lt;ul&gt;&lt;br /&gt;&lt;li&gt;&lt;a href=&quot;http://ug.oreilly.com/bookreviews.html&quot;&gt;O&apos;Reilly Media&apos;s Book Review Tips&lt;/a&gt;&lt;br /&gt;&lt;li&gt;&lt;a href=&quot;http://slashdot.org/book.review.guidelines.shtml&quot;&gt;Slashdot&apos;s Book Review guidelines&lt;/a&gt;&lt;br /&gt;&lt;/ul&gt;</description>
  <comments>http://perl-review.livejournal.com/17625.html</comments>
  <lj:security>public</lj:security>
</item>
<item>
  <guid isPermaLink='true'>http://perl-review.livejournal.com/17253.html</guid>
  <pubDate>Thu, 01 Dec 2005 09:30:01 GMT</pubDate>
  <title>I&apos;m disappearing for a bit</title>
  <link>http://perl-review.livejournal.com/17253.html</link>
  <description>It seems that every time I put out a new issue I have to leave town for a couple weeks. I don&apos;t think the two are related. Travel is just too busy this year. Add to that finishing up the Alpaca book and I&apos;ve had a pretty busy week. I&apos;ll be back in the middle of December.</description>
  <comments>http://perl-review.livejournal.com/17253.html</comments>
  <lj:security>public</lj:security>
</item>
<item>
  <guid isPermaLink='true'>http://perl-review.livejournal.com/16959.html</guid>
  <pubDate>Thu, 01 Dec 2005 09:21:37 GMT</pubDate>
  <title>The Perl Review 2.1 ready for download</title>
  <link>http://perl-review.livejournal.com/16959.html</link>
  <description>I&apos;m sending out the email announcements as I post this.  Once you get the new password, you&apos;ll be able to download the latest issue of &lt;a href=&quot;http://theperlreview.com&quot;&gt;The Perl Review&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;In this issue:&lt;br /&gt;&lt;br /&gt;&lt;ul&gt;&lt;br /&gt;&lt;li&gt;Seven Sins of Perl OO Programming -- chromatic&lt;br /&gt;&lt;li&gt;Hash Anti-Patterns -- Alberto Manuel Sim&amp;otilde;es&lt;br /&gt;&lt;li&gt;Haskell for Perlers -- Frank Antonsen&lt;br /&gt;&lt;li&gt;PerlWar -- Yanick Champoux&lt;br /&gt;&lt;li&gt;books reviews, commentary, news and more...&lt;br /&gt;&lt;/ul&gt;&lt;br /&gt;&lt;br /&gt;Some of you neglected to renew, but I won&apos;t bug you in email anymore. To find out more about the sampler on the cover, you&apos;ll have to renew that subscription.&lt;br /&gt;&lt;br /&gt;If you haven&apos;t subscribed yet, now&apos;s the time because I have to raise prices next year when the US postal rates go up.</description>
  <comments>http://perl-review.livejournal.com/16959.html</comments>
  <lj:security>public</lj:security>
</item>
<item>
  <guid isPermaLink='true'>http://perl-review.livejournal.com/16776.html</guid>
  <pubDate>Tue, 15 Nov 2005 19:49:13 GMT</pubDate>
  <title>We&apos;re on Perl.com, and a lot of other places</title>
  <link>http://perl-review.livejournal.com/16776.html</link>
  <description>We now have a permanent link on &lt;a href=&quot;http://www.perl.com&quot;&gt;Perl.com&lt;/a&gt;. We&apos;re way at the bottom, but that&apos;s okay. &lt;br /&gt;&lt;br /&gt;I went looking for other mentions of &lt;a href=&quot;http://www.google.com/search?q=site%3Aoreilly.com+%22the+perl+review%22&amp;amp;sourceid=mozilla-search&amp;amp;start=0&amp;amp;start=0&amp;amp;ie=utf-8&amp;amp;oe=utf-8&amp;amp;client=firefox-a&amp;amp;rls=org.mozilla:en-US:official&quot;&gt;TPR on O&apos;Reilly sites&lt;/a&gt; and found that they have cited many of our book reviews.&lt;br /&gt;&lt;br /&gt;We even have some of &lt;a href=&quot;http://www.google.com/search?q=site%3Aamazon.com+%22the+perl+review%22&amp;amp;sourceid=mozilla-search&amp;amp;start=0&amp;amp;start=0&amp;amp;ie=utf-8&amp;amp;oe=utf-8&amp;amp;client=firefox-a&amp;amp;rls=org.mozilla:en-US:official&quot;&gt;our book reviews cited on Amazon.com&lt;/a&gt;.</description>
  <comments>http://perl-review.livejournal.com/16776.html</comments>
  <lj:security>public</lj:security>
</item>
<item>
  <guid isPermaLink='true'>http://perl-review.livejournal.com/16590.html</guid>
  <pubDate>Sat, 12 Nov 2005 18:54:32 GMT</pubDate>
  <title>Reviewer opportunities</title>
  <link>http://perl-review.livejournal.com/16590.html</link>
  <description>We&apos;re looking for reviewers for Activestate&apos;s Komodo and OSoft&apos;s ThoutReader. &lt;a href=&quot;mailto:editors@theperlreview.com&quot;&gt;Let us know if you&apos;re interested&lt;/a&gt;.</description>
  <comments>http://perl-review.livejournal.com/16590.html</comments>
  <lj:security>public</lj:security>
</item>
<item>
  <guid isPermaLink='true'>http://perl-review.livejournal.com/16184.html</guid>
  <pubDate>Sat, 12 Nov 2005 18:52:18 GMT</pubDate>
  <title>It&apos;s renewal time!</title>
  <link>http://perl-review.livejournal.com/16184.html</link>
  <description>The next issue of The Perl Review comes out in a couple of weeks, so it&apos;s time to renew if you&apos;ve already finished your first year subscription!&lt;br /&gt;&lt;br /&gt;This may seem odd for some who just recently subscribed, but with the magic of time travel we let you pretend that your subscription started much earlier by allowing you to choose which issue to start your subscription. You may have subscribed yesterday but selected to start with issue 1.0 (Winter 2004), meaning that your issue ran out with our last issue, 1.3 (Fall 2005).&lt;br /&gt;&lt;br /&gt;I&apos;ve found that most new subscribers like to get most of the back issues at first, and it&apos;s worked out rather well for us. Now that we&apos;re starting our second year, though, I have to figure out how to make that work so people don&apos;t have to renew right away. I&apos;ll have to add a two-year subscription, I think.</description>
  <comments>http://perl-review.livejournal.com/16184.html</comments>
  <lj:security>public</lj:security>
</item>
<item>
  <guid isPermaLink='true'>http://perl-review.livejournal.com/16040.html</guid>
  <pubDate>Mon, 22 Aug 2005 01:44:10 GMT</pubDate>
  <title>Renewing subscribers </title>
  <link>http://perl-review.livejournal.com/16040.html</link>
  <description>I&apos;ve been reading lot about magazine renewal rates. A lot of publications seem to be happy to get 25% renewals, and they actually spend a fair bit of money to get that. Ever wonder why you get some many magazine renewal letters in your postal mail?&lt;br /&gt;&lt;br /&gt;For TPR, since I don&apos;t have a lot of money, I simply used email. The target audience is certainly technology-adept, so that&apos;s not so bad. So far I&apos;ve sent out three renewal emails. One was the week before OSCON, and I got about a 45% response for that. That&apos;s already good for magazines, but not quite the 98% renewal rate TPJ had in its first year. I sent out a second email two weeks after that, and another one over the weekend. I think I&apos;m floating somewhere around 75% renewal right now.&lt;br /&gt;&lt;br /&gt;I have a list of all of the people who haven&apos;t renewed (it&apos;s an SQL view ;), and a lot of them should have and I would be surprised if they don&apos;t. Although email provided me with a virtually free way to get that 75%, I also think email has a tendency to get lost. First, if the subscriber can&apos;t deal with it right awy, it joins the long queue of messages that get ignored forever. Second, it has a pretty good chance of being blocked by a spam filter. Third, some people might get so mucch mail that they just don&apos;t get to ever see it. I do send each mail individually since each contains a persoanl renewal code, so I&apos;m not blasting out spam to any user at each domain.&lt;br /&gt;&lt;br /&gt;I am considering sending out some postcards to the hold-outs. I figure that will cost me about $50, which means that I need about four renewals to make up for it. If I get four renewals, that&apos;s paid for. I&apos;m also going to try emailing people directly. It certainly helps when other people talk about TPR. I notice a big spike in renewals when Ovid talked about his upcoming Logic Programming article.&lt;br /&gt;&lt;br /&gt;There&apos;s another trick to getting renewals: special promotional subscriptions. Magazines give you a special rate for a limited time then hit you up for the full price as quickly as possible. It&apos;s all part of the ad-selling game. Advertisers want to know how many &quot;qualified subscribers&quot; you have, which means how many people actually want your magazine enough to pay for it. Getting people to be full subscribers raises those numbers.&lt;br /&gt;&lt;br /&gt;TPR is a bit different because I don&apos;t aim to make it an audited magazine, meaning that no one is going to come in and put a stamp on our books saying they verified our subscriber base. I&apos;m not in it to sell advertising (let&apos;s see if I&apos;m saying the same thing in three years). So far I&apos;ve only taken advertising from people the Perl community already loves and trusts. Most of that is just filling up the other full color pages that come along with the cover.</description>
  <comments>http://perl-review.livejournal.com/16040.html</comments>
  <lj:security>public</lj:security>
</item>
<item>
  <guid isPermaLink='true'>http://perl-review.livejournal.com/15831.html</guid>
  <pubDate>Thu, 28 Jul 2005 05:18:34 GMT</pubDate>
  <title>&quot;Computer Science Major Publishes Book on Perl Testing&quot; </title>
  <link>http://perl-review.livejournal.com/15831.html</link>
  <description>TPR got a mention in &lt;a href=&quot;http://www.research.neu.edu/computer/perl.html&quot;&gt;Northeastern&apos;s tiny article about Ian Langworth&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;Curiously, they dropped every name they could find, except mine. Oh well. :)</description>
  <comments>http://perl-review.livejournal.com/15831.html</comments>
  <lj:security>public</lj:security>
</item>
<item>
  <guid isPermaLink='true'>http://perl-review.livejournal.com/15391.html</guid>
  <pubDate>Tue, 26 Jul 2005 04:27:51 GMT</pubDate>
  <title>Review PrimalScript IDE </title>
  <link>http://perl-review.livejournal.com/15391.html</link>
  <description>Anyone want to review &lt;a href=&quot;http://www.sapien.com/ProductsandServices/PrimalScript31/tabid/255/Default.aspx&quot;&gt;PrimalScript&lt;/a&gt;, Sapien&apos;s IDE? It says it has Perl support.</description>
  <comments>http://perl-review.livejournal.com/15391.html</comments>
  <lj:security>public</lj:security>
</item>
<item>
  <guid isPermaLink='true'>http://perl-review.livejournal.com/15156.html</guid>
  <pubDate>Sun, 24 Jul 2005 12:19:36 GMT</pubDate>
  <title>Matching up records </title>
  <link>http://perl-review.livejournal.com/15156.html</link>
  <description>I now have a big stack of emails confirming renewal transactions, and I need to shove those transactions into my local database so people keep getting their magazines.&lt;br /&gt;&lt;br /&gt;Most of them are pretty easy because they are keyed on their unique ID in the database. A lot of people skipped the link I sent them and went to the subscription page directly, so I have to match up those with what I see in te database.&lt;br /&gt;&lt;br /&gt;So far it works like this and handles 95% of the records:&lt;br /&gt;&lt;br /&gt;&lt;ol&gt;&lt;br /&gt;&lt;li&gt; Get all the matches by name&lt;br /&gt;&lt;ol&gt;&lt;br /&gt; 	&lt;li&gt;With one match, we&apos;re probably done&lt;br /&gt; 	&lt;li&gt;With no match, try different parts of the name (last, first)&lt;br /&gt; 	&lt;li&gt;With multiple matches, we need to match something else too.&lt;br /&gt;&lt;/ol&gt;&lt;br /&gt;&lt;li&gt;From the name matches, compare email addresses. If they match, we&apos;re done.&lt;br /&gt;&lt;li&gt;At this point we probably have several candidate matches.&lt;br /&gt;&lt;li&gt;Look at parts of the address (country, city, address). If the first two are matches, we&apos;re pretty sure we have a match.&lt;br /&gt;&lt;li&gt;Look at the email if we might have a match and compare the user portion to the new email and the stored email. Do the same for the host portion. This is just to raise the confidence level a bit.&lt;br /&gt;  &lt;/ol&gt;&lt;br /&gt;&lt;br /&gt;This leaves about 5% that I need to check by hand. It&apos;s the first time I&apos;ve had to go through with this so I&apos;m being very cautious. Thank god for test suites.</description>
  <comments>http://perl-review.livejournal.com/15156.html</comments>
  <lj:security>public</lj:security>
</item>
<item>
  <guid isPermaLink='true'>http://perl-review.livejournal.com/14852.html</guid>
  <pubDate>Sun, 17 Jul 2005 06:58:29 GMT</pubDate>
  <title>It&apos;s renewal time </title>
  <link>http://perl-review.livejournal.com/14852.html</link>
  <description>Now that we&apos;ve made it through the first year, it&apos;s time to get people to renew. I&apos;ve sent out renewal emails, but I&apos;m guessing 10% of them will never make it into an inbox. Spam has just about ruined email for anything.&lt;br /&gt;&lt;br /&gt;If you&apos;ve already received four issues, it&apos;s time for you to renew, and you can use &lt;a href=&quot;http://www.theperlreview.com/cgi-bin/subscribe.cgi&quot;&gt;subscription form&lt;/a&gt; and subscribe again.&lt;br /&gt;&lt;br /&gt;Either way, I have an interesting task ahead. Since I don&apos;t store any personal information on the Pair.com servers that power our website, and we never store credit card information or do recurring billing, I get to match up the renewals with existing subscribers. It&apos;s easy to know which transactions are renewals, and each email I&apos;ve sent has a link with a query string that I can link back to a subscriber. However, people might not follow the link but go directly to the webiste, or all sorts of other things that don&apos;t let me see that code. We&apos;ll see how that goes.&lt;br /&gt;&lt;br /&gt;In related matters, I was rewriting the code bits that parse the email I get so I can shove all that stuff into the database. I was doing fancy things with ergexen, then Template::Extract, and some other things, and although it was a lot of fun, it was a big waste of time. Since I really just wanted to suck it into another program, why not send it as a ready-to-use data structure? It&apos;s easy enough to freeze things and unthaw them later. I still see my nicely formatted template, but at the end I include the Perl ready data. Besides the trivial parsing to isolate that, I&apos;m ready to important things into the database. Things can be too simple to be seen sometimes.</description>
  <comments>http://perl-review.livejournal.com/14852.html</comments>
  <lj:security>public</lj:security>
</item>
<item>
  <guid isPermaLink='true'>http://perl-review.livejournal.com/14611.html</guid>
  <pubDate>Thu, 14 Jul 2005 21:03:58 GMT</pubDate>
  <title>Review &quot;Pro Perl&quot; and &quot;Perl Testing: A Developer&apos;s Notebook&quot; </title>
  <link>http://perl-review.livejournal.com/14611.html</link>
  <description>Anyone want to review any of these books? &lt;a href=&quot;mailto:brian.d.foy@gmail.com&quot;&gt;Let brian know&lt;/a&gt; soon. The article deadline is at the end of the month.&lt;br /&gt;&lt;br /&gt;&lt;ul&gt;&lt;br /&gt;&lt;li&gt;Pro Perl (Apress)&lt;br /&gt;&lt;li&gt;Perl Testing: A Developer&apos;s Notebook (O&apos;Reilly)&lt;br /&gt;&lt;li&gt;Learning Perl, 4th edition (O&apos;Reilly)&lt;br /&gt;&lt;/ul&gt;</description>
  <comments>http://perl-review.livejournal.com/14611.html</comments>
  <lj:security>public</lj:security>
</item>
<item>
  <guid isPermaLink='true'>http://perl-review.livejournal.com/14511.html</guid>
  <pubDate>Wed, 29 Jun 2005 15:44:58 GMT</pubDate>
  <title>I finally meet Eric Maki </title>
  <link>http://perl-review.livejournal.com/14511.html</link>
  <description>I finally got to meet Eric Maki, TPRs designer, in person. We went through the current issue and looked at a lot of the design things we might want to change, and we also have an idea for an upcoming project I&apos;ll have details later.&lt;br /&gt;&lt;br /&gt;If you haven&apos;t seen the latest cover (Summer 2005), get yourself an issue. It&apos;s so nice that we&apos;re going to make posters of it.</description>
  <comments>http://perl-review.livejournal.com/14511.html</comments>
  <lj:security>public</lj:security>
</item>
<item>
  <guid isPermaLink='true'>http://perl-review.livejournal.com/14283.html</guid>
  <pubDate>Wed, 29 Jun 2005 15:42:49 GMT</pubDate>
  <title>I&apos;ll be on Perlcast soon </title>
  <link>http://perl-review.livejournal.com/14283.html</link>
  <description>After a long day at YAPC where I taught a 4-day Learning Perl course in a single day, and then a 5 hour boat dinner cruise, Josh McAdams of &lt;a href=&quot;http://www.perlcast.com&quot;&gt;Perlcast&lt;/a&gt; interviewed me about The Perl Review. I&apos;m not sure when he&apos;ll publish it.&lt;br /&gt;&lt;br /&gt;The cool thing is that Josh is moving to Chicago. I might be able to get on Perlcast a bit more often. :)</description>
  <comments>http://perl-review.livejournal.com/14283.html</comments>
  <lj:security>public</lj:security>
</item>
<item>
  <guid isPermaLink='true'>http://perl-review.livejournal.com/13884.html</guid>
  <pubDate>Tue, 21 Jun 2005 04:14:42 GMT</pubDate>
  <title>The Best Software Writing reviewer </title>
  <link>http://perl-review.livejournal.com/13884.html</link>
  <description>I got an advnace copy of &lt;a href=&quot;http://apress.com/book/bookDisplay.html?bID=453&quot;&gt;The Best Software Writing&lt;/a&gt; from Apress. It&apos;s a collection of writings compiled by Joel Spolsky. Anyone want to take a whack at reviewing this for the next issue?</description>
  <comments>http://perl-review.livejournal.com/13884.html</comments>
  <lj:security>public</lj:security>
</item>
<item>
  <guid isPermaLink='true'>http://perl-review.livejournal.com/13593.html</guid>
  <pubDate>Wed, 15 Jun 2005 18:13:14 GMT</pubDate>
  <title>In the mail today </title>
  <link>http://perl-review.livejournal.com/13593.html</link>
  <description>The Perl Review Summer 2005 issues should be in the mail today. The printer was screwing around again. They&apos;ve been a disaster. You know the sort of people: they can&apos;t just do something without sending four emails back and forth, each with some new reason why things can&apos;t happen right away.&lt;br /&gt;&lt;br /&gt;Ugh. My apologies everyone.</description>
  <comments>http://perl-review.livejournal.com/13593.html</comments>
  <lj:security>public</lj:security>
</item>
</channel>
</rss>
