It would be much simpler if one put no time restrictions on the responses
to a posted problem, but instead ask that a "spoiler alert" label be posted
on any purported solution to the problem. In that way, readers late to the
game or slow on the uptake, could bypass the posted answers until they were
ready to investigate how others approached their own solutions. This scheme
may not result in as clear a "winner" as a timed contest might provide, but
I expect it would still provide a good learning experience for all the
readers.
Skip
On Wed, Feb 15, 2012 at 8:54 AM, Dan Bron <j...@bron.us> wrote:
> Linda wrote:
> > Design a function with no restrictions
> > on style or specific functions.
>
> I'm glad the constraints on style and presentation were lifted.
>
> Linda wrote:
> > PLEASE DO NOT RESPOND UNTIL 2/22/2012
>
> Raul responded:
> > Please send again when we
> > can respond -- I will read it then.
>
>
> I also think the restriction on response time should be lifted. I believe
> that these challenges would see a lot more uptake and participation if they
> were unfettered by artificial restrictions.
>
> I suggest that those who need a little extra time to solve the puzzle are
> the ones who should exercise restraint. When a puzzle is posted, chances
> are most responses are going to contain spoilers (a smaller number may ask
> for clarifications or include digressions). So, the rule is: if you don't
> want help solving the puzzle, don't read the thread until you're done.
> Pretty easy. (I do this all the time with the more challenging J puzzles
> posted here.)
>
> This approach has the added benefit of not imposing a deadline on people
> who
> need more time than originally allotted (e.g., for those who are on holiday
> until 2/22/2012 and won't even see the puzzle til they get back).
>
> So, I'm just going to be bold here and adopt this convention. Let's see
> what
> happens.
>
> **SPOILER AFTER 15 BLANK LINES**
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> gw =: ' '&, {~ #\ (- (|. 1j1&#)"_1 >:@?) #
>
> gw 'many'
> m
> n m
> n a y
> a y n m
>
> gw 'many'
> n
> a y
> m y a
> n y m a
>
> gw 'cherrytrees'
> t
> r e
> e r e
> r e e y
> t e c h e
> r r r e h e
> e e c s t r h
> r s h e r y c t
> e s e y c r e r r
> s h c e r e r r e y
> s c e r r e r h e y t
>
> a=:gw '%%%####'
> a,.a,.a,.a
> # # # #
> % # % # % # % #
> # % # # % # # % # # % #
> # % # % # % # % # % # % # % # %
> % # # # % % # # # % % # # # % % # # # %
> # % # % # # # % # % # # # % # % # # # % # % # #
> # # # % % % # # # # % % % # # # # % % % # # # # % % % #
>
>
> -Dan
>
> PS: >:@? here is a great example of the benefits and uses of @ (in the
> sense that @: is not a suitable replacement, and therefore neither is [:
> >: ? or 1 + ? etc. You'd have to use circumlocutions like ([: >: ?)"0
> .
>
>
> ----------------------------------------------------------------------
> For information about J forums see http://www.jsoftware.com/forums.htm
>
--
Skip Cave
Cave Consulting LLC
Phone: 214-460-4861
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
