Languages Books

After 2 days of intense reading of Corba for Dummies, I am still a dummy when it comes to Corba. However, after reading first few chapters, I know I won't be a dummy for long. Will SAMS publish more updated edition (for Visibroker 4.x and Java 1.2)?

This book helped me get off the ground when I was trying to convert some Java/TCP code to Java/Visibroker. Very similar to Programming w/ Visibroker.

I have not yet read this book but, the reviews about these books tells me that this is an excellent book.

This book is the difference between going home at 6 p.m. and 6 a.m.

I've been working with Visibroker for Java for about 3 years now. The documentation that comes with the product itself is so bad that the only way I learned anything about the product was from experimenting with it.

About six months ago, I bought this book. I learned more from reading this book than I did from years of working with the product itself. (Usually it's the opposite.)

If you working on a project using Visibroker for Java, or any ORB for that matter, you must get this book. It will save you hours of frustration and you'll have time to spare to play Unreal Tournamnent.

This is a very good book if you are using and JDK 1.1.x and Visibroker for java 3.x.

If you are using Visibroker 4.0 and jdk 1.2 , you may need to read the Visibroker 4.0 documentation on compatability issues before using this book.

There are also some minor typing errors.

Overall This is a great book.

I've read quite a few of Jim's works over the years, and he has never failed to impress me. This book should be required reading for any project manager!

My initial pre-read perception of this book was that it was going to be just another perspective of agile methods. I was wrong. Coplien and Harrison have dissected development teams to identify the key criteria leading to successful efforts and high-performing teams. Beyond process, this book identifies the organizational structures required to make the processes work.

From an organizational perspective, roles and responsibilities within your development teams are a primary success criteria for your agile (or any other process) adoption. This book presents how and why key roles within your teams work and why teams without these key roles don't work. The way they have presented the material provides for a quick cross-reference when you are looking for solutions to help your teams.

Beyond the organization patterns themselves, I believe some of the richest material in this book is presented in the last few chapters as they present the history and importance of organizational structures, roles and responsibilities in applying process - "Process emerges from structure, and structure emerges from values". There is great value in this book beyond most software development process books.

As project managers, most of us who've been in the field working for a while come to realize that successful project teams are more the result of "good" ongoing social engineering of one sort or another rather than just dumping an almost randomly selected group of people together, coming up with an MS Project Plan and saying "do this" (the Death Star approach, all to common in large traditional process-driven IT shops). After this has happened to you, painfully, you begin to come to the realization that perhaps there's more to project management than the mechanistic "people are interchangeable resources" PMBOK-style approach.

If it hasn't already, it begins to dawn on you that the "soft" side of project management (client relationship building, communication within the team and between teams, team dynamics and team morale, motivation, empowerment, commitment, a human-style of project management) are as important or even more important than the technical work and the technical skills required. Most of us have run across teams with prima-donna's who think they're the cat's whiskers, be they project managers or technical personnel, who have the personal graces of a warthog and who are incredibly destructive to team morale and team performance. They continue to exist, sadly, and because they often deliver, albeit at the expense of everyone who works for them or with them, they continue to survive in "Death Star" style IT shops where delivery is all important and the style of successful delivery means nothing or is short-sightedly disregarded. OK, so that's my rant.

Now for the book. We've all seen successful projects and successful teams (or at least, I hope we all have). Some teams gell and perform way above the norm. What this book does is distil over 100 successfully applied organizational patterns of one sort or another from real projects in real software development groups. These patterns are broken down into logical groups (Project Management Patterns, Piecemeal Growth Patterns, Organizational Style Patterns & People and Code Patterns) which are dissected and explained, with examples provided. What the authors have done is to identify and describe key organizational patterns which are used by successful teams - not processes, but organizational structures of various types that are needed to make processes work successfully. A large amount of practical experience has gone into the content - over ten years of research experience from the authors alone.

I've read a lot of books on Agile, but this is the first I've come across that sets out organizational patterns - and does it so effectively that you'll wonder why all the stuff in here never occurred to you before. As you read through the book, you'll see patterns that will make sense, the kind of "ah-ha, that's what the problem is and this is how I can dom something about it" sense. You'll find this book useful in that the contents can be taken and applied right away. It's easy to pick what is most useful for your team, what can be applied immediately and what would be nice later on, once some of the basics are in place. The content is practical in that you can easily identify what your problems are and what pattern would help fix it, why the pattern is intended to fix it, and there's good advice on how to introduce new patterns.

With over 100 patterns, there are a lot, but they're set out concisely, a page or two to each pattern. There's no fluff, it's well-written, there's no appreciable bias, there's a lot of material, including some good coverage of the importance of effective organizational structures in applying process. As we all know, all the process in the world will not a great project team make. The book's structure is coherent and well-organized, the patterns described can be used individually or as groups and the authors give you some pretty good ideas as to what's immediately useful.

And the pictures all the way through the book are great! A nice humorous touch that helps make the point each time. Overall, I'd recommend this book very highly as a resource to anyone managing a project / team, whether Agile or not. There's a wealth of practical advice in here that any project manager could take and use, although the orientation is towards Agile Projects. An added bonus - unlike many technical books, this one won't date quickly - organizational patterns that work don't change much over the years, unlike programming languages. From a practical point of view, I've applied some of these patterns to teams I work with and the results have been positive - I've also shared the book with co-workers and they've all found it both illuminating and useful.

This book has to be The Grand Unifying Theory of Software with respect to managing the people and processes involved in software production.

To anyone who has worked in the software industry, this book is clearly the product of an enormous amount of practical experience in both management of people and projects as well as the development of software.

Coplien and Harrison have written a book which both the project manager and software engineer will understand and will immediately be able to apply to their respective work environments: This is because the book cunningly captures essential organisational concepts using a framework that is familiar to software engineers. Thus, the concepts will be by recognised by staff trained in business as well as those trained in software and systems.

I strongly feel that the material covered in this book can achieve a common communication basis between managers and engineers, and can help business developers understand the nature of their people and organisation.

If I could insist that all people in software read this book I would; but without the policing power, I can only highly recommend this book to those involved in all facets of software.

OK, I have to admit, this is the first book review I've ever written on Amazon and having read a lot of good books I should probably get off my a** and write more :-)

As a former developer and now a software development manager, I have come to realise that the "soft side" or sociology of software projects (communication with clients, communication with teammates, project management, team dynamics, cultural issues, morale, division of work, remote collaboration, etc) is considerably more complicated than the programming work itself.

Over time, you start to see patterns emerge such as "start a large project with a small experienced group and gradually phase people into a project as time goes on". This book does by far the best job of cataloguing and explaining dozens of these patterns related to (1) software project management (2) structuring, building and nurturing software project teams and (3) organization and division of development tasks to maximize the effectiveness of the team as a whole.

Highly recommended to anyone involved with software development at both the management level and in the trenches. Have fun!

I read this book years ago and it still sticks with me. As a reporter in Vietnam, Halberstam was a thorn in the side of the Johnson and Nixon administration. He was watched by Nixon's plumbers and the FBI; Nixon thought he was a subversive. What he is is an exceptionally perceptive historian. In this book he follows the growth of the media industry from newsprint to magazines, radio and television. He told the Edward R. Murrow story before anybody else and his details on Watergate are even more frightening than Woodward and Bernstein's "All the President's Men." Halberstam seems to have that unique capacity to crawl inside the heads of people like Luce who gave us Time magazine. From their perspective, and those of everyday reporters, we see the struggle to balance grasping for the truth and the glory of the headline. We begin to understand how McCarthy could rise to power by using the deadline to sneak in enuedos about people. The author does a masterful job of showing the frustration of reporters and editors and how they finally overcame McCarthy's sinister power. This is an excellent book, not only for journalist but also for those who wish to understand the power of the media in shaping our world.

Please rate this review. Thanks.

This book is big and thick and it is hard to put down. It opens the reader to the media-the reporters-the owners-the news broadcasters and the men and women behind the scenes. He tells in vivid detail how the reporters all over the world as well as covering wars are supported or not by the publications that put them there. And he vividly relates the love-hate relationship of the above people with the various presidents of the USA. I have recommended this book to everyone who will listen to me. I would go on a book tour to get people to read it.!

David Halberstam proves again what a thorough and engaging journalist/historian he was. He presents a detailed account of the rise of the great media families and individuals of the 20th century without being pedantic or tedious. Anyone who wants to understand The L.A. Times, The Washington Post, Time or CBS should start here. The book unfortunately highlights the huge loss that Halberstam's death represents.

Author David Halberstam takes us behind the scenes as he analyzes U.S. media from the 1940-1970's, showing many factors and internal squabbles that influence the medium. The author shows how a mix of professionalism, sloppiness, arrogance, and favorites affects what the media reports, plus how it reports. We see how the media sometimes kowtows to corporate sponsors, and often allows itself to be manipulated. Consider the 2004 campaign, when the media routinely filmed President Bush before cheering crowds, but never his secret service illegally detaining silent dissenters at rallies. Readers also learn about skilled leaders like Edward R. Murrow, capable if imperfect executives like William Paley (CBS) and Katherine Graham (Washington Post), and shysters like Henry Luce (TIME) that avoid truths when they don't fit the agenda.

This book arrived in 1979, before the advent of Internet and most cable news. Still its lessons remain appropriate, even if media often fails to live up to the hopes of the founding fathers and the First Amendment. Halberstam is a talented observer who capably follows George Selby, Theodore H. White, and many others with a critical eye towards the media. I gave the book just four stars because the prose is a bit thick, but this remains an important read.

Read all the other reviews for the media impacting intent which is only a small part of Halverstam's real message in spite of the title of this epoch. Halberstam's media message ranges from imformative to scarry.

But that which will stick with me forever is the way Halberstam delivers the frailty and fate of America to a mere mortal, the President of the United States. Eisenhower fiddles, Kennedy charms, Johnson screams and Nixon frightens. It took Halberstam seven years to research and write this book and after you read it you will wonder how he did it so fast, a monumental effort.

Fortunately the truth is often downright funny. Nixon's twenty eight year old publicity man making a side comment that Nixon looks like he drops down out of his closet every morning in the same rumbled suit and badly in need of a shave.

Halberstam conveys how power was for the taking and that those who had it developed it primarily in accordance with their own agendas, personal or family politics and use it and us in the process.

No matter that this is now just history ending with Watergate. Halberstam's real message is that the circumstances he describes will remain the same in any generation.

The Powers That Be may change the way you think of power and how it affects you.

Anything by D.Diller is a great resource. This book is terrific. I would recommend it to any teacher who likes an organized classroom.

When I received the book, I sat down and read it through and through. This book is exactly what I need for my third grade class. The concept of practice centers for intermediate students makes sense. Debbie Diller's book
gave me the written "how" and provided the blackline masters to put those ideas into practice. I just completed my first week of school and I have already used several of her ideas. This book is easy to read, understand,and most importantly practical.

This was an excellent resource! With our school getting ready to teach combination grades-I will highly recommend it to all teachers. The ideas are practical and with a limited budget, will be attainable in our classes.
Finally- a book to help right away, simple ideas that we can all use!

Recieved item on time, right when we were told it would arrive. Book in very good condition.

This is just what I've needed. Excellent source for getting kids motivated and on tasks that help THEM to learn. Outlines possible problems and solutions ahead of time. Great ideas for taking centers I already want and making them real learning stations in the classroom.

Other teachers on my floor are already looking to "borrow" it.

Issues specific to Open Source are well-covered in this book. I found the section titled "Handling Difficult People" especially useful; his advice in this dodgy area is to act eloquent and keep feedback directed at the problem, not the person. If the person *is* the problem, nip in-public issues in the bud and contact the person directly to resolve the personal issue(s).

Fogel presents lots of down and dirty day-to-day details on how to create excellent software. Not just Open Source, either... the transparency built into the processes he describes are also useful within a company firewall.

Fogel places a huge emphasis on development by random unsalaried people, but I feel that most important and rapid development is due to corporate sponsorship.

Overall: excellent. Read it cover to cover, refer back to it often.

If you are thinking of starting/managing a project in an "open-source" model, this is the book you MUST read.

The book is very well written and goes over lessons learned of others that created their own open-source projects. Believe me... every step so you don't have to guess anything!

How to start, how to document, where to deploy the project, what people to invite, whether or not coding standards are necessary, democracy versus dictatorship, all of these questions are answered inside.

A friend of mine has told me that much of the information in this book can be seen for free in video in Google. It's worth looking for.

I read the book in 5 hours and i think my time was very well invested. I now believe that this model is not only suitable for small projects but to larger projects. The complexity of the system will not the an issue if you apply the rules in the book. I still have to try it though... ;-)

