Bill Spight wrote:
I agree. You want to build up a "vocabulary" of at least 50,000 patterns.
I fall somewhere in between. First, I am not at all convinced that problems provide the best way to build up one's go vocabulary, although that can and does happen. Second, and more importantly, I think that easy problems do not provide enough of a workout. Sure, do a few over breakfast, but for a 10 minute workout at the SDK level, I think that working on 5-10 problems that are difficult enough so that you can solve only half of them in that time is better. In a real game there will be positions that you should spend a minute or two on, and I think that that's the right time to spend on problems, as well.
Redecker's books are a valuable resource.

Very interesting to hear your thoughts Bill.
I had another look at the section of the book that the first problem is from. Looking at the examples given and some of the other problems, it looks to be problems looking to take advantage of white's bad shape. The "attack" might mean "attack white's shape". I'll ask someone next week who might give me a better idea.
A much easier example;
$$B
$$ +---------------------------+
$$ | . . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . |
$$ | . . . , . . . . . , . . . |
$$ | . . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . |
$$ | . . . . . . , . . . . . . |
$$ | . . . . . . . . . . . . . |
$$ | . . . . . X . . . . . . . |
$$ | . . . X . X O . . , . . . |
$$ | . . . X O O . . . . . . . |
$$ | . . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . |
$$ +---------------------------+
- Click Here To Show Diagram Code
[go]$$B
$$ +---------------------------+
$$ | . . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . |
$$ | . . . , . . . . . , . . . |
$$ | . . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . |
$$ | . . . . . . , . . . . . . |
$$ | . . . . . . . . . . . . . |
$$ | . . . . . X . . . . . . . |
$$ | . . . X . X O . . , . . . |
$$ | . . . X O O . . . . . . . |
$$ | . . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . |
$$ +---------------------------+[/go]
If problems are not the best way to build a persons go vocabulary, what is, in your opinion?
It's been my experience when playing against western players that it is their reading strength, and basic tactics during contact fights that lets them down- I see a lot of broken shapes, allowing hane at the head of two stones, not cutting when it is possible etc. And then against Asian players, I see much of the opposite- good reading and tactical skills, but mistakes like playing too close to thickness, invading deeply when it's not needed or jealousy of territory, poor choices in opening (preferring to start an immediate fight rather than take a big point).
Your comments r.e. easy v. challenging problems is something for me to think about. Perhaps I'm biased towards easy problems because I just enjoy them more

I like to feel like I have accomplished a lot, rather than failing half the time. Actually, thinking about it now, if failing half the time scares me maybe I should choose a different game to play! Actually I feel that I maybe missed some elementary education early on when I started playing. I lost a game a few weeks ago by responding to a hane on my L+2 group incorrectly. Actually reading it out shouldn't be a challenge to me, and if it was presented as a problem I would likely get it right. But alas I did not read accurately during the game. I think had I solved many problems involving that shape, I would never get it wrong during a game. Immediate recognition of the shape would have given me the clue I needed. I miss a lot of opportunities to cut, capture, connect etc., that would be more apparent if I could just "see" that there is a better move there.
For me, solving problems seems to have two purposes; to improve brute reading strength- depth/breadth, secondly to improve (call it what you will) intuition- the ability to immediate see a shape and know that there is a good move to play. Harder problems seems to improve the former, as well as introduce new moves for the latter. Easy problems seem to cement the latter, ensuring that during a game those moves become immediately apparent. I'm guessing that your suggestion of over learning helps with the second; to practice the harder problems (hard because you cannot see the possible move) until they become easy (you can see the first move).