Earlier quoted context omitted.
He does not give the answer. Welcome to graduate school! (And, for that matter, real life.) As in grad school, the secret is: If you can't figure it out, ask around. Form teams that stay up until 3am waving their hands and sketching on chalkboards. If nothing else, it's a bonding experience that you'll treasure for life.
I get your message, but the problem is this is not grad school. This is a book; one way communication. I have no one to ask, as I am the only one I know who has an interest in coding. Of course I can always ask on the web, but having to break off from coding, pose a question, and then wait for it to get answered before I can continue really breaks up my learning curve.
I've been programming professionally for almost 20 years. What you described right there is the fundamental skill/activity I have performed. Whether waiting for a spec, or decision if this feature is going in, or most commonly like your self looking for answer to some problem I don't get.
Good programmers either know everything (ha) or know how to learn/find the answer quickly. It's a great skill to start honing now.