I like this concept. I think it has the potential to spawn some really interesting new challenges. So let it thrive for now and see where this is going. I also agree with Quincunx that we can wait for another one or two questions before making this a tag. Maybe this remains a one-timer after all, and then it's just a special popularity contest. If we do decide to tag it, I really like Quincunx's suggestion of patchwork-code. :)
But now the point I really want to stress. Code trolling happened recently and we don't want it to happen again. But I don't think we should discourage new and innovative types of challenges either, but we should maybe watch out to keep their evolution in more control.
So what I'm saying is, if the next weeks have several new duct-tape-coding/patchwork-code challenges, we should be particularly rigorous and scrutinising. If those new questions don't live up to our high standards, close them (and give the OP some advice what he could do better). Just because they might be popular is still no argument. In particular we should ask ourselves:
- Does this question add something novel to this type of challenge? After today's "Print 'hello mom'", another primitive string manipulation challenge like "Convert the input to lower case" would seem somewhat pointless. In fact, I'd close-vote as duplicate. A polyglot challenge on the other hand could be highly interesting.
- Does the actual problem benefit from being posed as a patchwork challenge? Even if the question sounds fun as it is, maybe it would be even more fun it was just a plain old code-golf or some other code-challenge? Don't close, but consider downvoting and voicing your opinion.
- Does it seem like the OP just wanted to post a patchwork challenge (because it's popular) and then just slapped an arbitrary problem on it? This may well fall in the first category, as this will likely not add anything new. Consider closing as duplicate, more importantly downvote and express constructive criticism in the comments.
- Does this meet the usual quality standards? Is it too broad? Unclear? etc... There are close vote reasons for that.
If the challenge still seems interesting after careful consideration, by all means upvote and encourage those questions. If not, decimate the population (of patchwork challenges; just saying). I just think we'd be throwing away a lot of potential if (after what happened with code trolling) we started to close things with reasons like "it's new, I don't like new, new is always worse, kill it fire".