Copyright (c) 2013 John L. Jerz

How Computers Play Chess (Levy, Newborn, 1990)

Home
A Proposed Heuristic for a Computer Chess Program (John L. Jerz)
Problem Solving and the Gathering of Diagnostic Information (John L. Jerz)
A Concept of Strategy (John L. Jerz)
Books/Articles I am Reading
Quotes from References of Interest
Satire/ Play
Viva La Vida
Quotes on Thinking
Quotes on Planning
Quotes on Strategy
Quotes Concerning Problem Solving
Computer Chess
Chess Analysis
Early Computers/ New Computers
Problem Solving/ Creativity
Game Theory
Favorite Links
About Me
Additional Notes
The Case for Using Probabilistic Knowledge in a Computer Chess Program (John L. Jerz)
Resilience in Man and Machine

howcomsplaychess.jpg

Interesting history, technically simple, July 13, 1996
Reviewer: A reader
This book is a definitive history of computers and chess up through Deep Thought in 1990. Largely a survey, it rarely takes a strong point of view of its own. For someone looking for such a history, or for a basic consideration of chess algorithms from alpha-beta pruning through hash tables, killer move tables, and quiesence, it is a fine book. For my money, though, it did not go into enough depth either in technical issues such as the details of even a simple evaluation function or move generator, or in the philosophical issues raised by computer chess.

p.61 I think that the problem [creating a champion computer chess program] can be solved only by chess specialists using their creative experience. - Mikhail Botvinnik
 
p.83 KAISSA [an early Russian chess program] used a complex evaluation function involving many features. In fact it was so complex that when I asked [Mikhail] Donskoy [one of Kaissa's developers] about it he replied "...I don't even remember what is in it."
 
p.108 Black [computer playing chess] exhibits the well known syndrome: All my pieces are on their best squares. Since it cannot see any way to improve the position of any of its pieces, Black moves the king back and forth until something happens.
 
p.219 Over the last 30 years, approximately 10,000 individuals from all over the world have participated in writing chess programs.
 
p.220 To write a chess program requires a great burst of energy and concentration for a 2 or 3 month period. It is necessary to fit together many pieces of a large electronic puzzle that can never be entirely visualized. Addiction sets in soon after the first game is played, and while the suicidal pace of the first few months cannot be kept up, the programmer maintains a high level of energy and concentration for many years to come as the program gradually improves.
 
p.221 Chess programs have been developed by individuals working alone, although more frequently they are the result of a group effort with one dominant leader. The team, no matter what the size, needs a programming whiz. Every program that has won the world championship has been a team effort with at least one programming whiz... A strong chess player is also important to a team, but not as crucial as a programming whiz.
 
p.222 Most of the time spent developing a chess program is spent testing and debugging. Endless hours are consumed playing games with the program, hunting for bugs and looking for ways to improve play.

Enter supporting content here