Message from discussion
Agility sucks [Was: How long should a function be?]
Path: g2news1.google.com!news3.google.com!news.glorb.com!cycny01.gnilink.net!cyclone1.gnilink.net!gnilink.net!cyclone.rdc-nyc.rr.com!news-out.nyc.rr.com!twister.nyc.rr.com.POSTED!53ab2750!not-for-mail
From: Kenny Tilton <ktil...@nyc.rr.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
Newsgroups: comp.software-eng,comp.lang.lisp
Subject: Re: Agility sucks [Was: How long should a function be?]
References: <ahome.4206$yG4.126187@news20.bellglobal.com> <87hdgl1xtb.fsf@huldreheim.no-ip.org> <roy-75C2D1.21251729052005@reader1.panix.com> <S2vme.221$iA6.81@newssvr19.news.prodigy.com> <vmwme.14838$IX4.8605@twister.nyc.rr.com> <Dhyme.255$IE7.159@newssvr21.news.prodigy.com> <uzmudcez1.fsf@news.dtpq.com> <5AIme.1120$iA6.865@newssvr19.news.prodigy.com> <uhdgk33gh.fsf@news.dtpq.com> <m3is10lc9c.fsf@gigamonkeys.com> <HmSme.220$vS6.145@amstwist00> <07c4a1t8tb1ihvrbtt3clja37v81mu48b0@4ax.com> <d7ua0h$3d1$2@possum.melbpc.org.au> <Zvzoe.20736$IX4.13006@twister.nyc.rr.com> <VeEoe.44$jS1.12@newssvr17.news.prodigy.com>
In-Reply-To: <VeEoe.44$jS1.12@newssvr17.news.prodigy.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Lines: 33
Message-ID: <uNEoe.21228$IX4.14039@twister.nyc.rr.com>
Date: Sun, 05 Jun 2005 15:23:06 GMT
NNTP-Posting-Host: 66.65.182.98
X-Complaints-To: abuse@rr.com
X-Trace: twister.nyc.rr.com 1117984986 66.65.182.98 (Sun, 05 Jun 2005 11:23:06 EDT)
NNTP-Posting-Date: Sun, 05 Jun 2005 11:23:06 EDT
Organization: Road Runner - NYC
Phlip wrote:
> Kenny Tilton wrote:
>
>
>>I can refactor perfect code, but I cannot clean it up.
>
>
> The clean spot moves over time. What worked today might not be good enough
> tomorrow.
My point was that "cleaning up" cannot be a synonym for refactoring,
because sometimes I have a very nice function which I eventually
discover contains some subprocessing which is desirable as a standalone
function, or undesirable in calls by a new client. Then I take what had
been a prime to my mind and factor it, such that the original function
now takes a new parameter (to suppress the subprocessing) or it now
calls a new function to do the subprocessing, which new function is now
available to clients.
That is not cleaning up.
--
Kenny
Why Lisp? http://lisp.tech.coop/RtL%20Highlight%20Film
"If you plan to enter text which our system might consider to be
obscene, check here to certify that you are old enough to hear the
resulting output." -- Bell Labs text-to-speech interactive Web page