Re: Perl can get you fired, if you suck at (your job/perl)

One job I had for over four years was writing Perl to do my job for me. When I had started, I had a working knowledge, but not much more. The first system I wound up writing replaced three people that had left the company a couple months before.

However, that company never sponspered any TPC or YAPC trips. I did get quite a few books out of it.

Perl made my job there. If not, I would of worked there for only a couple months and been off somewhere else.
Hmmmm, damn you Perl!

Actually, the value is to learn the best and quickest way to do your job. It just happens that Perl can be very useful to do that.

Comment on Re: Perl can get you fired, if you suck at (your job/perl)

Replies are listed 'Best First'.
Re: Re: Perl can get you fired, if you suck at (your job/perl) by Beatnik (Parson) on Aug 05, 2001 at 12:34 UTC
I don't remember who told me this at YAPC::Eu (please step forward) but he stated that he did 90% of the work in the first X months of the Y years he worked there (using Perl ofcourse)... Greetz Beatnik ... Quidquid perl dictum sit, altum viditur.	[reply]
coding yourself out of a job by Anonymous Monk on Aug 05, 2001 at 18:30 UTC
i wasn't the one who told you that, but it was true of my last job. i worked there for about two years. the last year i spent doing mostly non-work-related development because i had automated all of my job functions and had nothing left to do (well, practically nothing). guilt eventually got me to find a new job where I could feel like i deserved the paycheck i got	[reply]
Re: coding yourself out of a job by blakem (Monsignor) on Aug 06, 2001 at 00:13 UTC
Wasn't Thomas Edison rumored to have done that as a telegraph operator? He automated the required hourly 'ping' that let people know he was alive and awake. This gave him time to sleep, if I remember correctly. -Blake	[reply]