in reply to Shut down the Snippets Section

I'm trying to figure out why the distinction between Code and Meditations exists. Most RFCs are posted in Meditations as are most cool things people do. As far as I'm concerned, get rid of all three and push everything towards Meditations. If that's too radical, I say get rid of everything except for Code and have each of the elements be optional.

My criteria for good software:
  1. Does it work?
  2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?

Replies are listed 'Best First'.
Re^2: Shut down the Snippets Section
by Erez (Priest) on Apr 14, 2008 at 17:46 UTC

    I'm trying to figure out why the distinction between Code and Meditations exists

    It's what you expect to find when you go to each section.
    You go to Code to look for programs, i.e. code that can be downloaded and edited or executed, and to Meditations for a debate over code, or for code that is shown not as a working program, but as a demonstration of a concept, or as a RFC.

    Software speaks in tongues of man.
    Stop saying 'script'. Stop saying 'line-noise'.
    We have nothing to lose but our metaphors.

      I go to CPAN to find programs that I can download. I go to Perlmonks to discuss concepts and to learn. Code is a poor CPAN.

      My criteria for good software:
      1. Does it work?
      2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?

        Code is a poor CPAN.

        If it was meant as CPAN, then it would've been a poor CPAN. It's hardly meant as that, but as a collection of working examples, scripts, utilities, proof of concepts, how-to's, recipes, implementation of design patterns, workarounds, macros, joke programs, and whatever else you don't go to CPAN to look for. RFC's can go to meditations.

        Also, there are many levels of Perl programmers, and at the early-to-mid levels, reading code is a great way of learning. CPAN is meant for a sort of "black box" usage, not for displaying code examples that should be abused and edited.

        Software speaks in tongues of man.
        Stop saying 'script'. Stop saying 'line-noise'.
        We have nothing to lose but our metaphors.