<?xml version="1.0" encoding="windows-1252"?>
<node id="826743" title="Re: It's the little things..." created="2010-03-04 11:59:23" updated="2010-03-04 11:59:23">
<type id="11">
note</type>
<author id="8157">
webfiend</author>
<data>
<field name="doctext">
&lt;p&gt;That's a tough question for me, because part of the reason I love Perl is all the little things that are waiting to nibble my toes. It's a rich, delightful language, and I miss it every day when I clock in to work on some overbearing Rails project.&lt;/p&gt;

&lt;p&gt;I think the &lt;em&gt;first&lt;/em&gt; playful nip from Perl was when I realized that I didn't need to explicitly specify &lt;code&gt;scalar&lt;/code&gt; to get the length of a list - I could just assign the list to a scalar variable. I had already read this in the Camel book, but I stuck with &lt;code&gt;scalar&lt;/code&gt; because I didn't trust Perl to do what I meant. I still remember the day the scales fell from my eyes, sitting in front of my Slackware machine with coffee in hand and suddenly seeing &lt;em&gt;context&lt;/em&gt; in my Perl app where before I had seen only code.&lt;/p&gt;

&lt;p&gt;I continued using &lt;code&gt;scalar&lt;/code&gt; in production code for a while, mainly because my coworkers and managers didn't really grok context.&lt;/p&gt;

&lt;p&gt;I've had many nibbles since, but that is the one sticks out in my memory.&lt;/p&gt;</field>
<field name="root_node">
826230</field>
<field name="parent_node">
826230</field>
</data>
</node>
