Great book for beginners on the subject... even for experts ! Even if this book was edited in 1997, it is a good apoptotic reference ! You like cell death subject ? You'll like this book. Based on pharmacology, you will take a look around lots of areas.. heart, GI tract, genetics, brain, AIDS and signalling pathways... You will like this book.

The first time laid my eyes on this book; to tell you the truth I was a bit frightened. I was expecting a very complex law book that would take me more than one pass over the material in order for me to get the material. This was not the case, the book really made the subjects easy to understand and the writers made the book very easy to read. The tables and diagrams also make the book even better for those of us that are more of the visual learner types. I would recommend this book.

Thomas Sullivan provides a clear, consise, and easy to use reference guide for anyone to use. This book not only contains actual text of some major environmental laws, but it also sites case studies and court decisions, all in an easy to read format. This book is a must for anyone dealing in environmental matters, and is a good source of reference for anyone concerned with the environment and public policy.

I bought this book for a college class. I really like the cover, I don't know why. It has some pretty good facts in it besides the same ol' polysci stuff. If I wanted a text book just to have about the US government, I would probably get this one. It wasn't a bad price either.(I bought it from a dealer).

The watercolors of JMW Turner have the concise, simplified vision of contemporary art even though they were painted in the mid 1800's. This survey shows the progression of this master of light and delicate color from tightly delineated landscapes to the atmospheric , nearly abstract vistas of his late career. The reproductions are supported by quotes selected from writings contemporary to the paintings. This book provides an inspirational overview of the work of Turner and belongs in the library of the serious watercolor artist.

Thomas wrote a good book on a quite specialized subject. Although finite difference schemes have been traditionally viewed as a game field for physicists, they are given today much more commercial attention as financial option market evolves. Those who seek standard numerical recipes are advised to read this book. You will enjoy it (easy reading) and learn. But the book may not satisfy quests of a more rigorous readership. It abuses the Fourier method in stability analysis while considering only PDEs with constant coefficients. The bibliographical work has not been done at all. In addition, the cover does not state that this is the first book of two. I'd also advise to read G.Marchuk "Methods of Numerical Mathematics" (Springer, 1982) where a more general approach for stability of numerical schemes is developed.

The book is complete and detailed. It gives the conmputer developer what they need to know in order to comply with EDI standards

this was truely a great book and i enjoyed reading it, however i desired more interpretation on "the secret sayings of the living Jesus." i thought the authors would elaborate in depth the sayings they've discovered, but rather they were just presented. I'd recommend buying the book, that is for sure, but you should research the gospel of Thomas deeply before you undertake the reading.

I found the material to be insufficiently motivated. Unfortunately, the authors take some of their variables from an old english alphabet, which just ruins the aesthetics.
I had this as the text for a math/philosophy class. The philosophy students looked confused by some of the math. The math students knew what was going on, but didn't know why it was worth doing.
Basically if you're not yet a grad student with a stellar background in math and logic, there's got to be some better way to learn this material.

