It's an interesting article, but I think it's an oversimplification. In CS (the game), there's some strategy, but most can be picked up on the fly. There isn't a need to abstract away details, there isn't loads of theory that can help you make better choices. You're either more or less proficient.
I think the analogy breaks down for CS (programming). There are a number of concepts you won't likely grok without first reading them. A much better strategy is to read then do. Both are necessary, and you need a balance. All doing or all reading won't get you as far as a balanced approach. Programming is significantly more complex than playing a video game.
For me, it's a cycle. I have trouble reading about something when I don't know WHY I am reading about it. If I 'do' first, then hit a wall, then read, then I really care about the reading because I've got skin in the game. Then I'm trying to solve a problem, which makes me happy.
I think the analogy breaks down for CS (programming). There are a number of concepts you won't likely grok without first reading them. A much better strategy is to read then do. Both are necessary, and you need a balance. All doing or all reading won't get you as far as a balanced approach. Programming is significantly more complex than playing a video game.