I would be more inclined to do this if the book is non-technical. When you commit to reading a technical book, you're committing yourself to more than just the time spent reading: you're committing yourself to the time spent applying and fully understanding what you read -- installing tools, tinkering with syntax, coding, and so on. I've got enough of that now.

With non-technical books (literature, history, quality-of-life), most of the time will be invested into actual reading, with a bit of pondering and maybe discussing. We can have a conversation right away, and there's still knowledge and insight to be gained.

Here are some non-technical books I'd like to read:

* How to Read a Book - http://amazon.com/dp/0671212095

* Influence: The Psychology of Persuasion - http://amazon.com/dp/006124189X

* Liar's Poker - http://amazon.com/dp/0140143459

* Growing a Business - http://amazon.com/dp/0671671642