Beefy Boxes and Bandwidth Generously Provided by pair Networks
Keep It Simple, Stupid
 
PerlMonks  

Re: Re: Re: One Section to rule them all.

by graff (Chancellor)
on Jun 17, 2003 at 01:15 UTC ( #266349=note: print w/ replies, xml ) Need Help??


in reply to Re: Re: One Section to rule them all.
in thread One Section to rule them all.

I agree in principle about the difference between a 'snippet' and a 'program', but I think that this distinction is easily blurred

There was nothing in rozallin's proposal to stipulate that an entry in Code Catacombs had to be a particular minimum number of lines of code. If a one-liner stands on its own as a useful and reliable tool, then it would belong in the Catacombs. (Meanwhile, some "snippets" could be quite large, despite having limited utility...)

I especially like rozallin's proposed distinction between the functions of "Craft" and "Catacombs" -- i.e. tentative vs. tested code. Note that rozallin used the term "polished", not "finished"; indeed, there is virtually no such thing as "finished" code (except for stuff that no one uses any more).

And because folks can update their own root nodes in the Catacombs section, this is an excellent place to maintain useful tools.


Comment on Re: Re: Re: One Section to rule them all.
Re: Re: Re: Re: One Section to rule them all.
by benn (Priest) on Jun 17, 2003 at 09:46 UTC
    There was nothing in rozallin's proposal to stipulate that an entry in Code Catacombs had to be a particular minimum number of lines of code.

    There was nothing in mine either, or my answer. I was simply pointing out that the distinction is fuzzy, and often the 'wrong' categorisation choice is made, based on the lack of firm criteria, and that I felt the choice was fairly arbitrary in the first place.

    Note that rozallin used the term "polished", not "finished"

    Actually, the exact phrase was "I have always regarded Code Catacombs as a place for finished polished code"...(unless my cut'n'paste is inserting random words again {g}) - hence my making the jokey point about code never being finished, which you kindly repeated.

    As for the point about distinguishing between 'tentative' and 'tested' code, again I think this is extremely fuzzy, and why bother trying to make it? As you say, the Catacombs is an excellent place to maintain code - why not have it spend its whole life cycle there? At what point would somebody decide to 'move' their code from Craft to Catacombs? Would the node move? Or would we simply get duplicated code - an old version in Craft, and newer versions in Catacombs? All this could simply be replaced, as I said, with a "status" indicator, which (if were required) would be able to give a finer granularity than simply "tentative/tested".

    Cheers, Ben.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://266349]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others meditating upon the Monastery: (7)
As of 2014-12-29 10:58 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    Is guessing a good strategy for surviving in the IT business?





    Results (186 votes), past polls