Just yesterday I was talking to a friend about this book and we discovered each other very glad with it. First of all, the author has a lot of experience with the theme in question. Furthermore, Karl Fogel is very compelling with words. He knows how to write down his experience in a way that is pleasant, certainly due to a lot of writes he had made through plenties of open source projects.

With this book you will be in touch with topics like the needed infra-structure to setup open source projects, the dinamics of the open source community, strategies for packaging and releasing software, common issues that arise in open source daily development and how to workaround then, a brief about licenses (with properly links for more information on this topic); just to highlight some aspects.

This book was the first hand someone land me into the open source world. It's helping me in three ways: to extract more from open source softwares that already exist, to start my own open source project, and to look at software development through a new, different, and till now better perspective.

Hope this review helps you!

If you have already read pretty much everything that there is to be read about why you'd want to start, manage, fund or participate in an Open Source project, but want to know everything about how best to do it, then Karl Fogel's Producing Open Source Software is the book for you.

Drawing from his extensive experience with the Subversion project, Fogel provides in this book a comprehensive overview of all aspects of Open Source software development, covering technical, social, political, economical, legal, and managerial aspects.

While the book is more aimed at medium-to-large scale projects, especially those involving some kind of corporate entity, there is much in it that is applicable to most projects, excluding maybe only those little, one-man efforts that rarely become successful. But if you are the originator of one of the latter and, should it suddenly attract a wide following, you'd better be prepared to face the unavoidable problems that popularity brings.This book will come in handy in this case.

