This book is written by a highly sceptical radio personality, who has used every means at his disposal to debunk the whole medium idea. George Anderson cooperated with the book and the testing.

I was particularly interested to read some of the case studies, understand some of the rationale behind after death communications. It helped to understand in depth the passing of my brother, and by being able to get this perspective to deal with it better. I was also very interested in what he said about the nature of the afterlife. There is no hell per se, there are just different levels based on how spiritually advanced people were in life.

This is the kind of book to read when you need to read it, when the time is right. I passed my copy along to my sister who was also very impressed and she in turn passed it along to someone who found it to be a great comfort. This book could be helpful to someone you know.

In grief, the one piece of knowledge that might help you get the perspective that helps you to deal with the loss can be so elusive. This book can help you. I would also recommend Lessons from the Light, which focuses more on the afterlife.

There was some stuff that I thought he experimented with that didn't quite work for me. There are two poems that he frames into shapes, one of a dollar sign and one of a skull. I thought the dollar sign one was very funny, but it was gimmicky. The skull one was too bitter, but I guess that's an emotion too. The "Ode to a Rag Doll" poem was very touching, and for my whole life I wish someone had written a poem like "Forbidden" for me. And there are a couple of others in there like that, really good love poems. The two haiku poems were really good; one was very amusing and the other I just adored because my mom was Japanese and she loved eastern poetry and she would have liked that one alot. Theres probably more than 80 poems, so I can't review them all, and I'm not even mentioning my favorites (except for the Cage and the Forbidden poems).

The closing was very fitting. Someone else wrote that now she wanted to know what happens to the man next, and I hope I don't have to wait more than a decade to find out, either.

To summarize, I gave this book four stars because I think five star books should be classics or staples on everyones booksehelfs. But I am very glad that I read past the first couple of poems because it was so worth it, and it took me on a ride that I was in no way expecting. It was very emotional and fun. Each poem made me think about my experience through life, and like my life I didn't know what the next poem was going to be about, or how my life would turn. I related to it FAR more than I thought I would relate to a book of poetry written by a man. It wasn't an artsy-phartsy collection of poetry, it was just very open, honest, and I have to say really brave for the man to let you in the way he did.

I have read the book twice, and my advice is to pick up a copy and do the same. Bring kleenex and let a friend borrow it.

Fran

I found so much of myself in this book, I thought it was about me. Sadness, happiness, rage, I related. I borrowed it from a friend at work, and it was really funny because the poems that she thought were going to me my favorites were really good guesses, but not my favorites. Poems like "Forbidden", "Saturday After Work" and "Antihero" hit me like a ton of bricks, but the ones I liked the best were the ones like "Day 11,736", "Regret", "Pretzel" and "Collusion" (oo, and "The Forgotten Words of God" too, very existential) were my favorites because they were a little more abstract and mysterious but still descript enough to draw conclusions by.

Anyway, I need to say also that although the title makes you think that the book is all about relationships, that might be a little deceiving. Some relationships are parent/child or other family relationships, some are about relationships with friends, pets, nature and experiences. There are a few poems that are just about fun. All of them put together are like reading a person's life as they grow up.

Anyway, pretty cool, and I think that this kind of writing should be looked at by high schools and colleges as a project for there students. I highly recommend the book because it's kind of like a movie that you can go back to and feel comfortable from watching it. I hope that made sense.

The poetry is not complicated. It is easy to read and enjoyable, vivid, and what made it fascinating to me was that in reading it from cover to cover, you saw this man evolve from a seventeen year old to a mature adult. I have kept journals since I was 13, and reading this book made me wish that I had kept mine in poetic form too, or even better, made me think about taking my writings and converting them into poetry so I can relive my life in my words as I have relived his as an observer.

I highly recommend "While Searching for Love and Self" not only because I enjoyed it and will certainly enjoy it again, (and find more layers in it each time), I also recommend it because everyone will find forgotten memories and emotions in it. It's impossible not to.

Refactoring is a book which details simple techniques of fixing your code to facilitate making changes.

The book's main feature is a large catalog of at least 50 refactoring patterns (presented in a similar way to Design Patterns) with a name, example, and motivation for using it. The patterns are described using UML. There are several other chapters of interest, including one on "Bad Smells" which lists many telltale signs of poor programming and how to fix them.

