talking to an author more insightful than reading the 200 page thesis,

Find the right books, and it'll probably be far more rewarding than talking to an author, simply because of the information density and better organization that you can get in written form.

An hour of reading Hennessy and Patterson's excellent book on CPU design will teach you a hell of a lot more than six hours of classes. I speak from recent quantitative experience here, which is where I got those specific numbers. The exceptions to this rule are local: particularly hard-to-understand concepts like the Tomasulo algorithm are a lot easier to wrap your head around if you have someone to walk you through them. But for the most part, a well-written textbook can teach you better than a person talking with you.

One problem is that most textbooks just aren't written that well. Often they're too concerned with signaling academic status, and they forget to make the book something that people will want to read. Just because an author can go off on a tangent about graph isomorphisms doesn't mean they should. Other times they get bogged down in obscure details up front, killing off people's interest. There are other failure modes, too depressing to list here.

By the way, I think that one reason why wikis are so easy to learn from is because you can skip past the boring stuff until you need it. This makes reading a wiki more fun, and also leads to tab explosions, keeping you hooked. I figure that this could significantly improve on the traditional textbook model, despite all those nice things I said about it earlier in the post.

(In honor of the tab explosion, I've stuck in a bunch of links to pages that might be interesting.)