Here are, in my opinion, the strong points of the book:

* Providing a concise, yet comprehensive, overview of all aspects of Open Source development. This is really the manual of open development.

* Demonstrating that there is much in open development that is similar to more traditional, corporate-style software development (you cannot always rely on good will and volunteers), but also much that is different, in motivation, rewards and objectives.

* Putting the accent on the human aspect of development: mutual respect between participants is often the deciding factor in determining whether a project will thrive or fail. Since even the best of intentions sometimes are not enough to foster a peaceful, productive and collaborative environment, Producing Open Source Software contains a lot of useful, practical advice that you can follow if you want to keep developers happy and motivated.

It's easy to make the mistake of viewing this book as "too fluffy" or perhaps too soft to be of any use to the practical user or developer of open source software. Nothing could be further from the truth: in a classic open source way, the author has compressed man-centuries of OS community experience into a practical working guide for anyone who wants to do something serious in this area.

If you want to understand programming the Flash Communication Server and it's capabilities this is a good place to start.

Although I'm using Flash Media Server 2, this book is still highly relevant as not much has changed. The core objects and language is the same so I would not hesitate to recommend it for anyone looking to use FMS.

This book is all about the design of applications using Macromedia's Flash Communication Server MX. FCS MX enables the building of media-rich web applications by taking care of the basic tasks required in the networking of the applications. Thus, you can focus on the application itself rather than worrying about low-level communication details.