Maybe I'm just showing my lack of sophistication, but Design Patterns went over my head. I only "got" a few of the patterns. But this book is much more accessible to an intermediate programmer who wants to improve his coding style. If you've ever wondered how to write more maintainable code this is your book. One good thing about this book is it's directly applicable to almost every standard procedural or OO language, whereas Design Patterns are pretty much for OO programming only. Even if you are writing VBScript or Javascript for your web page you could use many of the techniques illustrated here.

Highly recommended. Buy this one.

However, Fowler doesn't stop there. He presents rationales for refactoring (with an eye towards making a case to management) and much detailed, practical insight that comes from experience, but is rarely expressed so concisely and elegantly. I also appreciated the importance Fowler placed on unit testing; in fact, using unit testing makes refactoring happen much more quickly, and leaves you with a lot more peace of mind besides.

I read the book cover to cover and enjoyed nearly every page. The book has added a lot to my value as a developer, and was a lot of fun in the bargain. I don't think a whole lot more needs to be said. Just buy it, you can thank everyone who told you to later.

Fowler suggests refactoring a program to simplify the addition of new functionality. The program should also be refactored to make it easier for human readers to understand at the same time.

He also insists that each step is small and preserves functionality, and on frequent unit testing with a comprehensive test suite.

Half of the book consists of a catalogue of refactorings. He gives each refactoring a memorable name, such as "Replace Type Code with Subclasses". He illustrates the design transformation with a pair of UML class diagrams, and has a standard set of sections: Motivation, Mechanics and Example.

The Motivation is a prose section that describes and justifies the refactoring, showing the relationship to other refactorings.

The Mechanics is a sequence of steps needed to carry out the refactoring, shown as a list of bullet points He expands on some points.

The Example is where the value of this book lies. Fowler takes a fragment of Java code, and takes us step by step through the refactoring. The code is small enough that he can show it all each step of the way without overwhelming us, but is large enough to be realistic.

The code is clear enough for non-Java programmers to follow. He explains his code well enough for the book to function as a Java tutorial where the meaning of the code is not obvious. One or two of the refactorings are specific to the Java object model, and do not apply to other languages. Other languages would benefit from similar treatment, but there are very few language-specific refactorings.

The book is very much of the Design Patterns movement, with frequent references to patterns. The aim of a factoring may be to achieve a particular pattern, or it may take advantage of a particular pattern. The book can be used as a tutorial on Design Patterns.

I have a small number of complaints. Fowler advocates the use of refactoring while studying code for a code review. One needs to be very sensitive to the feelings of the programmer here, especially if he or she is a novice. The reviewer should read the code with refactoring in mind, and possible refactorings recommended, but it is for the programmer to make the changes.

Reading this book has inspired me to refactor some of my own code. My mistakes underlined the need to take small steps, and to test frequently. I spent a day building a useful Delphi testing framework from the description Fowler gives of the JUnit testing framework. The one category of code that does not seem to lend itself to this approach is some highly coupled parsing code. While I can extract small blocks of code, they remain tightly coupled with each other, and it is hard to give them meaningful names. The answer here may be to use the top down approach of recursive descent, rather than the bottom up approach of refactoring. Perhaps recursive descent can guide refactoring. Refactoring is largely a local approach. One can almost say a pinhole approach. Sometimes a global view is needed.

In summary, I would say that this very good book would be of use to Java programmers who have some understanding and much bafflement. It is very good for us older dogs who have become a little jaded and need some new ideas and motivation.

I, extremly recomend this Book!

·Lack of precise topo info. So, what do you need? Easy-to-read 3-D slanted terrain maps or overhead topo maps with elevation lines and numbers?
·No GPS waypoint info. Many of us now have handheld GPS receivers and want waypoints for trailheads, trail intersections, and scenic points as a minimum requirement
Summary: With the exception of lacking topo and GPS info, this book would be the only resource one would need for Pt. Reyes.

But there's more! The book is packed with information about the history, geology, flora and fauna of the area, including black-and-white illustrations. Sections on exploring tidepools, precautions and general area information make this a very complete guide that would be very helpful to any visitor to the area. It's small enough to take along on your travels, but don't let that fool you - this guide covers just about everything you'd need.