Intro
"There is no one book that is best for every person. There couldn't be one. People are too different in the way they learn, in what they already know, in what they need, in what they want, and in what kind of effort they are willing to make." Bjarne Stroustrup (The creator of the C++ programming language.)
I always try to remember this whenever I have to judge a writing effort.
Whom is this book for?
This book is for a beginner database developer who wants a simple process to follow and some light intro to the fundamentals of database design.
What does this Book offer?
The main aim of the book is to offer a database development process that would help a novice get the basics of database development through light weight process the writer follows and I insist on the word light weight since the writer aims at abstracting some hard concepts in simple ways. Thought the process tips are given on how to conduct an interview, how to name tables, how to search for fields, light weight normalization.
What I liked?
This book is well written, simple and an easy read. The best of the book seems to be at the end.
What I didn't?
If you didn't, go read the Stroustrup quote I wrote in order not to miss understand me, the book seems to be aimed at shallow people :) never the less its good, the writer seems to think that he is the only good database developer and that he is always right
Conclusion
The book is not so deep but yes you may be able to design your own database system.

Intro
"There is no one book that is best for every person. There couldn't be one. People are too different in the way they learn, in what they already know, in what they need, in what they want, and in what kind of effort they are willing to make." Bjarne Stroustrup (The creator of the C++ programming language.)
I always try to remember this whenever I have to judge a writing effort.
Whom is this book for?
This book is for anybody interested in managing a web project or being part of a well managed one. (Need to be more specific read my conclusion?)
What does this Book offer?
The book seems to offer tips more than any thing else, some guidelines about the roles of personals in a web team, a "Web project method", and a case study.
The part regarding web teams seems to be good and gives a lot of insight.
The case study is full of tips.
The method, (Here where my good feeling change) a high level view, full with tips but no real details, never the less seems to be good.
What I liked?
This book is very well written, tips every where (even in the acknowledgments), the graphics are nice, and is good for the right people.
What I didn't?
If you didn't, go read the Stroustrup quote I wrote in order not to miss understand me, the book didn't help me a lot, I m a web developer searching for an all around web process to follow in my projects, and this book simply doesn't offer. The writers seem to ignore that there are software systems behind those web sites. More details wouldn't have harmed.
Conclusion
I feel that the most people that would benefit reading this book are already practicing web project managers.

Intro
"There is no one book that is best for every person. There couldn't be one. People are too different in the way they learn, in what they already know, in what they need, in what they want, and in what kind of effort they are willing to make." Bjarne Stroustrup (The creator of the C++ programming language.)
I always try to remember this whenever I have to judge a writing effort.

Whom is this book for?

This Book is for a non C++ programmer, a beginner to intermediate C++ programmer interested in learning the fundamentals of C++, some backward compatible features related to c, and some advanced C++ features.

What does this book offer?

C/C++ Basics. (Very nice converge)
Pointers, arrays (I finally fully understood how they work "or at least that's what I think")
General Programming basics (Some what but the writer doesn't claim to do)
Introduction to OOP (Just an intro)
C++ OOP Features (Very Good coverage)
Advanced Features "Namespaces, Generic programming, Exceptions " Brief but thorough.
STL (Brief but very good)

What I liked?

This has been one of the easiest books to follow from a collection I have read it builds up information in a very nice way (and yes as somebody said while reading some parts you would feel that you are in a classroom with the instructor answering some of the questions you have in mind before asking "Some parts").

What I didn't like?

Ok, I am never satisfied.
I feel that the book should have offered more (computer science basics like the Dietels do). Or that is what I wish.
As some body said the writer seems to have more experience with C than C++ I may have to agree but this doesn't mean that he came out short. Anyway you are not going to get the same OOP Intro as the one you'd get reading the "Thinking in Java Book" but never the less.
Damn the Typos are annoying.

Conclusion.
A very good written book not a classic though (I have a very high standing regarding classics).

Intro
"There is no one book that is best for every person. There couldn't be one. People are too different in the way they learn, in what they already know, in what they need, in what they want, and in what kind of effort they are willing to make." Bjarne Stroustrup (The creator of the C++ programming language.)
I always try to remember this whenever I have to judge a writing effort.

Whom is this book for?

This Book is for a non C++ programmer, a beginner to intermediate C++ programmer interested in learning the fundamentals of C++, some backward compatible features related to c, and some advanced C++ features.

What does this book offer?

C/C++ Basics. (Very nice converge)
Pointers, arrays (I finally fully understood how they work "or at least that's what I think")
General Programming basics (Some what but the writer doesn't claim to do)
Introduction to OOP (Just an intro)
C++ OOP Features (Very Good coverage)
Advanced Features "Namespaces, Generic programming, Exceptions " Brief but thorough.
STL (Brief but very good)

What I liked?

This has been one of the easiest books to follow from a collection I have read it builds up information in a very nice way (and yes as somebody said while reading some parts you would feel that you are in a classroom with the instructor answering some of the questions you have in mind before asking "Some parts").

What I didn't like?

Ok, I am never satisfied.
I feel that the book should have offered more (computer science basics like the Dietels do). Or that is what I wish.
As some body said the writer seems to have more experience with C than C++ I may have to agree but this doesn't mean that he came out short. Anyway you are not going to get the same OOP Intro as the one you'd get reading the "Thinking in Java Book" but never the less.
Damn the Typos are annoying.

Conclusion.
A very good written book not a classic though (I have a very high standing regarding classics).

Like any other book some people like it but others don't, since readers come from different backgrounds it is some time's your background and previous knowledge which will lead your absorption to a books material, since I cant assess any of the potential readers ability's and background I will give you a general reason why I will not recommend this book.
When Material is tough and hard to absorb a writer should try doing one of two things. He could build up knowledge from the easy stuff up, and some extra explanation or he could at least keep you interested and willing to repeat what you have just read and these writers did neither.
Review End...

Like any other book some people like it but others don't, since readers come from different backgrounds it is some time's your background and previous knowledge which will lead your absorption to a books material, since I cant assess any of the potential readers ability's and background I will give you a general reason why I will not recommend this book.
When Material is tough and hard to absorb a writer should try doing one of two things. He could build up knowledge from the easy stuff up, and some extra explanation or he could at least keep you interested and willing to repeat what you have just read and these writers did neither.