|Perl: the Markov chain saw|
Re^4: New Section: Obfu Art Gallery? (change)by tye (Cardinal)
|on Apr 21, 2004 at 03:28 UTC||Need Help??|
Implement it, and you'll have a much better idea. (:
It took me several hours to turn the Perl News section into a place people could post to. And it already existed as a section and I didn't even implement much of what is implemented for other sections (you can't "approve" news items, for example).
There are a ton of features involved with 'sections'. Several of the sections are nearly identical, several are less so. Lots of the common code is factored out. Some of it could be factored out more effectively. But there are still a ton of entries to make and things to tie together and the process is rather time consuming because you're patching a live site without an automated 'roll out' system. And this stuff is harder to do from where I'm typing this node (giving my kids their bath) both in terms of display/keyboard issues and (more so) in terms of concentration.
And the proposed section (as I already covered) isn't like any existing PerlMonks section.
If you just want another 'page', not really a 'section', then it'll be a lot less work to 'do it yourself', either here (your home node or such) or elsewhere.
But my objection has more to do with continuity of design for the site. While I'm not volunteering to do this work, bolting on something as specific as this, well... as proposed, it would fit in like something bolted onto the side. I'd like to have it, though.
And if I wanted it more, I'd put it on my home node (or just use the root node of this thread for it) and encourage people to /msg me suggestions for additions. And as time went on I'd adjust how the list is broken up into sublists, etc. It'd still be bolted onto the side, and it would get done.
And if it got fairly big and I wanted to let people vote on things, then I'd write a little web app and move the current list into some kind of database.
There aren't any fields in the current PM database for 'reputation as obfu art'. And if someone wanted that information in the PM database, I'd tell them to come up with a more general design so we could do more 'best of' pages... And then I'd tell them to implement it off of PM (where it will be much less work for them to do and they won't have to be much bothered by my or other gods' ideas of 'good design' or my frequent 'lack of time' for such).
We've been trying for years to get PM development improved and moving along. We've made a lot of improvements and we've also taken a lot of steps that didn't do much good (at least not yet). So every once in a while we get a flurry of changes. The backlog of things that really should be done is huge.
I've taken a bit of flack for my lack of progress in some things over the years. As I see it, I often get this flack because I'm often the one doing the most (as little as it is). So I've become pretty non-apologetic about it.
The site limps along rather successfully. About the best way to ruin the experience for yourself is to get hung up on something you want changed or (the lack of) the process of change.