<font size=2 face="sans-serif">> </font><tt><font size=2>I've read
Dominus's "Higher Order Perl" and didn't care for it.</font></tt>
<br>
<br><font size=2 face="sans-serif">Sorry for the top-post -- Lotus Notes
does what it does.</font>
<br>
<br><font size=2 face="sans-serif">I have a different reaction to "Higher
Order Perl." I got a lot out of it. I hadn't had any </font>
<br><font size=2 face="sans-serif">dealings with self-referencing subroutines
previously, and had a problem to solve </font>
<br><font size=2 face="sans-serif">for work that Dominus's stuff solved
fantastically. The code I ended up writing evolved </font>
<br><font size=2 face="sans-serif">into a tool used regularly by our team
and has saved countless hours in our development work. </font>
<br>
<br><font size=2 face="sans-serif">Looking at what the market wants is
certainly important on a career level. But I'd like to </font>
<br><font size=2 face="sans-serif">put in a plug for attending to what
your interests are, what really turns you on. Doing so has</font>
<br><font size=2 face="sans-serif">helped me keep my fires lit over the
years. I don't always get to do what I want to do at</font>
<br><font size=2 face="sans-serif">work every day, but since I've made
it a practice to speak to what I like to do, many times</font>
<br><font size=2 face="sans-serif">team members and various managers have
found ways to use my Perl skills in places</font>
<br><font size=2 face="sans-serif">where that might not have happened otherwise.
Case in point. I got really, really interested</font>
<br><font size=2 face="sans-serif">in Catalyst and DBIx::Class a couple
years back, and started building hobby web sites </font>
<br><font size=2 face="sans-serif">on my personal linux machine on weekends.
One day at work, the subject came up around</font>
<br><font size=2 face="sans-serif">needing a place to collect the succession
of documents and code packages our team</font>
<br><font size=2 face="sans-serif">had been building. I piped up with the
idea that a dedicated web site would be ideal. To my</font>
<br><font size=2 face="sans-serif">surprise, the manager OKed that idea,
and gave me the time and support to build the site</font>
<br><font size=2 face="sans-serif">for in-house use, and the final product
proved extremely useful. For me, hog heaven :-)</font>
<br>
<br><font size=2 face="sans-serif">/dennis</font>
<br>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">kevin <kbrannen@pwhome.com></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">dfw-pm@pm.org</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">11/07/2012 11:00 PM</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: [DFW.pm]
in dallas for a short time</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">"Dfw-pm"
<dfw-pm-bounces+ddaupert=csc.com@pm.org></font>
<br>
<hr noshade>
<br>
<br>
<br>
<br><tt><font size=2>On books...<br>
<br>
I liked Conway's "Perl Best Practices". Even when I didn't totally
agree <br>
with it, he says up front that if you think about the "why" and
feel <br>
like you can defend your answer, then the book has worked (or something
<br>
like that). It did make me think about how and why I work, so it was a
<br>
success.<br>
<br>
I found Conway's "Object Oriented Perl" to be fantastic and well
worth <br>
the price. Besides discussing multiple ways to do OO, he also has good
<br>
advice on perl programming in general. In fact, Damian Conway is my <br>
favorite Perl author and he's a blast to listen to if you can catch him
<br>
at a conference or a talk. (I hope we can get him to come back and give
<br>
a talk to our group again.)<br>
<br>
I've read Dominus's "Higher Order Perl" and didn't care for it.
While <br>
there is some interesting stuff, there's not enough to make it <br>
worthwhile -- fortunately it was free I would have been very <br>
disappointed if I had bought it. To me, it was like he had an "Iterator
<br>
hammer" and tried to solve most problems with them. While that works
<br>
well on some problems, it felt like he was having to stretch too much to
<br>
make that work on too many of the problems.<br>
<br>
I've got "Modern Perl", but have yet to read it.<br>
<br>
I'm presently working my way thru the O'Reilly Git book. :) I do <br>
recommend the Chacon "Pro Git" book, and it's free online.<br>
<br>
HTH,<br>
Kevin<br>
<br>
<br>
On 11/07/2012 11:46 AM, Stuart Johnston wrote:<br>
> Unfortunately, most employers are going to want real-world, job<br>
> experience. To substitute for that, make sure you have code that you
are<br>
> proud to share. Put it on github. Look into working on some CPAN modules.<br>
><br>
> Books to read: chromatic's "Modern Perl", Conway's "Perl
Best<br>
> Practices", and if you are really ambitious, MJD's "Higher-Order
Perl".<br>
> Has anyone read "Effective Perl Programming"? That's probably
a good one<br>
> too. (Assuming you have already read "the Camel".)<br>
><br>
> Try using Moose and Plack. Frameworks are good too. Catalyst, Dancer,<br>
> Mojolicious. I know of at least one DFW employer using Catalyst.<br>
><br>
> Have fun!<br>
><br>
><br>
> On 11/7/2012 11:25 AM, Jerry Kassebaum wrote:<br>
>> Stuart and Group,<br>
>><br>
>> What would you suggest I do to build my skills to make myself
hirable? I<br>
>> can use cgi and regular expressions to scrape websites and put
the info<br>
>> into a MySQL database. I can also update divs and spans in webpages
with<br>
>> Ajax. What should I study next?<br>
_______________________________________________<br>
Dfw-pm mailing list<br>
Dfw-pm@pm.org<br>
</font></tt><a href="http://mail.pm.org/mailman/listinfo/dfw-pm"><tt><font size=2>http://mail.pm.org/mailman/listinfo/dfw-pm</font></tt></a><tt><font size=2><br>
</font></tt>
<br>