in reply to Shut down the Snippets Section
Having the Snippets Section gives us nothing but redundancy and confusion. ... For that matter, we could afford to shut down the CUFP section as well
Agreed on both points.
I read the site using the Newest Nodes and the Recently Active Threads pages, so I could take or leave either of the two, but in the sense of looking at the Monastery with the eyes of someone who searches for something specific (code, comment, topic), the distinction isn't making much sense.
I see the concept of the sections as general collection of similar topics. It should be broad enough that posters will be able to understand its functionality, but specific enough to prevent it from becoming a dump. In this sense, I might say that there are too few sections, and more sub-sectioning is needed, or that there are too many. Had this been a forum, or a repository, I'd support a more fragmented, and therefore specialised, format, but seeing the site as it is, I believe it is the other way that should do.
There are many section that overlap. We have an obfuscation AND poetry, snippets, CUFP and Code Catacombs, and SoPW, Categorized Q&A and Tutorials. Some of those parallel sections are creating a confusion.
With Perl, sometimes it you can say something very significant in a few (or one) lines, but sometimes it takes several pages, the distinction should not be made according to size.
Removing CUFP will move the code posts to the catacombs and the non-code use to the meditations, where they will be more available.
Software speaks in tongues of man.
Stop saying 'script'. Stop saying 'line-noise'.
We have nothing to lose but our metaphors.
|
|---|