Since this book is concerned with situations where multiple Flash applications will be executing on the same server simultaneously, there is going to be considerable effort involved in coordinating events, which is addressed by this book. You should already have FCS installed and running on your server and you should also have Flash MX available on the client. The following is description of the book by chapter:

Chapter 1, Introducing the Flash Communication Server - Acts as an introduction to FCS and an overview of the whole book.

Chapter 2, Communication Components - How the FlashCom communication components encapsulate commonly needed features such as chat, video recording and playback, bandwidth control,and user configuration. These components implement many basic building blocks for your application.

Chapter 3, Managing Connections - This chapter covers connections in more depth past the SimpleConnect component, including how to write custom code to handle various changes in the connection status as well as different errors.

Chapter 4, Applications, Instances, and Server-Side ActionScript - This chapter describes how to write Server-Side ActionScript and work with the objects that control application instances and the Flash movies that connect to them.

Chapter 5, Managing Streams - Offers a somewhat oversimplified but complete example that shows the basic steps in publishing one live stream and subscribing to a second.

Chapter 6, Camera and Microphone - This chapter explains how to use both the Microphone and Camera classes to record live streams. These classes are at the heart of most communication applications involving multimedia.

Chapter 7, Media Preparation and Delivery - This chapter covers many details for compressing and streaming audio and video.

