Re: Pearls (not really) of Perl programming

Haven't really got any nice snippets to post, but the application I managed to convince management to throw away and replace has this in one of the files:

__END__


ONE DAY SOMEONE WILL HAVE TO UPDATE THIS.
APOLOGIES FOR THIS, TIME WAS NOT GIVEN TO ALLOW FOR PROPER ORGANISATIO
+N OF THIS CODE
[download]

I think that pretty well sums it up :)

(I happen to know exactly how long the developer had as well.. can't really say it's an excuse).

Comment on Re: Pearls (not really) of Perl programming Download Code

Replies are listed 'Best First'.
Re^2: Pearls (not really) of Perl programming by itub (Priest) on Nov 24, 2004 at 18:57 UTC
I saw a study cited in Steve MacConnell's Rapid Development where they gave the same task to five teams of programmers, but each team had a different priority: one had to optimize for memory use, other for programming time, other for program size, other for code readability, and the last one for output readability. Every team ranked first or second in the aspect that they were told to optimize. Guess who did worst on code readability? The team that was told to optimize programming time! (And the team the optimized code readability was the worst in terms of programming time.)	[reply]
Re^2: Pearls (not really) of Perl programming by exussum0 (Vicar) on Nov 25, 2004 at 00:11 UTC
My personal favourite is, "forgive me father, for I have sinned." I tend to write that when other people force me to do poopy things. ---- Then B.I. said, "Hov' remind yourself nobody built like you, you designed yourself"	[reply]