I'll post a bit more, then ping you :)
but lets say there's a pangram radiation-hardening challenge
which could totally be interesting
the thing is that that really is a new type of challenge
like, the only thing different about your "Print code-bowling" and "Print this ascii art" is what you are printing. The actual challenge still is coming from the pangram
but with radiation-hardening, you are making the source-layout challenge harder
(the actual task to be performed is basically irrelevant)
Therefore, you'd basically end up with a list of "challenge types", where each presents a different challenge with the source layout
but since the actual task is irrelevant, you'd only be able to reuse the type so many times
therefore, I'd argue that the post would become like the secret santa post above
where you have a list of potential source-layout challenges
some of them used, some of them under-used
(I'm not saying that this is a bad thing, I'd just argue that the post should be presented in that manner)
you already do that to a large extent
I'd just make that the main focus of the post
this is all my opinion, so take it with a grain of salt :)
Because right now, you focus on tons of the "patches" that
code-bowling challenges need. But each of those patches are specific to the source-layout tag you are going to use
like, the "max 10K characters" patch would potentially work for the pangram challenge, but wouldn't be needed for a
radiation-hardening challenge
Sorry for the wall of text
in essence I'd argue that you focus more on "Try these unused source-layout challenge types" and "Try to come up with interesting source-layout challenge types" and less on patches that need to be applied.
Ping me if you respond :)
AKA: The Regifting of the White Elephants
Note - I'm not sure this is on-topic or not on meta, but it seems to be as good a place as any. Comment if you disagree.
I have a few challenges that I have posted to the sandbox and then more-or-less forgotten. Some of these challenges are OK; some n...