This is probably one of the best introductions to mathematical logic for those with sufficient mathematical maturity. I especially enjoyed the treatment of the completeness theorem for first-order logic (using Henkin's Theorem), and the treatment of Godel's incompleteness theorem, and Trachtenbrachts incompleteness theorem for second-order logic. Compared to other books, this book tends to go light on the notation.

If you do not have sufficient math maturity, then you may want to try Smullyan's book on the subject.

This is *the* excellent mathematical logic book for anyone sufficiently familiar with the aims and spirit of mathematical logic. However, it is probably *not* suitable for a first introduction.

Some of the informal discussion expects the reader to supply the sense, and hence could be misleading for a novice (or even incorrect if taken literally!) On the other hand, the discussion is crystal clear and illuminating for someone with a bit more of background.

This book will not provide philosophical enlightenment to students of logic (esp. to those who seek such enlightenment in the first place), but it will provide good understanding of the study of general mathematical structures and their relation to logic. The prospective reader should first get acquainted with the model theoretic point of view (i.e. with its aims and presuppositions) before tackling this book. Good sources are: the first few chapters of Wilfrid Hodges's "A Shorter Model Theory" and the relevant articles by Jaakko Hintikka which were published in the journal "Synthese" in the late 1980's.

BE WARNED:

- This book is on process and *NOT* architecture.
- It is for managers and not for developers.
- It concentrates primarily on project management issues.
- The book is filled with personal opinion.
- It is spotted with questionable "anicdotal" evidence.
- It will not save a project in crisis--but maybe the next project.
- Less than half of the book is even worth reading.

Anyone looking for a companion to the GoF Design Patterns book will be *sorely* disappointed in AntiPatterns. This is not a "bad apples" version of architecture patterns. Instead, it devotes itself to describing symptoms resulting from failed or missing processes. As far as being a process book, it's barely average. It has some good insights and might help a manager spot emerging problems, but much of the advise is too generalized to be of much applied use.

You can tell that this book was written by four seperate people. One of them did an outstanding job (making about 1/4 of the book 5 stars). He describes solutions with detail and clarity. One does a decent job. Two of them are clearly jargon blowhards who have trouble completing a thought. Their chapters offer no detailed advice on what action to take but rather generalize and summarize on vague remedies. For instance, "put more money into architecture" is one fortune cookie they offer.

I wish they had a critical eye preview the book and point out all of their holes -- both in supportive argument and in solution description. Often times a paragraph introduces a concept, and the author neither explains it nor offers any futher reading.

The book is spotted with questionable "evidence" supporting their opinions. Here is my favorite quote of the book, "Meeting productivity gains are must more dramatic,... and we have seen productivity gains over 100,000:1." They have seen fifty years of work performed in an hour! Talk about overselling a process improvement!

And don't get me started on their misuse of the term "refactor."

I can't believe the number of reviews on this site that compared the book to Design Patterns from GOF. If you bought it expecting the same, write yourself the one-star review. This book does have some problems, but it really does a whole lot of things very well.

- It's easy, and fun, to read. The authors expertly inject humor and life into a dead topic. A dull book with good ideas will rot on the shelf.

- It provides a fresh, new angle that has value. We programmers do not learn enough from war stories told around the water cooler.

- It provides the other side of the design pattern. You really do need both, and this industry needed someone to take a stab at creating a template for antipatterns. Consider health care. You need diagnostics and preventative care. Ditto for auto maintenance. Operations research has been built around building models that work while trouble shooting the kinks in a system. The authors did a noble job of seeing the vacuum and stepping up to fill it.

I find it incredible that this book has been slammed for something that it does not pretend to be. If you wrote a one star review because this book was not the second coming of the Design Patterns book, then shame on you. What you will get is a humerous look at some very real problems around software development. The bias is clearly toward project management, and that is a appropriate for a first book on antipatterns. That much was clear to me from browsing the book for a minute or two. Great job, team.

If I had a criticism, it would be that the contributions from the four authors were not better coordinated. After writing two books with two additional co-authors each, I can testify that it is a difficult problem to solve. Still, better coordination could have helped. Five stars for the writing style and the concept. That's why this book is a smashing success.

Most people make the transition from C to C++ or to Java with little trouble, if any. If you look at their code, you'll understand why: People figure out clever ways to do C programming in any language -- No person, no discipline, no environment, and no programming language can FORCE you to program in an object oriented way if you really don't want to. So you don't, and you don't reap the benefits of object orientation either, even though you're using an object oriented language... This means your code is not factored properly, this means you don't have re-usable components, this means you don't get the orthogonality and modularity and reduction in program complexity that object orientation promisses. What would such a program look like? It look like hell!

It turns out that people misuse object oriented technology in similar ways, forming not "patterns", but rather "AntiPatterns." The AntiPatterns book is like a pathology textbook for software engineering: It helps you identify projects gone awry, what were the basic reasons for the program to have developed the way it did, what are the consequences of such pathological development, and how to fix things. The idea is not to have to do a complete re-write, but to either isolate the working-but-malstructured parts of the program or fix them gently, a small piece at a time, or both. The book will also teach you how NOT to think about patterns and object orientation.