Re: New series of articles on Code Golf

Jasper wrote:=0A> you know, I wish you'd do one of these on the choose golf=
. Probably a=0A> very straightforward solution, but at the time I was very =
annoyed that=0A> I couldn't get those extra characters.. codegolf appears t=
o be down=0A> now so I can't even be reminded how far off I was.=0A=0AIf it=
 makes you feel any better, I was similarly very annoyed during=0Athat game=
.=A0codegolf.com has been down for over a week (maybe forever?)=0Aso I can'=
t even check if I'm ahead of you or not. :)=0AIIRC we're tied two or three =
strokes from the lead. The google cached=0Apage only shows the top ten and =
you and I are both missing. I notice=0Athat a couple of likely lads (terjek=
 and tybalt89, aka Rick Klement)=0Aboth effortlessly=A0found the "obvious" =
35 stroke solution though ...=0Aso if they are listening, you might be in l=
uck.=0A=0ABTW, Rick Klement is the fastest golfer in the west; in the grid=
=0Acomputing challenge, Rick got the lead at 45 within hours but got=0Acomp=
lacent. After two weeks of effort I finally caught him on 45,=0Abut then ma=
de the fatal mistake of posting a 44 before thoroughly=0Aanalysing it. With=
in an hour or so, I realised I'd missed an easy=0A43, but too late. Posting=
 that 44 must have provoked Rick; in any=0Acase, he responded to my 44 with=
 a 43 within _minutes_. I was just=0Aabout to triumphantly post the "winnin=
g" 43 when I noticed, to my=0Ahorror,=A0that Rick had beaten me to the punc=
h! Reminded me of the=0Agood old days, just for a little while. :)=0A=0A/-\=
=0A