This book shows one topic per page or two-page spread, which makes for a rather choppy reading experience. Each topic has some introductory paragraphs, and some screenshots of code with numbered "steps". I think it might make a decent desk reference, except for the rather odd trick of leaving "fill in the blank" spots in the code, presumably to encourage learning. The "blueprint" scheme gets old quickly, and there's too much whitespace that leaves me wishing for more explanation. I didn't get too far in this one.