Re^2: Documenting Perl Scripts

"You should tell your boss to stuff it."

This tends be be a career limiting move.

In my years of programming, I've been given maintenance problems in Fortran, PL/1 (and some of its subsets), COBOL, wacky special purpose languages for simulation, SQL, awk, C, C++, VB, various *ix shell-scripting languages, JCL, CLISTS, DCL, VBS, VBA, sed, InstallShield's scripting language, html, RAMIS II, and Speakeasy (this list may be incomplete). I haven't had any in Perl, because I'm the only Perl programmer at my current employer.

It's a learning experience; I really want to be indispensible, as in when I leave my employer frequently calls me with offers of large sums of money

emc

Comment on Re^2: Documenting Perl Scripts

Replies are listed 'Best First'.
Re^3: Documenting Perl Scripts by Perl Mouse (Chaplain) on Nov 14, 2005 at 16:19 UTC
I really want to be indispensible I've been there - on both sides of the fence. It doesn't work. Noone is indispensible. The world doesn't end if you're hit by a bus - let alone if you leave. No matter what mess you create, someone will figure it out, or rewrite it. The only one knowing Perl at the company certainly doesn't make you indispensible. Someone else can always learn. Or hired. Or your work can be replaced by a Java program. `Perl --((8:>*`	[reply]
Re^4: Documenting Perl Scripts by swampyankee (Parson) on Nov 14, 2005 at 16:33 UTC
I want to be indispensible; I've been laid off four times so I don't expect to be indispensible. The world might end for me if I get hit by a bus. (I worry more about getting hit by a taxi; NYC bus drivers are not as rude) emc	[reply]