http://qs321.pair.com?node_id=113121
mjeaton's user image
User since: Sep 18, 2001 at 17:46 UTC (23 years ago)
Last here: Nov 12, 2023 at 19:55 UTC (20 weeks ago)
Experience: 1429
Level:Hermit (10)
Writeups: 38
Location:Coldwater, MI
User's localtime: Mar 28, 2024 at 16:07 -05
Scratchpad: View
For this user:Search nodes
Watch for posts by this user

I learned Perl in 1997. At the time, I was working on a team that had what I would call a Perl guru on it. This guy was absolutely one of the smartest people I've ever known. He was able to listen to a developer give a possible solution to a problem and within 5 seconds have 10 reasons why the solution wouldn't work (he had been on the project longer than anyone else).

At the time, I didn't see the point of learning Perl -- VB is where my efforts took form. I was given the task of automating our build process -- the project consisted of several VB programs and a few C programs. My first thought was to do it in VB. After this didn't go too well, he suggested that I try Perl. He loaned me his Camel book and the rest is history...within a week I had the build process fully automated using Perl (and makefiles). That build program was still being used after I left.

I continue to use Perl when I need get something done quickly and efficiently.

My favorite (recent) nodes
(OT) Professional Employees: who owns your thoughts?
Beginning Programming with Perl
Perl falls victim to shifting trends
Are design patterns worth it?
Using CVS for revision control
Style, style, style
Creating Books and Manuals with Perl
Perl6 Quick Reference
Editor / IDE Consolidation
Perl Programming guidelines/rules