Chapter 8, Shared Objects - This chapter starts an entirely new subject - shared objects, which provide a mechanism for the transmission of data between client and server.

Chapter 9, Remote Methods - This chapter also shows how to broadcast method calls to every movie and application instance connected to a shared object or stream, or send them to and from individual movies using RMI.

Chapter 10, Server Management API - Discusses the Server Management API and its applications, including monitoring a FlashCom Server, gathering statistics on application instances, and managing the log streams.

Chapter 11, Flash Remoting - Demonstrates how Flash Remoting can be used to add data connectivity to FlashCom applications. Flash Remoting can access web services, server-side scripts, CGI applications, XML files, or the local filesystem with the help of an application server such as ColdFusion.

Chapter 12, ColdFusion MX and FlashCom - Teaches some specifics involved in using Flash Remoting with ColdFusion MX and FlashCom. There are some practical working examples shown that demonstrate how you can leverage the benefits of Flash Remoting in conjunction with FlashCom.

Chapter 13, Building Communication Components - This is the first step in building complete applications, and is demonstrated through an extensive example.

Chapter 14, Understanding the Macromedia Component Framework - How to modify an existing component and how to create a new one. Also discusses server-side framework code and its core features and data structures.

Chapter 15, Application Design Patterns and Best Practices - Describes some of the best practices available to application developers. This chapter provides some useful design options, patterns, and best practices that will help you build better applications.

Chapter 16, Building Scalable Applications - Deals with building multi-instance and multiserver applications that don't bog down as the number of client connections increases.

Chapter 17, Network Performance, Latency, Concurrency - Traditional network design issues affect FCS also.

Chapter 18, Securing Applications - Specifically this chapter examines the three A's of security - Authentication, Authorization, and Accounting.

Excellent book, stuffed of examples very well explained, easy to read and to understand, essential for who desires initiate or even though to profound itself studies on FlashCom.
Obligator reference in projects involving FlashCom, either for fast consultations and advanced tasks.
Excellent approach of subjects as Design patterns and security, yonder a perfect demonstration about audio, video and much more.

If you're a developer looking into real-time server communication using Adobe Flash, this book is a must-have. It guides you thru various levels of application development in an easy to understand format, and provides well documented pieces of code to assist you in the learning process of putting together your project:

Topics covered include:

