TOP 10 REASONS WHY YOU SHOULD STOP PROGRAMMING CHESS

[Martin Zentner]

Here they are finally:

THE TOP 10 REASONS WHY YOU SHOULD STOP PROGRAMMING CHESS.

10. You play better chess than your program.

9. Your program is bug-free
(or otherwise: Your program thinks, that c8=N is a pretty strong move)

8. You want to have your son named Hiarcs.

7. You find that your program is in a wrong coloured bishop ending against Ananse.

6. You post to "recursive double nullmove" thread in r.g.c.c.

5. Your program beats the hell out of Kasparov.

4. Your program is pondering on a nullmove.

3. You start looking like David Levy.

2. Richard Lang is pestering you for information.

1. You start evaluating your sexlife by centipawns.

---------------------------------------------------------------------------
Disclaimer:

This list was compiled by a bunch of drunken chess programmers at the WMCCC
in Paderborn. Please send all your flames to /dev/null/
---------------------------------------------------------------------------

[chris whittington]

Martin Zentner <zen...@phil.uni-passau.de> wrote:
>
> Here they are finally:
>
> THE TOP 10 REASONS WHY YOU SHOULD STOP PROGRAMMING CHESS.
>

> 9. Your program is bug-free

> (or otherwise: Your program thinks, that c8=N is a pretty strong move)
>

THANKS GUYS - DID CHESS SYSTEM TAL REALLY PLAY THIS MOVE !?

> 3. You start looking like David Levy.
>

THEN I REALLY WOULD GIVE UP, NOT JUST CHESS PROGRAMMING, BUT LIFE TOO .......

- chris whittington