Ok, so I won't do that
Instead, I'll just use this as a place to say stuff. Outside the oracle.com domain.
This month I've been working on Expert One on One Oracle, second edition. It is sort of eye opening. I'm taking the book from being Oracle 8i, 8.1.7 and before specific and updating to 9ir1, 9ir2 and 10gr1. So much has changed. The single chapter that was chapter 2 (Architecture) is now chapters 3, 4 and 5. In Oracle's quest to make things easier, it has become alot harder to describe! Look at files -- lots of new "file stuff" from ASM to spfiles to flashrecovery areas. Memory, unbelievable. Describing the SGA used to be easy, how PGA/UGA memory worked -- a piece of cake.
Now, are you auto PGA memory management and what about that pga_aggregrate_target which is more of a wish than a directive and add into that auto SGA management, manual SGA management and the hybrid automatic/manual mode you could put it in -- well, 12 pages blossomed out to 35 pages.
I even have some 500 user tests in there, to show how workarea_size_policy = AUTO|MANUAL scale up in their use of memory... Wonder how I got that on my single cpu laptop?.. Actually I ran that on my dell poweredge server in the basement. It was quite fun, never did a 500 user test in my basement before. Things have changed since version 1 of the book.
As for the book, I would like to offer an opinion on books -- technology books. I was involved in a discussion on this topic and someone made the claim that
As the book, as with most do today, had to be published by a certain date we did most of the work on beta and to provide complete coverage, some was from docs.
The marketing truth these days is, if you aren't first to market with a book you won't have sales.
I really took exception to that. I don't think that is the truth. I think that was their choice. If you are writing a book on technology, as a technology "name" (a name people just trust, because they know the name), writing a book based on beta software and making suggestions on how to use it (based on beta software) without having any real world experience is a bad choice.
I can promise you one thing, my books will be last to market. When Expert One on One Oracle first edition went public, a book that says on the cover "covers Oracle up to version 8.1.7", it was one short week before Oracle 9i went production.
When Effective Oracle by Design first edition went public, Oracle 10g Release 1 followed it by four months.
In both cases, I could have had the very first 9i and 10g book on the market. The publishers would have loved it (so they think). I refused to do it. Why? Because I had no real world, in the field, been using it and breaking it experience to work from. I had lots of nice theories about how it "should" work, "might" work, "could" work -- but not having actually used it in real life, I won't write about it.
So, maybe beware of the first to market books. Other than being a new features guide (which Oracle puts out by the way...), the material contained therein may be questionable, as it hasn't been put to use by anyone yet.
I look at a book and judge it not by the cover, but rather by the quality of the technical review team. I've been very "proud" of the teams working on my books. I've learned alot from them. They are what make or break a book. I've sat on both sides of the table on this one, I've written 2 books and contributed heavily to a third. I've tech edited perhaps 10 or 12 now. I've reviewed books that were a pleasure to read, with minor corrections to be made. I've read books where I've sent back "if this chapter remains in the book, I want my name off of the list, i refuse to be associated with it (and here is my evidence why I'm saying this....)". In the end, the books that get published are better and some of the books just never get published at all (which is a good thing).
Anyway, back to the book. I'll update this site from time to time with opinions. We'll save the debunking as something for Q&A on asktom.oracle.com....