- learning about components and how to use them
- establishing and managing client connections
- publishing live and recorded streams
- local communication with clients
- remote communication with outside applications

The book also shows how to build and integrate your own custom components, and how to scale your application using the components that you've created. Other highlights include information on how to use shared objects and server management API, as well as ways to improve both design and performance.

This is a great resource to utilize for implementing a balance literacy program in your classroom.

I love how Regie Routman balances passion with dedication and inspires enthusiasm for even the most mundane routines. She understands that a happy teacher is a good teacher, and is one of the few who encourages educators to have a personal life and share important parts of themselves with students. "Reading Essentials" is not just a practical guide to literacy education: it's a call for teachers to fall in love with reading and inspire the same passion in their students. The children I've taught have learned to become authentic, purposeful, and enthusiastic readers in large part because of Regie Routman's ideas and strategies.

This is an awesome resource for beginning or student teachers and helps with the basics. Very clear, simple and direct.

Great!One of the best books on reading instruction ever! Easy to read, and very well organized,full of practical tips,and lots of student examples. Enjoy!

This is unquestionably the best "how-to" book on teaching reading that I have come across. It is written from the standpoint of a classroom teacher, but there are plenty of essential ideas for homeschoolers, too. One way or another it covers every (as far as I can see) important point, and I agree with most of them. The best chapter is #8, Teaching Comprehension, where the first sidebar says "Teach Comprehension Right from the Start." Cool!

Routman moves most of the academic material to the end of the book, where there are many endnotes with references to research articles and a hefty index.

So what's not to like? The text is more of a collection of ideas and tips rather than an evolving education in teaching literacy (which I would love to see Routman take on). The many entry points to the text material (sidebars, bullet points, "Try it, Apply it" tabs, chapter heads, and subheadings) prevented me from finding a continuous, developing thread of instruction. The book is, as it sets out to be, a tune-up guide for trained teachers who are already dealing with classrooms of students. There is too little step-by-step guidance for homeschoolers who are new to teaching literacy. This is especially apparent in dealing with very early readers, where specific training, commercial materials lists, and informal assessments would be welcome (Routman seems to say that such would be infeasible). I missed recommended reading lists that might specifically tie in with coaching in the text, and striking the best balance of phonics to reading is brought out, but left up to the intuition of the teacher.

The thrust of most of the book is about 5th grade difficulties, but it seems to me that a solid K-3 program would head off most of those problems. I found K-3 to be the weakest component of the book.

Routman acknowledges the many demands on classroom teachers for their time and compassion, but I think she is unrealistic about what is achievable in a classroom-based school setting. Interestingly, though she never mentions homeschooling, her prescriptives are precisely what motivates homeschoolers (this one, at least) and homeschooling is a very sensible response to many of the ills she addresses.

Finally, I had the nagging feeling that the book could have benefited from being substantially shorter. Whatever shortcomings Reading Essentials may have for homeschoolers, it's still the best resource available, and it IS essential.

Any book that tells you how to say "May i give you a back massage" and "I dont have any diseases" in three different languages is definatly worth buying it. Also it has the basics and maybe the more useful phrases like "where is the bathroom" "check please" and the like.

I bought this book because of the reviews I read and it lived up to the hype. It came in handy in both routine and emergency situations - particularly when I had left my passport, money and credit cards on a train in Italy and had to communicate to the stationmaster in Genoa!

This is one of my best purchases in Amazon, it's amazing how good is this book. It's very practical for any traveler around the world, it has detailed content in subjects like: what to tell to italian men if they are bothering you (and as a woman... this can become very handy!) or everything you need to say in a medical emergency or how to enjoy the food in a restaurant (because you can understand now the menu). I really recommend this book if you are looking for a better experience in your trips or if you are learning a foreign language (like me). Greetings from Mexico. Nayeli

