Finding my way in the chessdevelopment- and training jungle in order to improve my rating.
Saturday, April 02, 2011
Blown away by the idea of Checks, Captures and Threats
. . . I used to think that CCT of Dan Heisman was some kind of blundercheck. Since I don't drop pieces very often, I didn't consider it to be very usefull. But in search for tasks to automate during calculation I stumbled upon it. In fact looking for CCT is a method for pruning the tree of analysis. In stead of learning to calculate branches very fast, it is much better to know when there is no reason to calculate a branch at all! The idea behind it is fairly simple. If there is no CCT, there can't be no tactic. If there is no tactic, there is no need to calculate.
I have a tendency to end up in time trouble. I tried to manage that by avoiding complex openings like the King's gambit. The first tests with CCT during serious long games show that I calculate way too much!
Using CCT is not as straightforward as it sounds. So I'm first going to apply it to the >2000-rated tactical problems of Chess Tempo to get the hang of it. Once the thoughtprocess is clear, I will try to automate it. That should kill two birds with one stone: speeding up a sound thought process and pruning branches from the tree of analysis!
And of course continuing with automating tactical vision.