Things have not been going well with the Chess studies this week. Four things in a row went bad, causing me to reconsider the whole idea. I mean, if you’re not having fun, why do it?
I did promise an explanation of how I do the knight’s tour, so here it is. To be clear, the knight’s tour is where you take a Chess knight and move it around a Chess board so that it goes to every square once without going to any square twice. I use it as a visualization exercise to help see possible knight moves when playing Chess. I find it is also good for practicing thinking ahead a few moves, because at certain points you have to be careful about where you will be three moves later.
One of the thing you are supposed to study for Chess is visualization. That’s what they call being able to see what the board will look like three moves into the future. Like many things in Chess you can build visualization up from small pieces. First you learn to be able to tell what color a square is without looking at it, and then which diagonals it is on, and so on. Being a programmer, I wrote a computer program to generate random visualization questions for me to answer. In a fit of originality I decided to call it Visualizer. I’ve set up a page for it here on WordPress, and one at the pygame site (since I wrote it in Python and pygame).
In following with step 9 from my first truly analyzed Chess game, I shifted my Chess work to address the problems I found with my play. Rather than continue reading my new Chess book (Reassess Your Chess) on Wednesday, I poked around on the internet and found some articles on the thought process in Chess. Today at work I had a lot of test runs to do on my new search program to deal with our new Sharp Floor system (more on that in the next post). While they were running, I did what I probably do best (and like to do most): I analyzed what I had learned about the thought process in Chess.