1. RE: [NF]The best code is No Code At All (Stephen the Cook)
Message: 1
Date: Sat, 2 Jun 2007 09:00:25 -0500
From: Stephen the Cook [EMAIL PROTECTED]
Subject: RE: [NF]The best code is No Code At All
To: [EMAIL PROTECTED]
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain;
Derek Kalweit wrote:
A function of half a dozen lines is sometimes far
easier to read than one of 5 lines. I try to code to make things
clearly readable and explicit and only shorten/compress the code if
needed for optimization. If I feel the optimized code is too hard to
read, I leave the
Sorry about the link, I sent HTML Format. It should have been:
http://www.codinghorror.com/blog/archives/000878.html
or
http://tinyurl.com/33vuuy
Dave Crozier
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Dave Crozier
Sent: 01 June 2007 10:13
To:
An interesting discussion on the benefits of writing as little code as
possible. Also, the comments make good reading.
HYPERLINK
http://www.codinghorror.com/blog/archives/000878.htmlhttp://www.codinghorr
or.com/blog/archives/000878.html
Dave Crozier
No virus found in this outgoing
This bring back memories.
This remind me of a pseudocode one of my fellow
students wrote back in the 80s, ok don't calculate
my age now ok... it did the job but had more than
300 statements and the longest so far was 30 statements
and the smallest 12, so the professor gave him an F
he told him
On 6/1/07, Dave Crozier [EMAIL PROTECTED] wrote:
An interesting discussion on the benefits of writing as little code as
possible. Also, the comments make good reading.
I think the original poster missed the mark.
if (s == String.Empty)
if (s == )
.. It seems obvious to me that the latter case
Ted Roche wrote:
On 6/1/07, Dave Crozier [EMAIL PROTECTED] wrote:
An interesting discussion on the benefits of writing as little code as
possible. Also, the comments make good reading.
I think the original poster missed the mark.
if (s == String.Empty)
if (s == )
.. It seems
Aida I. Rivera-Benítez wrote:
This bring back memories.
This remind me of a pseudocode one of my fellow
students wrote back in the 80s, ok don't calculate
my age now ok... it did the job but had more than
300 statements and the longest so far was 30 statements
and the smallest 12, so the
Well said, Ted. Computers can crunch a ton of stuff, and especially
with today's remarkable processing power, the guy is perhaps focused on
the wrong aspect. My POV: Always write code that others can maintain,
because even if that's you, you don't want to be cursing it (or
yourself) years
9 matches
Mail list logo