This books is great. It has many handy phrases that make traveling in Europe easier. Contrary to what most people believe, not everyone in other countries speak English. If you are the adventurous type and like to explore on your own, knowing some phrases to navigate the area is really useful.

I purchased additional copies of this book for a few friends that were traveling as well.

This book is full of practical advice and essential information that kept me from making some mistakes on our vacation this summer. Though I probably won't return to Europe for a few years, this book will stay in my bookshelves for future reference. I have always enjoyed Rick Steves' travel shows because of his down-to-earth, straight-forward style. The book follows that pattern perfectly. I highly recommend this book to any European travel novice.

this is far the best com book I have read. I am happy to be in possession of one

It's a great book to possess, When it comes to Component programming. After Don Box "Essiential COM", this is by far the best COM+ book I have read. It will give you good understanding about not just writing but design and implementing COM+ Components. Examples are great and right to the point.

I finished this book over a year ago, and never got around to writing a review. Probably won't help too many with most of the new development moving to .NET, but here goes. Overall, it was solid but I thought it could have done two things better. I thought the coverage on MSMQ could have been stronger and the project at the end did not get tied together as well as it should have. I like the approach of a lot of the Wrox books that really get into detail WHY they're doing something in their projects they use to tie their ideas together. I felt as thought the author really almost rushed this section of the book, and, in doing so, missed the opportunity to really drive home his points. Hopefully he reads these and will take a page out of the Wrox books in really getting down to explaining his reasoning and what is going on when he's tying his ideas together with a project in his next book. I thought he did an outstanding job up to that point though.

Scot Hillier's book COM+ VB is destined to be considered a classic among the great big programming books. I wouldn't jerk you around. In fact I can honestly say I love to read Scot's work. Tony Davidson once said "A Smith can be a common man, but does that mean I see a Smith and think: "There before
heaven go I"? There is absolutely no need to ponder. In fact to ponder this is to get confused. I read and laid down the book again. Soon I'll read more.

Joanne Brady

I started my COM+ learning experience with Peishu Li's "Visual Basic and COM+ Programming by Example" and then used this book to get a more advanced look at COM+. This was NOT money wasted. I highly recommend both books to users wanting the learn about COM+ and n-tier. This book is very well written. Developers with a background in MTS may want to skip the "by Example" book but you definitely want to read this book. Scot Hillier understands COM+ (and MTS for that matter) and his style of writing is pleasant to read.

"The Sea and the Poison" is a low-key but very powerful novel set in Japan in World War II. In fewer than 200 pages of lean prose, the book explores the moral dynamics of group of doctors and nurses who perform lethal experiments on POWs at the behest of the Japanese Army. One doctor is corrupted by ambition; another lives only for social approval; one nurse is worn down by a hard life and a bad marriage; almost everyone is numbed by the mass death caused by air raids and diminished by the tendency of medical practitioners to see patients as things rather than people. The upshot: a group of morally lobotomized persons who conform to a perverted work environment at the cost of their humanity and professional duties. It's a disturbing story. The setting is believable, the psychology acute, and the message topical: in fact, it's hard to read "The Sea and the Poison" and not think of CIA agents and private contractors torturing prisoners at Bagram, Guantanamo, and secret sites in Europe. Most of all, the book makes you think. Can there be higher praise for a work of art? Highly recommended.

Teachers: "The Sea and the Poison" would be a perfect book for older high school students looking for "serious" yet accessible world literature.

Without once making specific or explicit reference to Catholicism, Shusaku Endo's membership in the Mystical Body of Christ is as clear as mountain water. With superb craftsmanship and artistry, Endo depicts the nightmarish results of living one's life without seeking and obtaining that membership, without obedience to the commandments of the Lord and the teachings of His Church.

No, it's not a question of being holier than thou -- after all, we're all sinners. Rather, it's a question of knowing the difference between right and wrong, between good and evil, and not pretending that there is no difference, or that the inverse might be true, or that there is no truth at all.

