On Sunday, April 14, 2002, at 06:21 , Bill -Sx- Jones wrote:
--boring, cautious, obvious over commented code--
Nothing wrong with being OVERLY cautious, especially if YOU expect to
understand why you did what you did months or years later.
I wrote a quick hack once to fix a short term
Drieux == Drieux [EMAIL PROTECTED] writes:
Drieux I have the first printing from 1991 version - does this version have
Drieux a name??? So that when I mention it, I can use the culturally
Drieux accepted term. This remains the dog eared, coffee stained,
Drieux fast thumber - in lieu of a
On Monday, April 15, 2002, at 10:54 , Randal L. Schwartz wrote:
[..]
Now, the next step would be to write a book that is how to spend your
*second* 40 hours with Perl :)
while that sorta sounds like a joke - it might help some of the
folks I know - sober as a judge
may I request an
On Sun, 14 Apr 2002 12:54:56 -0500, Gilmore-Baldwin, John wrote:
That said, I think there's a difference between a show-off programmer
(who may think he's really cool and smart for writing code that nobody
else can understand) and a person who's new to perl and using well
regarded reference
Sorry. I know this is getting pretty far off topic. But...
I couldn't agree more with the first sentence of this post. Show-off
programming should only be used for entertainment, or not at all.
That said, I think there's a difference between a show-off programmer
(who may think he's really cool
On Sunday, April 14, 2002, at 01:54 , Gilmore-Baldwin, John wrote:
I can't imagine a quicker way to destroy those last two qualities (eager
and motivated) than to laugh at them for doing a little research (rtfm,
so to speak), finding an answer to a problem and using it. In my
experience,
On Sun, 14 Apr 2002 18:12:37 -0400, ellem wrote:
I'm a sys admin. I never told anyone I was a programmer. A few months
ago I got yanked into a coder meeting and one of my Perl Scripts was on
the wall in 4 foot glory and our manager was pointing out how NOT to
write code. He never asked
--boring, cautious, obvious over commented code--
Nothing wrong with being OVERLY cautious, especially if YOU expect to
understand why you did what you did months or years later.
I wrote a quick hack once to fix a short term problem - three years later
that code is STILL in use :( I can
I started this thread some aeons back, and if some of you think it is
OT, sowwwy. but I just wanted to make a few comments...
I appreciate and feel encourage by Randal's comments, although I
wouldn't judge the PerlGolfers so harshly. Obviously, Randal is in a
distinctly different position
