Re: [computer-go] Pattern matching - example play

["Frank de Groot" <frank@xxxxxxxxxxxxx>]

From: "Mark Boon" <tesujisoftware@xxxxxxxxxxxxxxxxx>
Subject: RE: [computer-go] Pattern matching - example play



> To make a good Go program I'd rank the following in order of importance:
>
> 1) Lots of spare time
> 2) Lots of motivation and determination (in other words, be a nerd!)
> 3) An inventive mind.
> 4) A high rank in the game.
> 5) Strong programming skills.

I would rank it, in order of importance:

1) An inventive mind
2) Strong programming skills
3) Lots of motivation and determination (in other words, be a nerd!)
4) Lots of spare time
5) A high rank in the game.


I have a contrary opinion on attaining strong programming skills, I think it
needs a greater talent than the talent needed to become a Shodan Go player,
and I also think it takes much more investment in time to become a really
good programmer (20 years is a good estimate). There are kids that are
Shodan but there are no kids that are highly professional software engineers
that have sustained rates of a patentable invention per year. With all due
respect, you can't compare a game with the most complex engineering
profession on earth.

My (1) is by far the most important point for Go programming, as current Go
programs stink, therefore a lot of (1) is required.
I am pretty sure that a main reason Go programs stink is lack of (2) as
well.

(5) I consider to be almost of no significance whatsoever, based on my
earlier expalnation on how I see people try to put their own knowledge into
Go programs instead of adopting a scientific, systematic approach and put
the knowledge of tens of thousands of pro games in to their games.  A pro
can't voice his thoughts on Go programming, but his games speak for him.

_______________________________________________
computer-go mailing list
computer-go@xxxxxxxxxxxxxxxxx
http://www.computer-go.org/mailman/listinfo/computer-go/