According to Endo, the character Suguro can go no further. But we can. If we don't shake off this diabolical disorientation, we can sink deeper and deeper into the sea of poison; wander further and further through the sinister halls of our own Fukuoka University Medical School.

I liked this book much more than what is generally considered Endo's masterpiece, "Silence", so poorly translated by the Christophobic William Johnston. Michael Gallagher, translator of "The Sea and Poison", also pays some homage to oh-so trendy Christophobia. His is not as egregious as Johnston's, however, and he's a much more careful translator.

SEA AND POISON by Shusaku Endo

Reading Shusaku Endo's Sea and Poison was such a delightful experience I was reluctant to close the book. Granted, it is sad to read about cruel and heartless experiments on living human beings but that is not what the book is about. From the vantage point of Japanese/Christian culture Endo courageously shines his compassionate light into the dark crevices of our souls and makes us confront our own demons nesting there. In doing so he helps us become better persons. Robert Wright in his often quoted The Moral Animal points out that "Human beings are a species splendid in their array of moral equipment, tragic in their propensity to misuse it, and pathetic in their constitutional ignorance of the misuse." Endo does us a service by diminishing our "constitutional ignorance of the misuse" [of our moral equipment]"

Endo traces the inner development of his characters with such a deep understanding of the human condition that I was astounded and moved to tears and joy. He placed two aspiring medical doctors, Toda and Sugura in a University hospital in southern Japan now seemingly under the control of the military establishment. The end of the Japanese/American war was quickly approaching. Daily bombing of the nearby city flattened the city and killed thousands of civilians and gave rise to implacable hatred directed towards two enemy airmen the military captured and brought to the hospital for experiments to determine how much could be surgically removed from a person before the person died. Toda and Sugura are assigned to assist the chief medical doctor who controls the future of the two aspiring doctors. Endo explores how Toda and Sugura deal with the conflicting demands of society, the medical establishment the nation and their conscious. Endo gently opens a window into their souls and allows us to witness the mighty clash between the demands of self preservation and the importuning of their conscious.

Endo writes so evocatively, with such elegance and grace and without a trace of judgment or preaching it was like reading a book length haiku. I recommend that the readers read Bushido the Soul of Japan by Inazo Nitobe, (it's in the public domain and several sources allow a free download). Reading Inazo gave me a deeper and broader understanding of Endo's perspective and I intend to return to reading his books.

This short, dark, psychologically gripping novel is an indictment of militarism and its corrupting effect on the individual and society. The old, the young, the innocent, the pure of heart, caregivers, families, traditions, institutions - all will be degraded if not destroyed by it. It is, for me, Endo's most important and accessible work; it is also that rare thing, a Japanese artist's unsparing summation of the worthlessness and hideousness of The Fifteen Year War.

Edmund Burke would have agreed with Endo's novel "The Sea and Poison". Although a short novel, it is one that delves into some very deep issues about morality and the ethics of passively accepting evil in one's presence.

Contrary to another review, "The Sea and Poison" is not based on the activities of Unit 731 in Manchuria at all. The novel is based on the vivisection of 8 B29 crewmen at Fukuoka Imperial University. These experiments involved removal of lung tissue, puncturing hearts and other experiments, while the airmen were alive. None survived the experiments.

Returning to the novel, Endo focuses on a medical intern, Suguro, and his friend Toda. Both characters represent very different responses to the proposal to vivisect the airmen. Toda feels no guilt or remorse, and has no issue with taking part. It is not even matter of justifying it to hinmself: he just has little response in his conscience. Suguro, on the other hand, is flooded with doubt, ethical problems, and his own conscience. Shown to be a basically kind man, the novel reinforces Burke's suggestion that all evil needs is for good men to do nothing.

A burning look into the morality of the passive, "The Sea and Poison" will challenge and provoke. Despite its brevity, it packs a punch, and will leave you thinking for long after you have turned the last page. As usual, Endo has written a fantastic novel with real weight.