Slashdot Mirror

Duncan Lawie writes: "Kim Stanley Robinson started reading science fiction at the start of the 1970s, as New Wave was breaking over the genre, and began writing it not long after. He soon established a reputation for literate science fiction, confirmed by the 'Orange County Trilogy' written during the 1980s. Perhaps more usefully re-named Three Californias, this thematic trilogy offers alternative visions of America's future. In the 1990s, he came to dominate science fiction through his massive, and massively detailed, Mars trilogy, tracing the colonisation and terraforming of our neighbouring planet. In turn, his output has been dominated by the success of this work and the continued working out of the ideas contained within it. For a new decade, there is a new kind of work by KSR." Duncan goes on to review an example of this new work below. The Years of Rice and Salt author Kim Stanley Robinson pages 670 publisher HarperCollins rating 7.5 reviewer Duncan Lawie ISBN 0553109200 summary What would the world be like without European influence? Very different yet much the same.

The Years of Rice and Salt is an alternate history, opening at the dawn of what should have been the 14th Christian century. Instead, the Black Death has wiped out the population of Europe, leaving the future open to the trans-Asian cultures of the Old World. Robinson has applied his usual detailed research and rich, convincing narrative to the production of this book, giving the world he creates a lived in and liveable depth. Through this, he has successfully avoided many of the pitfalls of alternate history, growing his work from a common root but not dependent on our branch of history for its survival. This book could have been a rather tedious meditation on the absence of da Vinci, Shakespeare, Hitler and a million others. Instead, it is defined by the presence of Arabic and Chinese civilisations, expanding across the planet and finding $other cultures.

The Years of Rice and Salt covers a period of seven centuries and, in the end, the technology that these rather different occupants of the planet discover seems remarkably similar to what our contemporary world has found. In this, KSR seems to have had a failure of imagination -- he does not, or dares not, find the world too different a place. Perhaps the book would have been tedious to read, or impossible to write, if the world had collapsed into an eternal mediaeval culture. Perhaps a pure golden age ushered in by the avoidance of "Western rapacity" would have produced a story without sufficient conflict or complexity. Perhaps, in the final analysis, human nature is human nature regardless of the cultures which seek to shape it. Of course, this leads to the essential problem of alternate history, something which the book discusses directly - "we don't know if history is sensitive, and for want of a nail a civilisation was lost, or if our mightiest acts are as petals on a flood, or something in between, or both at once."

As the tapestry of its internal history is so convincing, and so little reliant on our own, it can be hard to see what the book actually has to do with us. The characters spend a lot of time in discussion throughout the book's length but as the world reaches into the modern age, it reaches also into self-awareness and the protagonists increasingly become historians and philosophers. Towards the end, the book almost dissolves into the deconstruction of it's own content. This approach seems to be an attempt by the author to give himself an opportunity to comment more directly upon our world. In the final section, the story regains the impetus as a new global culture starts to pull together. This section is written in the future from our perspective and the narrative is more comfortable as Robinson abandons alternate history for the stronger stuff of true science fiction.

In terms of technique, Robinson manages both interesting and admirable approaches, experimenting and further developing his craft as a writer. He maintains a set of central characters across the whole period in question by making use of the idea of reincarnation. This fits nicely with the idea that this is an "Eastern" book rather than a "Western" one whilst avoiding the complications of a generational saga or of writing about totally new characters in each section. It provides the reader with a thread to follow through the ten tales, tying them together in small ways as well as large and allows commentary on the progress of the book and of society. Additionally, each of the ten 'books' which make up this large novel is written in a different style, reflecting the characteristics of the period in which it is set. Even the map which introduces each section is drawn differently.

This new book is vintage KSR - so rich in detail that the experience of his milieu becomes personal. Clearly, a master builder of worlds is at work, thoroughly working his research into the foundations. It also has the fingerprints of ethical and ecological concern, encouraging us to do our best, be of good will and to maintain an upward slope for ourselves, our kind and our world. Robinson's fans will enjoy The Years of Rice and Salt. Other readers may fare better by skipping to the final chapter.

You can purchase The Years of Rice and Salt from bn.com. Want to see your own review here? Just read the book review guidelines, then use Slashdot's handy submission form.

Dark Paladin writes: "Why wait a week when you can go read the novelization of Star Wars Episode II: Attack of the Clones, and know what happens before you view it on the big screen? Then again, if the book is any indication, you might as well wait for the Big Screen version instead." Read on for the rest of his review to see why. Star Wars: Episode II, Attack of the Clones author R. A. Salvatore pages 336 publisher Ballantine Publishing Group rating 6 reviewer Dark Paladin ISBN 0345428811 summary It's written from the screen-play -- how much more do you need to know?

Hello, Mr. Salvatore! For the folks who want to get the details on the story without downloading the bootleg version, there's always the novelization based on the screen play, adapted by R. A. Salvatore (the same man behind the many D&D books in the fantasy section of the bookstore).

The last time this happened, Terry Brooks was the captain, guiding us through his interpretation of Episode I: The Phantom Menace. It was a good book, filling in the gaps that the movie missed, while telling the story in style. To be honest, I wish we had Mr. Brooks back. It's not that I don't like Mr. Salvatore, but -- well, maybe I don't after reading this book.

It's clear that Salvatore had access to the screen play for the movie, with every move, look, and nuance that was put inside. He also has access to the choreographed scenes, which becomes clear since he feels the need to tell us every single detail of the fights. Thanks to him, I now know that in a fight scene between Obi-Wan and Jango Fett, Obi-Wan "...ducked the blow and did a tight, stationary somersault right under the swinging arm, double-kicking as he came over...", and every other minor detail, blow, kick and jump. A fight scene that probably takes 2 minutes in the movie now takes up 15 pages of text.

It's overkill, and Salvatore does this over and over again. I would say he's wordy, but the definition is too short by at least 30 characters. In another scene, where Anakin goes all Dark Side on us, Salvatore writes it like this (well, not exactly - but it feels that way):

And as the rage raged through Anakin's rage, he raged through his raging rage to rage the rage rage.

I'm not clear here - is Anakin angry? It's a formula that is used over and over again with as much verbage as Salvatore can invent - how much Shmi Skywalker misses her son, or how Padme has chosen professional life over personal life.

You almost want to scream out "We get the point - move on to the story!"

Jedi and Bounty Hunters and Clones, Oh My!

The story itself is predictable sci-fi fiction. We can spot a plot device half a mile away, and in many ways, it emulates Episode I in its setup.

The story involves the attempted assassination of Padme Amidala, who is no longer Queen of Naboo (seems they can only serve 2 terms), but is now Senator of Naboo, fighting to prevent the creation of an army for the Republic to defend it from the Separatists. So the Jedi Council, at the advice of Emperor^H^H^H^H^H^H^H Supreme Chancellor Palpatine, enlists the help of Obi-Wan Kenobi and his Padawan Apprentice, Anakin Skywalker, to protect the young Senator.

While Obi-Wan takes off to chase after the assassins, Anakin is holed up with Padme all alone on her home planet on Naboo. Of course, nobody else seems to notice that Anakin has been Jonesing for Padme since he was 10. Even though Obi-Wan seems to think that Anakin might get himself into trouble, but is overruled by the Jedi Council, who don't seem to realize that a barely 20-year-old man with raging hormones around Natalie Portman might feel a little tempted.

This soon leads to romantic moments between the younglings, boiled down to this:

Anakin: Padme, I love you, and I'm not even vaguely trying to uphold my vows as a would-be Jedi to never marry. Kind of like a Catholic Priest, without the altar boy scandal. Padme: Anakin, we can't be together. You're a Jedi, and are forbidden to marry. (Even though I think those brown robes are so hot on you.) Anakin: What was that? Padme: Oh, nothing. Let's to romp in the meadow and hold hands even though I say we're not going to fall in love. Anakin: Sure. Can I look longingly at you at times? Padme: If you must. (While I undress you with my eyes.) Anakin: What? Padme: Nothing!

Gaps in the Universe

So while Padme and Anakin are making goo-goo eyes at each other, Obi-Wan is discovering the creation of a clone army, an army based on the genes of Jango Fett, the best bounty hunter of the galaxy, who's cloned son, Boba Fett, is being trained by his "father" to be even better.

But then the questions come up. Who would want the creation of a clone army to fight the Separatists, when the Senate is still arguing about creating an army in the first place? What is Count Dooku, the former Jedi who is labeled as "the best kick ass lightsaber duelist in the history of the galaxy", doing at the head of the Separatists - and what is his plan? And how long until Anakin and Padme finally give in to their lusts and make the beast of two backs?

The story, in and of itself, isn't that interesting. But the story does a good job at tying up the lines between Star Wars Episode 4: A New Hope and the prequels. For the first time, we meet Owen and Beru, and understand how they fit into the Skywalker family. We see how the future Emperor manipulates the public to put himself as the head of the Republic. That alone is enjoyable as you go "Ah...now that makes sense."

But for the cost of the $26.00 book, you might as well just wait a week and pay $11.00 at the movie theaters for the same information - in much less time.

You can purchase Attack of the Clones from bn.com. Want to see your own review here? Just read the book review guidelines, then use Slashdot's handy submission form.

RickHigh writes: "I've been waiting for a book like this. If you are doing software development of any kind, you should read this book. Especially if you are doing Extreme Programming and you errantly believe modeling has no place in XP. Or, your doing the Unified Process and you feel that your models and documents are more important than a working system, or you feel you are bogged down in documentation and required artifacts (more likely). Agile Modeling (AM) is a modeling methodology that enhances your modeling endeavors, whatever your process methodology inclination. Agile modeling will help you effectively incorporate modeling into your organization." Read the rest of Rick's review below. Agile Modeling: Effective Practices for Extreme Programming and the Unified Process author Scott Ambler pages 400 publisher Wiley, John & Sons, Incorporated rating 7.5 reviewer RickHigh ISBN 0471202827 summary A worthwhile melding of XP techniques with modeling of general interest to programmers of all stripes.

The title is only partially accurate as the book covers a lot more than modeling. I know from experience that picking titles is tricky (you can't please everyone). You don't need to be a UML expert to get value of this book. Any software developer should be able to appreciate it. Modelers, software developers and Yes, managers will find this material useful. In fact you may want to buy a copy and put it on your manager's desk. This book is original and well thought out. It is also well written and very readable. I wish there were more examples of applying the different artifacts in different phases of the XP life-cycle, but there has to be room for the next edition. The depth is appropriate.

Many UP developers (and those working with other prescriptive processes) get bogged down in the tonnage of documents and artifacts that are required. They wonder if they are ever going to have time to actually write the code.

XP offers a methodology for building high quality software fast. However, many XP developers, and I've spoken to them about this very subject on many occasions, find that XP does include time to do models. This books shows how to integrate XP and modeling.

This book sets the record straight about design and Extreme Programming. Actually, Kent Beck set the record straight with the first book on XP when he said 'In the time it would take you to code one design, you can compare and contrast three designs with pictures.' Kent Beck's views were corrupted over the years for various reasons that Agile Modeling explains, as it clarifies once and for all the relationship between XP and modeling.

The book emphasizes that you should model to understand the problems and only apply the right artifacts, i.e., that not all modeling must lead to writing code.

Despite the title, he AM book transcends just being a book on modeling; the book covers many aspects of developing software. Agile Modeling endeavors to be real. By real I mean it talks about real issues and how things are handled in the real world, not the perfect world covered by most books. For example, the chapter on documentation is an excellent coverage of the subject, but not idealized beyond all usefulness.

Like the original XP book, the AM book lists values, core principles and practices. It also adds supplementary principles like 'Content Is More Important Than Representation.' A key lesson from the book is that models are important if they help you understand and solve problems. And, models do not have to be perfect -- in fact they can be thrown away when you are done with them. After all is said and done, 'Software is your Primary Goal.'

The author, Scott Ambler is the author of numerous books (and by numerous I mean a lot) for the Unified Process, and UML. He also contributed to the Mastering EJB Book, and the Java Elements of Style book. All his work in UP seems strange since AM seems to have closer ties to XP than UP, but that is probably my own warped misconceptions of the world. Bottom line, Scott has mastered the craft of writing and I really enjoyed his writing style. The first few chapters seemed a little slow, probably because their content has been covered before in other books. The chapters on AM and XP, though, were informative and useful (as was the chapter on agile documentation mentioned earlier).

If you are doing software development of any kind, you should read this book. It is an informative and enjoyable read.

What's covered? Here are the chapter headings:

• Table of Contents:
• PART I: INTRODUCTION TO AGILE MODELING.
  • Introduction.
  • Agile Modeling Values.
  • Core Principles.
  • Supplementary Principles.
  • Core Practices.
  • Supplementary Practices.
  • Order from Chaos: How the AM Practices Fit Together.
• PART II: AGILE MODELING IN PRACTICE.
  • Communication.
  • Nurturing an Agile Culture.
  • Using the Simplest Tools Possible?
  • Agile Work Areas.
  • Agile Modeling Teams.
  • Agile Modeling Sessions.
  • Agile Documentation.
  • The UML and Beyond.
• PART III: AGILE MODELING AND eXTREME PROGRAMMING (XP)
  • Setting the Record Straight.
  • Agile Modeling and eXtreme Programming.
  • Agile Modeling Throughout the XP Lifecycle.
  • Modeling During the XP Exploration Phase.
  • Modeling During an XP Iteration: Searching for Items.
  • Modeling During an XP Iteration: Totaling an Order.
• PART IV: AGILE MODELING AND THE UNIFIED PROCESS.
  • Agile Modeling and the Unified Process.
  • Agile Modeling Throughout the Unified Process Lifecycle.
  • Agile Business Modeling.
  • Agile Requirements.
  • Agile Analysis and Design.
  • Agile Infrastructure Management.
  • Adopting AM on an UP Project.
• PART V: LOOKING AHEAD.
  • Adopting Agile Modeling or Overcoming Adversity.
  • Conclusion: Choose to Succeed.
  • Glossary of Definitions and Abbreviations.
  • References and Suggested Reading.
• Appendix A: Modeling Techniques.

Sites of interest

• The Agile Modeling site
• The XP programming site
• The Agile Alliance site
• Scott Amblers Website
• Applying XP to J2EE

You can purchase Agile Modeling from bn.com. Want to see your own review here? Just read the book review guidelines, then use Slashdot's handy submission form.

The redoubtable Stella Daily writes: "For many, the word 'chemistry' brings up deliberately suppressed memories of acid-base titrations and annoying stoichiometry problems. 'Nature's Building Blocks' by John Emsley has the singular ability to take chemistry out of the tedium of the high school lab and bring to the reader the sort of childlike wonder that pioneering chemists like Mendeleev and Lavoisier must have had when making their discoveries." She's got a bit more to say about this book, below. Nature's Building Blocks author John Emsley pages 539 publisher Oxford University Press rating 8 reviewer Stella Daily ISBN 0-19-850341-5 summary Bedtime stories for chemists

From actinium to zirconium, Emsley covers each of the elements of the periodic table in alphabetical order and includes a short section on the periodic table arrangement itself. Though the result looks rather formidable at 500-plus pages, Nature's Building Blocks is less like a college chemistry text (or the staple of every chemist's bookshelf, the CRC Handbook), than like a collection of bedtime stories. For one thing, the book need not be read front to back; just pick an element, any element, and start wherever you like; it's not even necessary to read any chapter beginning to end. Each is broken down into cleverly named subtopics such as "Human Element," "Economic Element," and by far the most fun, "Element of Surprise." Besides information on the history, uses, origin, and chemistry of each element -- all of which are a pleasure to read -- Emsley uses the "Element of Surprise" section to present the reader with facts that range from the commonsensical "I never thought of that!" variety to the utterly unexpected and fascinating. The gee-whiz quality with which he writes is truly refreshing.

The book demands about a high-school knowledge of chemistry, though many sections can be read without even that much, and even lifelong chemists will find it full of surprises. The stories and facts gathered therein include the clever way Niels Bohr is said to have hidden his gold Nobel Prize medal from the Nazis when he fled Germany, how nonstick Teflon sticks to aluminum frying pans, how magnetic mines work, how the British government accidentally killed 31 of its own citizens with silver iodide, and, in the "Who Knew?" category, the fact that a piece of indium metal lets out a high-pitched shriek when bent. As you read, don't be surprised to find yourself saying the words "Too cool" aloud fairly frequently.

So why does this book get an eight instead of a nine or ten? Unfortunately, Emsley is a lot better at talking about the elements' history, usage, etc. than he is about their chemistry. He often seems to be unsure of whether the reader is a knowledgeable chemist or reading about the subject for the first time; in the chapter on silicon, for example, he explains why silicon dioxide is a neutral compound -- a no-brainer for anyone who's had high school chemistry -- but two paragraphs later says that silicon is part of n- and p-type semiconductors without explaining what the heck an n- or p-type semiconductor is. Elsewhere, the text contains serious errors that any half-decent copy editor should have caught. The periodic table section of the book contains the phrase, "Most hydrogen atoms consist of a single proton." In context, he means hydrogen as opposed to deuterium or tritium, whose nuclei contain neutrons in addition to protons, but a hydrogen atom consists of a single proton and an electron; a single proton is a hydrogen ion. This sort of careless error is common enough to be seriously annoying (and possibly deceiving to the chemistry beginner).

Though it must be read with the proverbial grain of sodium chloride, Nature's Building Blocks is a worthy read indeed -- the kind of book that can get people excited about a subject that usually inspires groans and protests of "I hate chemistry!" And for that, this former chemist is grateful indeed.

You can purchase Nature's Building Blocks from bn.com. Want to see your own review here? Just read the book review guidelines, then use Slashdot's handy submission form.

From the opening pages of Scott Kelby's Macintosh... The Naked Truth, I was literally laughing out loud. I am a generally jovial character, so this is not the finest endorsement available, but it is typical of the experience the rest of the book offered me. Macintosh... The Naked Truth author Scott Kelby pages 219 publisher New Riders rating 7 out of 10 Macsbugs reviewer pudge ISBN 0-7357-1284-0 summary Funny, irreverent, but kinda bugged me in spots

The Naked Truth is a book about what it means to be a Macintosh user, in a world dominated by Windows. This should have tipped me off as to some troubles ahead, as I live as a Mac user in a predominantly Linux-dominated world. And I proudly use Linux (and, to a lesser extent, other forms of Unix, not even including Mac OS X) daily. As I write this, I have four terminal windows running in NiftyTelnet, connecting me to Linux boxes at work and at home. I am inserting a 700MB database dump into MySQL, scp'ing some MP3s, restarting some daemons, copying some source code for later porting, and monitoring disk space. I am a Macintosh devotee, and have been for more than 15 years, but I am a geek. A big, preemptively multitasking, geek.

But Kelly takes the perspective that Macintosh is not a computer for geeks, but for creative people who can't be bothered with geek-like things. So when he belittles those "PC users" who like to build their own computers, and I see the Linux box under my desk that I've recently been fiddling with, I just take it with a grain of salt. After all, geeks are allowed to like ease of use and a consistent and usable GUI, too.

This mischaracterization of some Mac users is also evident in his "definitive platform test." The questions, asking for things like a description of your own driving skills, are intended to tell you which platform you should use. On one end of the scale is the Macintosh user ("Average, I'm not a bad driver"), followed by borderline between Mac and PC user ("I'm an excellent driver, very cautious and alert") to obvious PC user ("I obey all posted traffic signs and don't exceed the speed limit"), to "militant" PC/DOS user ("I wish all those idiots would just get off the road!"). But clearly, any sane person would choose the latter response. I don't understand what the problem is. I selected the "Mac" and "DOS" answers evenly, which didn't do well for my overall score. I happily continue to use Mac OS nevertheless.

That said, Kelby is dead-on about many things, like how computer store personnel are mostly clueless (not that this is specific to Macintosh products, but it is more pronounced in that particular arena than in most); how most anti-Macintosh arguments by PC users either don't make sense any more or never made sense to begin with; how Apple has been the primary innovator of PC hardware and OS software; how Apple seems to succeed sometimes in spite of its own management. He tends to belabor his point on occasion (OK, we get it, CompUSA's Apple store-in-a-store is all the way in the back, we don't need you to spend two pages describing just how far back it is), but if taken in the good humor intended, it's a satisfying journey nevertheless.

His most interesting points, perhaps, have to do not with what it is like to be a Macintosh user in a foreign land -- I think everyone on Slashdot can understand these things, regardless of whatever non-Microsoft platform of choice they use -- but what it is like to be a Macintosh user in relation to Apple itself. He has some keen insights about where the passion comes from; why people love Apple; what's going on inside their heads.

But then again, reading his responses to letters written to Mac Today and Mac Design Magazine by PC users are just downright entertaining -- keenly insightful or not -- if you are the sort of individual who likes to see stupid people get smacked around. And who isn't?

Now, being a geek -- and a pedantic one at that -- I did take issue with him on some relatively minor issues, like claiming that Apple changed the name of Mac OS X to "OS 10.1" when it came time to do the first maintenance release; the fact is, the official name from day one was "Mac OS X 10.0," and that nothing has changed at all in that naming scheme. The current release is "Mac OS X 10.1.4." It's the same thing, with an incremented version number. He's absolutely right that this is a point of confusion, and in some ways poor marketing. For the next major release (Mac OS X 11.0? Mac OS 11? Mac OS XI?) there will surely be some more confusion, too. But nothing at all has changed in the naming scheme since the initial release. For now. I just want to make sure everyone is clear on this point. It is "Mac OS X, version 10.1.4," and "Mac OS, version 9.2.2." "Mac OS" and "Mac OS X" are OS names. "10.1.4" and "9.2.2" are version numbers. Got it?

Similarly, he bashes the Newton. Sure, the first release of Newton kinda stunk, but it was the first version. The last versions of the Newton MessagePad, aside from the size, were still by far the best PDAs around for the next several years. Newton still, to this day, has the best handwriting recognition in any consumer PDA, as well as the best (non-color) interface, and it was years ahead of its time in functionality. It was just too big. That was its only problem. Well, and too expensive. But maybe less so if it weren't so big.

And he also called Compaq's PDA an "iPac." And occasionally used poor punctuation. And I think I saw a run-on sentence in there.

But now I am getting worked up. I'll settle down. Deep breath, in, out, in, out. That's the thing about being a Mac user, Kelby points out: passion. Passion for Apple and its products, even the ones that stink, because Apple is more than just a company, it is an organization that changes our lives in important ways, by making products that make a difference to us.

OK, so maybe I am in the target audience after all.

Chapter List

1. Life after switching to Macintosh
   Using a Mac is easy; being a Mac user sometimes isn't.
2. "I can't believe you actually use a Macintosh!" and other stupid things PC users say
   Congress should rethink giving PC users freedom of speech.
3. Things Apple doesn't tell you about owning a Macintosh
   Since Apple's not going to tell you, dontchathink somebody should?
4. The definitive platform test
   Find out if you're really a Mac person, or just a PC person in cool clothing.
5. How to resist the overwhelming temptation to strangle Apple's management
   Is "Apple Management" an oxymoron? And is "oxymoron" actually a synonym for a pimple cream for really dumb people?
6. CompUSA: Your own private hell
   Tips for surviving the visualization of Apple's place in the world.
7. Why PC users need Apple
   Heere's why they should be kissing Apple's butt (instead of Microsoft's)
8. "Don't pick fights with people who buy ink by the barrel"
   PC users write me nasty letters, and I give them the public flogging they so richly deserve
9. Pot shots at Microsoft, the media, and anything else that gets in our way
   Nobody gets out of here alive!
10. The 20 most important things I've learned about being a Mac user
    There were actually 22 things, but that made for a really clunky chapter title.
11. The secret of Macintosh
    Here's a hint: it's not Apple's advertising.

You can purchase Macintosh ... The Naked Truth from bn.com. Want to see your own review here? Just read the book review guidelines, then use Slashdot's handy submission form.

Reader Cole Tucker writes with this review: "The Ruby Developer's Guide was written with the intent to provide an overview of Ruby tools used for developing real-world applications. The book touches on a variety of areas, from GUI development to neural networks, and discusses existing Ruby packages that developers can take advantage of. In the end, the book comes out as a Ruby version of the Perl Cookbook." To see what he means by that, read on below for the rest of Cole's assessment of this book. Ruby Developer's Guide author Robert Feldt, Lyle Johnson, and Michael Neuman pages 720 publisher Syngress rating 7 reviewer Cole Tucker ISBN 1-928994-64-4 summary Good introduction to Ruby -- an overview as well as a practical cookbook.

The writers of the book are very enthusiastic about both Ruby and the Ruby Application Archive (RAA), Ruby's response to CPAN. Overall, the text does a very good job demonstrating the base knowledge necessary for each of the libraries introduced and so can be quite useful to any developer with an understanding of core Ruby programming.

Directed towards programmers with a working knowledge of Ruby, the text is a quick read even with working through the examples. It effortlessly introduces the basic concepts of each package worked through and then gives locations where more in-depth information can be gathered. If you wish to work through any of the topics covered without digging through documentation just to obtain a basic grasp of the package, then this book is for you.

The book itself is a Syngress publication, and comes with a "1 year upgrade buyer protection plan" which seems to mean they have an errata page for the book and an "Ask the Author" section on the books website, along with a couple of other features mostly involving email. Looking at the errata page, it seems to be useful and up to date. The "Ask the Author" section also seemed to be fairly well-used by prior customers. Syngress seems to be serious about keeping customers up to date about the state of the book and providing services beyond that.

As for the book's problems, none of which are horrible, but do get old after a while: First, the book is big, and not completely because of content. The examples in the book span pages, and the text used in the source is a larger font that in the rest of the text. The examples also are full applications within themselves, instead of being presented in chunks and then having the full source available online. Another annoyance is each time the book mentions installing a package or library it goes through the whole "$./configure.rb; make; make install" process. The book also appears to have some organization issues, with notes for the text in the table of contents, which just served to irritate me. The final negative thing I noticed was that, though the text assumes programming knowledge of Ruby, the first chapter is dedicated to walking the reader through downloading and installing Ruby. The chapter is a big one too. So the book has a couple of hitches, mostly related to layout or mixed expectations towards the ability of the reader.

If you can deal with these small issues and are interested in the material covered, I can definitely recommend the Ruby Developer's Guide. The content is definitely there and they authors know their stuff.

Chapter List:

1. Booting Ruby Discusses downloading and installing Ruby, IDE and editor support for Ruby and syntax stylings.

2. GUI Toolkits for Ruby Covers use of Tk, GTK+, FOX and SWin GUI toolkits with a brush through on others available.

3. Accessing Databases with Ruby Introduces the Ruby/DBI, Ruby/ODBC, Ruby/LDAp and Ruby DBM-file drivers.

4. XML and Ruby Talks about the use of XML, including a basic introduction to it and then goes into parsing and creating XML using libraries from the RAA.

5. Web Services and Distributed Ruby Goes into the libraries used for RPC's, SOAP and running distributed services with Ruby.

6. WWW and Networking with Ruby Implements a server using high-level and low-level Ruby networking classes, then goes into using Ruby for the web, finishing up with a discussion of mod_ruby and eruby.

7. Miscellaneous Libraries and Tools This chapter finishes the discussion centered around the RAA, going into graphics programming, data structures, genetic algorithms and other topics that didn't fit into a chapter of their own.

8. Profiling and Performance Tuning Introduces the aspect of analyzing algorithms in Ruby, profiling your programs and discusses the advantages of similar Ruby constructs depending on what your focus is, with the intent of getting lean, mean programs.

9. Parse Generators Discusses using Ruby instead of Bison or Yacc for creating a parser, and then goes into the advantages of various Ruby libraries to each other.

10. Extending and Embedding Ruby Covers writing extensions to Ruby in C and C++ and later embedding Ruby into programs.

You can purchase the Ruby Developer's Guide from bn.com. Want to see your own review here? Just read the book review guidelines, then use Slashdot's handy submission form.

David Kennedy writes: "Java Tools For Exteme Programming: Mastering Open Source Tools including Ant, JUnit and Cactus by Hightower & Lesiecki is a welcome addition to my bookshelf at work. It tackles a gap in the Java book market in dealing with the thorny issues of testing, integration and deployment." The rest of his review is below. Java Tools For Exteme Programming: Mastering Open Source Tools including Ant, JUnit and Cactus author Richard Hightower & Nicholas Lesiecki pages 516 publisher Wiley Computer Publishing rating 8 reviewer David Kennedy ISBN 047120708X summary Practical introduction to Java tools for Extreme Programming, with an emphasis on immediate results rather than deep theory.

In recent years there has been a increased emphasis on Agile Software Development. The most prominent of these methodologies is probably Extreme Programming.

What sets Extreme Programming apart from most other Agile Technologies, in my opinion at least, is that it has provided practical, easy-to-use tools to support its way of working. Most of these tools (Ant, JUnit etc) are Open Source and freely available. However popular these tools have been with the Open Source and Extreme Programming communities, it has arguably been difficult to introduce them to traditional IT development environments. This has been primarily due to the problems of justifying spending time on 'playing' with something and the difficulties of retro-fitting new tools to an existing development environment (think projects of 150+ people which have been releasing for 5-10 years for some idea of the potential problems).

It's worth noting that when embarking on a new, large-scale project it's very difficult to find a book discussing the issues of controlled builds, integration and deployment in practical terms. The most valuable aspect of Java Tools for eXteme Programming is that it's alone in its market niche.

The book is mainly useful as (a) an introduction to the various building and continuous testing tools out there and (b) a tutorial to getting them setup and working on your computer. As the authors note, there's a critical period where the user must get some result after playing with the tool for a short period of time or just give it up as 'too difficult.'

From a technical standpoint the book is very readable, but it doesn't tackle any one subject in great depth. It certainly provides enough information to get you up and running, and also, perhaps more valuably, illustrates how to integrate the tools together. It's an excellent primer for those who want to use the tools but are unsure of how exactly to start.

What's covered? Here are the chapter headings:

1. Introduction and Key Concepts
   1. Introduction to Extreme Programming
   2. J2EE Deployment Concepts
   3. Example applications
2. Mastering the Tools
   1. Continuous integration with Ant
   2. Building Java Applications with Ant
   3. Building J2EE applications with Ant
   4. Unit testing with JUnit
   5. Testing Container Services with Cactus
   6. Functional Testing with HttpUnit
   7. Measuring Application Performance with JMeter
   8. Load Testing with JUnitPerf
3. API and Tag Reference
   1. Ant Tag Reference
   2. Ant API Reference
   3. JUnit API Reference
   4. Cactus API Reference
   5. HttpUnit API Reference

If you use some of these tools already will you learn anything? Probably -- I personally have been using JUnit to test EJBs for almost nine months now but didn't know about JUnitPerf or Cactus.

Should you buy it? If you're new to the tools, then Yes. If you work in a professional but traditional IT shop, I'd buy one for the group (I have). It'd be particularly useful when dealing with management and proposing changes to working processes, or when trying to bring co-workers up to speed and sell them the benefits of agile ways of working.

You can visit the book's website at Wiley. You can purchase the Jave Tools For Extreme Programming from bn.com. Want to see your own review here? Just read the book review guidelines, then use Slashdot's handy submission form.

Long-time reviewer clampe writes with this piece on Human-Computer Interaction in the New Millenium. This is not a book you're likely to find at the corner bookshop, but if you're serious about keeping track of goings-on in the field of HCI, Cliff argues this one is worth seeking out. Human-Computer Interaction in the New Millenium author John M. Carroll (Editor) pages 703 publisher Addison-Wesley rating 9 reviewer Cliff Lampe ISBN 0-201-70447-1 summary Academic HCI lovefest.

Reviewer's Note:

Most of the people in the book I'm reviewing could crush me beneath their heels, given I'm a lowly doctoral student in the HCI field. However, it's not a simple question of whether the collection is good or bad, but whether it will be good for the reader in their context. Besides, I can give you good inside information on lots of the authors. Like George Furnas, as cool a cat as you'll meet, gets nervous when he does magic tricks and Paul Resnick picks a mean fiddle. Yep, I got tons of dirt.

The Scenario

Anyone who has taken an HCI class has probably come across a gigantic blue paperback book called Human-Computer Interaction: Toward the Year 2000, which has acted as a de facto text in HCI classes in the past. In 1998, leaders in the HCI field realized that this book would soon be obsolete, and started organizing the players who would contribute to this worthy successor. This book is a collection of 29 articles from the lead researchers in the HCI academic research community, and it attempts to outline the research programs that will dominate the HCI field, if not for the next millennium as advertised, then at least for the next 10 years. The book is divided into seven sections:

1. Models, Theories, and Frameworks
2. Usability Engineering Methods and Concepts
3. User Interface Software and Tools
4. Groupware and Cooperative Activity
5. Media and Information
6. Integrating Computation and Real Environments
7. HCI and Society

Each section has 3-5 articles on the section's topic. Examples of the research included:

• Terry Winograd proposes a conceptual framework for the design of interactive spaces, or more basically computing environments built into the architecture of a space and seamlessly integrated with personal context.
• Hollan, Hutchins and Kirsh follow up some of Hutchins work on distributed cognition as an HCI research area, including a call for more ethnographic studies in the area and a better understanding of how people and tools interact.
• Olson and Olson outline the problems of distant work collaboration, and outline situations in which distant work makes more sense than not.
• Terveen and Hill give a great review of work in collaborative filtering, and then outline several approaches to making recommender systems better able to return positive hits.
• Doug Schuler in one article and Paul Resnick in another argue how HCI issues go beyond desktop computing or small groups and can be applied to larger groups, including communities both online and off.

Other topics include situated computing, participatory design, new user interfaces like tangible user interfaces or gesture recognition, cognitive modelling and so on. Some common themes that emerge are the expectation that user interface needs to go beyond the desktop environment, the application of HCI principle to things other than the individual or small group, the importance of groupware and the development of a unifying theory for the field.

Really, one could write a pretty long review on any of the 29 chapters, since each one does have serious weight, as well as an innovative edge as these investigators attempt to outline directions for the next several years. Some of the articles included here have already struck a chord in this research community and have become widely cited in their draft forms, or from appearances in special journals. Each section of the book typically appeared as as journal article in Human-Computer Interactions, or were specifically solicited by John Carroll.

The Good and the Bad

These are some heavy hitters. The authors list reads like my general prelims, and it takes someone like Carroll to pull together a group like this. Each of the 29 articles stands strong on its own, though one may quibble with claims here and there, yet still manage to paint a remarkably cohesive picture of the area as a whole. This book contains serious research in a single bound volume that should grace the desk of any person interested in HCI issues. It is simply unarguable that this is going to be the HCI book for the foreseeable future.

The book bears some of the problems of the field, which is that it comes from a specific set of disciplines like cognitive psychology and computer science, so may preclude applicable theories from other disciplines. That is the nature of academic boundary making, and is not the specific fault of the book. Just so you are aware of it.

And speaking of academics, some readers may be turned off by the academic edge of this book. HCI in general has always had a foot in both the university and the corporate sector, as evinced by the list of speakers at this year's ACM-SIGCHI conference, but this book tends towards the academic side. Although specific applications get mentioned here, large parts of the book may be a turn off to people like my brother-in-law who is a sysadmin and definitely not interested in new macrotheory for HCI research. Or shaving.

This book takes commitment. It is not for lily-livered pedants who want something to fill the space until the next Harry Potter book comes out. That's neither good nor bad, just fair warning. Don't expect this to be as eminently accessible as a Don Norman book. Still, like in most things the work is very worthwhile.

So What's In It For Me?

It seems that in every field there is That One Book that people will point you to as the ultimate source to quickly get a sense of what it is all about. This book plays that role for the HCI field. If you are at all interested in the state of HCI research, mostly in the U.S. of course, then this is the book you should get. Even if you are already some tricked out, super-HCI guru, there is likely to be some research in here from outside your specific area that you will get value from.

This is not a book for someone who has to do a usability test for the boss next week and needs to know how to conduct one. Nor will this book tell you how to make your website look really cool. What it will do is give you incredible insight into the history and future of an exceedingly interesting field of endeavor.

Cliff is a doctoral student at the University of Michigan School of Information, studying in their Human-Computer Interaction program. He plans to be a contributing author in the next version of this book. You can purchase the Human-Computer Interaction in the New Millenium from bn.com. Want to see your own review here? Just read the book review guidelines, then use Slashdot's handy submission form.

Reader the_rev_matt writes with this review of Hungry Minds' Zope Bible. He finds both merit and shortcomings in this book, and suggests that "Bible" may be too grand a word for this decent-but-spotty work. Read on for his reasoning. The Zope Bible author Michael R. Bernstein, Scott Robertson & the CodeIT Development Team pages 613 publisher Hungry Minds rating 8 reviewer the_rev_matt ISBN 0764548573 summary An in depth look at extending Zope with Python.

Part One is the basics, which anyone familiar with Zope can skip over if they so choose. For a newcomers it may seem a little overwhelming, but for readers unfamiliar with web development it may seem a light on details at times. It opens with the obligatory "History of Zope" which is mercifully brief and includes a single paragraph on the history of the Internet that publishers still insist on including. It does mention some great high-profile organizations that are using Zope (Red Hat, NASA, Bell Atlantic Mobile, CBS, and the U.S. Navy). The Features section could be used to great effect in selling the use of Zope to management, as it is brief and to the point and focuses on things that businesses actually care about. Next up is Architecture, and the Bible does a fine job of describing the Zope architecture and highlights the primary advantages in nice bullet points (Cost of ownership, RAD, reliability, scalability).

Installation is covered with proper dispatch and goes into great detail about the ZServer (the preferred web server) as well as how to install new products and troubleshoot bad installations. The basics of the Zope Management Interface and the Control Panel are covered in chapter three.

Chapter Four is where the meat starts. This is a fairly in-depth presentation of DTML, Zope's built-in markup language. It includes a nice reference to Python modules natively available in Zope, and examples of all standard tags in action. Closing out Part One is a chapter about Object Oriented Programming in Python. It is less detailed than the documentation and tutorial that come stock with Python, and anyone who plans on getting that down and dirty will want to get a real Python book. Those 50 pages would have been better used in providing a case study or two of developing an end-to-end web app in Zope. Even given the focus on writing things in Python, this section isn't actually helpful.

Part Two begins with an example of writing your own Zope product in Python (though not one that actually does anything useful), rapidly followed by the process of creating a real product in Python. Given the detail and scope of the AddressBook products, there is no need for the first "create a product" example. Chapter 8 continues with adding functionality to the AddressBook product.

Chapter 9 is Zope Product Security. This chapter explains both what Zope will and won't do for you, and how to determine security requirements and policies. Chapter 10 finishes up the AddressBook application and explains the use security concepts to control levels of access. The order is slightly awkward: it would have made more sense to introduce security concepts before going down the entire create-a-product path, rather than take a side trip in the middle.

Part Three: Management. Not PHBs, but application management. This starts off with Content Management. If you remove the specific Zope examples, you have what amounts to a best-practices guide to web development regardless of language. This is a Good Thing(tm). Database Management assumes zero familiarity with databases and provides a nice basic intro to databases and specifically how to connect assorted DBs to Zope as well as how to integrate SQL with DTML. The last part of the triumvirate is User Management and Security. This section covers the basics (users/roles) and a very light taste of addons, but really could stand a bit more breadth.

Part Four is called Advanced Zope Concept, or "everything that doesn't really fit anywhere else." ZClasses can hardly be considered an advanced concept, especially when compared to rolling your own product in Python. Zope Core components is a compilation of basic OO concepts (acquisition, persistence), the ZODB, ZPublisher, and Document Templates. This is another section that could have been better served by more detail. DocumentTemplates is breezed through with no detail whatsoever.

Scripting Zope demonstrates once again how to extend Zope using Python and covers scripting with Perl in just under two pages.

ZClasses, which have in the past been the most common method of writing Zope products, are discussed in fair detail, including a nice comparison of ZClasses -vs- PythonProducts.

Chapter 17 covers searching, describing how the ZCatalog works and how to leverage it. Zope Page Templates warrant their own (very brief) chapter which explains the shortcomings of DTML (HTML-editor unfriendly, not renderable, mixes presentation and logic) and gives a decent overview of the new PageTemplates that are meant to replace DTML in many instances.

Debugging is another light chapter, though it does cover the essentials fairly well. Finally comes Alternative Methods of Running Zope. This, as you might expect, explains how to use Zope with Apache/IIS and also addresses scalability, with a focus on Zope Enterprise Objects.

The appendices consist of What's On the CD-ROM and Installing Zope from the Red Hat RPMS or Souce Code.

What's Bad?
Zope Bible is a misnomer. There is a lot of great information here, but many sections are to shallow to be of any use. A more appropriate title would be "Python for Zope" or "Advanced Zope Development with Python." The book claims to be aimed at beginning to advanced users, but it is not organized in a manner that will be useful to Zope newbies and the things a beginner needs to know most often are missing or covered in such little detail as to be as good as missing. They could have dropped the first three chapters, and used that space to flesh out some of the later chapters and perhaps do a second case study.

What's Good?
The sections that are good are very good. The authors obviously have a deep understanding of Zope, and I didn't catch any technical errors. The writing is clear and effective. If you're already familiar with Zope and already have The Zope Book and The Book of Zope, then this would be a great next book for getting more into the Python parts of Zope. I particularly liked that they built an actual useful product from end to end in the course of several chapters explaining how different features of Zope can be used. The reference sections on CM and DBM are great. It's nice to see some aspects of Zope that are woefully underdocumented get addressed (Templates, DB integration, Security, Searching) even if some of them aren't in as much detail as I'd like.

You can purchase the Zope Bible from bn.com. Want to see your own review here? Just read the book review guidelines, then use Slashdot's handy submission form.

During the cavalcade of April Fool's spoofs here on /., one submission stuck in my mind as fascinating and enjoyable -- and a complete scam. It was about an alleged anti-gravity disc, made from a 12" superconducting ring that looked not unlike a brake pad. As luck would have it, I was reading the book Voodoo Science at the time and thought once the April Fools hoopla had died down that I'd do a review of it for Slashdot, so read on if you care to. Voodoo Science: The Road from Foolishness to Fraud author Robert Park pages 230 publisher Oxford University Press rating 4/5 reviewer chrisd ISBN 0195147103 summary Robert Park exposes how bad science propogates. Perhaps I should have posted the story, but in the end that sort of pseudo-scientific chicanery doesn't even deserve the attention that /. would bring it on April Fool's day.

The short review of Voodoo Science is that this is not a book that would make a good birthday gift for Alex Chiu or for that matter Deepak Chopra.

Voodoo Science is a happy little bon-bon of a book for the scientifically inclined. Robert Park is the head of the Washington office of the American Physical Society, and has worked inside the beltway helping the U.S. government and others understand the basics of science so they can make appropriate policy decisions. It is depressingly clear how badly they need it.

While there is a certain level of joy to be found in reading about Mr. Park's exploits debunking cranks and frauds, there is a sad realization that prominent legislators have no clue as to the physical laws that are the underpinnings of science. No, I wasn't surprised, but it was depressing nonetheless to see Trent Lott's name on a resolution designed to push through a patent on a "free energy" device, or Tom Harkin using his power to force the NIH to embrace alternative medicine as anything other than a placebo.

While fun, this isn't a perfect book. It is organized a little strangely, with subheadings throwing off the flow of reading, and at a little over 200 pages it seems too short.Park's mission with this book was not to dissect the great scientific frauds of all time, but I thought he could have spent more time on the issues he did bring up and less on trying to understand the Alex Chius of the world. Mr. Park is probably just trying to be polite, but in my reading of Voodoo Science he comes off as being too soft on the very targets of the book.

The case of cold fusion is a perfect example. His recounting of the famous events was right on, but it just fell flat when it came to to point the finger at Pons, Fleischman and the University of Utah for their complicity in fraud before the Utah state legislature. It is akin to writing a book about Enron and saying about Ken Lay: "It is likely he knew what he was doing was possibly improper."

I'd recommend Voodoo Science as a good gift to a younger reader, as it describes foundations of science in an accessible way. As you've probably gathered, an appropriate name for this book might be "The Laws of Thermodynamics and those that thought it didn't apply to them." As such, the book serves as a decent introduction to critical thinking about the physical world around us.

You can purchase Voodoo Science from bn.com. Want to see your own review here? Just read the book review guidelines, then use Slashdot's handy submission form.

Peter Wayner writes: "A friend of mine who works as a public defender knows a thing or two about selling fear to the jury filled with doubts. Several months before December 31st, 1999, he asked me if we should be worried about the Y2K disasters. My answer was: The machines crash every day. Why should it matter if it happens on December 31st?" This time around though, the fears are of a different nature and scope: Peter reviews below Edward Yourdon's latest book Byte Wars, one aimed at everyone concerned about online terrorism in the post-9/11 climate. Byte Wars: The Impact of September 11 on Information Technology author Edward Yourdon pages 300 publisher Prentice Hall rating 7 reviewer Peter Wayner ISBN 0130477257 summary Plainspoken but fear-centric advice for reducing the dangers of vandals or terrorists to online systems.

My friend who nodded as if this was the same game he played every day in the courtroom. If no one knew what was going to happen, the jury's instincts could be manipulated with a mixture of fear, sympathy and tribalism. Juries were always afraid of watching a good, relatively innocent man lose everything, he explained. Corporate executives were just as worried of the same thing happening to them.

The Y2K binge is long gone and the biggest effect on computers seems to be found in the bits representing the bank accounts of Y2K consultants. Gimmicks may fade but human nature and human fear remains the same. The destruction of the World Trade Center has given new life to the fear mongers who worry that someone may obliterate our electronic infrastructure. Edward Yourdon, the old school computer consultant who made plenty of noise about Y2K, is back with another book, Byte Wars: The Impact of September 11th on Information Technology .

When I say old school, I mean that he started programming and writing about programming in the mid 1970s and this shows in the way he spells ( "Obe Wan Kenobee") and talks about "paradigm shifts" instead of "memes." He comes from the age group that decided how much to spend on Y2K and he knows how to talk to the group that will control how much we spend on our fears of terrorism.

There is no mention of his record on Y2K on the book cover or the biography, but if you're interested, the net never forgets. The book does mention the scary days of December 1999 a bit in passing, but only to note that there was "very little awareness in the media" that some "small organizations did suffer moderate-to-severe Y2K problems." He also notes with some pride that many companies survived the turmoil after the World Trade Center attack because they made so many preparations for the turn of the millennium.

This time around Yourdon is blessed with a much more concrete threat and this both helps and hurts his cause. On one hand, no one can debate the power of airplanes as weapons in the same way we can still debate whether Y2K would make a difference to embedded controllers. On the other hand, it's not really clear what the latest attacks have to do with computer networks. He even notes that the DOD's computers were relatively unhurt by the destruction of the Pentagon. How many web sites or e-commerce sites can anyone knock out with a box cutter? One company I knew with offices on the 81st floor of the World Trade Center used a co-lo facility that survived. Their web site kept on pumping out hits even after their entire office turned to dust.

Yourdon dodges all of this by being politely vague and abstract. His chapter on risk management, for instance, counsels that we should find a "realistic assessment of risks" and weigh the probability against the danger. If we develop a process to deal with the risk, then we can ensure that the risks are shared between the stakeholders. Most of the chapter could have been written at any time about any risk , but he makes it all a bit more current by including a few references to kamikaze players who are shifting the paradigm.

Some of his advice gets so abstract that it's hard to know exactly what he is suggesting. He tells us to "examine the practical impact of increased security and decreased privacy." To him, that means warning people who rely upon the social freedom of "don't ask, don't tell" to realize that so much information about us will eventually be documented by the new security state. "Now is the time to think about such matters, not two or three years from now when you suddenly find that you can't get a job, or can't buy a house in a particular neighborhood." Should we rise up or acquiesce? Which side is he on? I'm still not sure. He does such a good job playing to everyone's fears.

Occasionally, he doles out some practical advice that is close to the needs of managers worried about the aftereffects of 9/11. We are told that terrorists may be posing as "ordinary employees" or even government employees who've "risen to high levels of trust and authority." He reminds us that "hardly anyone watches the programmers." Is some terrorist slipping in a buffer-overflow loophole? Or maybe just a crook? One of the most practical suggestions is that corporations should do more code reviews.

He's also hip to some of the latest intellectual fads. Emergent organisms like Napster can be useful and resilient. He's a big fan of empowering employees by cutting away bureaucracy so the organization can evolve some emergent intelligence. Of course, we must also be ready for more scrutiny from the security bureaucracy checking to ensure that the emergent organism isn't evolving buffer-overflow backdoors. This gets a bit confusing and he waves away much of conflict with abstract calls for balance.

In the end, Yourdon can't offer many answers because there aren't many answers to give. We had risks, terrorism, info warfare, bombs and whatnot before September 11th and we'll meet them again despite the security. Anarchists detonated a horse powered wagon filled with explosives in front of the NY Fed in the 1920s. Not much has really changed and the book ends up being a distilled version of the inchoate fears that haunt us.

The real challenge is determining how much fear we should have. Yourdon is far from the only person who automatically assumes that the attacks on New York mean more attention to cybersecurity. All of the major beltway consultants near Washington are gearing up with the new tools. The more I read the book, the more I began wondering why. Why do some kamikaze hijackers mean that the web needs to be locked down? Who really has time to worry about some al Queda l33t d00dz owning my site when so many people are dying true deaths that can't be fixed with backup tapes?

At the end of one of the chapters, Yourdon exhorts us to get our act together and secure our home computers. Our old, pre-9/11 computing style was equivalent to "living in a house with the doors and windows wide open", he says, something that was "a pleasant way to live if you were in a small town in the 1950s."

Ah, the 50s. He and everyone else should rent a copy of George Lucas's pre-Star Wars classic, "American Graffiti." In one scene, the teenagers cheerfully drop a cherry bomb down the school's toilet. In another, they destroy a police car by wrapping a chain around the rear axle. The laugh track blessed both events in the movie, but all of us know that they would bring out the SWAT teams today.

The movie managed to avoid much of the discussion about Eisenhower, Francis Gary Powers, the Russian H-Bomb, or any of the other fears rippling down our spines. The 50's seem so much more fun after editing out the fact that the Russians had (and still have) fusion bombs on the tips of missiles. No amount of frisking by airport security can keep them out of our airspace. Yet we survived and managed to laugh about kids trashing police cars.

Another solution is not to quiver and worry about Osama bin Hacker's script kiddies. We can redefine the terms of engagement in much the same way that the cops in the "American Graffiti" just laughed at those impish kids. Hacked web sites are easy to restore if you have adequate backups. Denial of service attacks from zombies on cable modems sound threatening, but they rarely last longer than Friday evening rush hour.

It's hard to argue with much of the plainspoken, largely abstract advice offered by Yourdon. All of it makes good sense. The harder problem is finding the right attitude to carry us through the night. This book is filled with worry for our future and awe of the unseen l33t d00dz hiding under the bed. There are bits of light and a stab at optimism near the end, but most of the book trades on the thoughts that will keep us up well past midnight.

Peter Wayner has two resilient books emerging this spring: Translucent Databases , an exploration of database security, and Disappearing Cryptography: Information Hiding, Steganography and Watermarks , the second edition devoted to hiding secret messages in plain sight. You can purchase Byte Wars from bn.com. Want to see your own review here? Just read the book review guidelines, then use Slashdot's handy submission form.

Tal Cohen writes: "It is said that one of the most important skills a physicist needs is the ability to quickly make "back-of-the-envelope" calculations. For example, Jan Wolitzky (in Jon Bently's "Programming Pearls") tells about Enrico Fermi, Robert Oppenheimer, and the other Manhattan Project brass who were behind a low blast wall awaiting the detonation of the first nuclear device from a few thousand yards away. Fermi was tearing up sheets of paper into little pieces, which he tossed into the air when he saw the flash. After the shock wave passed, he paced off the distance traveled by the paper shreds, performed a quick "back-of-the-envelope" calculation, and arrived at a figure for the explosive yield of the bomb, which was confirmed much later by expensive monitoring equipment." Read on to find out what this has to do with the unusual characteristics of Earth, and how they could influence our search for life elsewhere in the universe. Rare Earth: Why Complex Life is Uncommon in the Universe author Peter D. Ward, Donald Brownlee pages 368 publisher Copernicus rating 7 reviewer Tal Cohen ISBN 0387987010 summary Maybe we are alone, after all.

But expensive monitoring equipment which can confirm the calculation does not always exist, and hence in some fields, our entire knowledge is based on back-of-the-envelope calculations and rough estimates.

Take, for example, the following question: "How many intelligent civilizations, capable of radio communications, currently exist in the Milky Way galaxy?". The worthwhileness of search projects (such as SETI) is closely related to the answer to this question. The number of positively known civilizations is exactly one: the human civilization. And yet, many scientists believe, or at least believed until recently, that the actual number is far, far higher.

This belief was based on various estimates, such as the calculation proposed by Frank Drake, now known as "The Drake Equation." This equation was popularized in Carl Sagan's remarkable TV series, "Cosmos". Sagan himself believed the calculation's result, and was one of the founders of SETI.

Drake's equation is easy to understand. Take the number of stars in the galaxy (about 200 to 300 billion, based on generally accepted estimates), and multiply it by: the percentage of stars that are similar to our Sun in the energy output and stability; the percentage of stars that have planets (since not every star has any); the percentage of planets orbiting their star in a proper distance (so they could hold liquid water, a necessity for maintaining life); the percentage of planets with liquid water on which life actually evolved; and finally, the percentage of life-bearing planets in which intelligent civilizations (i.e., those that can communicate by radio) eventually came to be. All in all, there are five or six factors in this product.

(Note: In my own copy of the book (2nd impression), page 267 states that "a good estimate for the number of stars in our galaxy [is] between 200 and 300 million" - one letter misspelled, and wrong by three orders of magnitude. I do hope the authors' actual calculations were based on the correct value.)

But what values should be used for the various percentages? Drake (and Sagan) chose what they considered to be a conservative approach, and estimated that only about 1 in 10 stars has any planets; only 1 in 10 planets is in the proper orbit, and so forth. Despite the conservative approach, the results were encouraging, indicating that there are thousands of intelligent civilizations in the Milky Way, and probably millions of them in the whole universe. Thus they concluded that there is intelligent life out there, in all likelihood; now we only have to look for it.

In their book Rare Earth, published by Copernicus Press in 2000, Peter Ward and Donald Brownlee point at Drake's (and other physicists') mistakes in a long and depressing discussion, a discussion that took the wind out of more than one SF author's sail.

The book presents what the authors call "the rare Earth hypothesis": simple (bacterial) life is very common in the universe; complex life (multi-cellular life forms, or animals -- let alone intelligent life) is very rare. The first part of the hypothesis is easy to understand, and few scientists will argue with it: indications of simple life were already discovered on rocks originating on Mars, and even here on Earth in conditions that were, until recently, considered completely hostile to life (such as temperatures higher than 100 degrees Celsius, in which 'extremophile' bacteria were found to exist). The second part is the interesting one, and it suggests that the existence of simple life does not necessarily lead to the evolutionary development of complex life, for any number of reasons.

Drake's mistake was basically in the assumption that all it takes for a planet to develop life is being in the proper distance from a proper star. The truth, Ward and Brownlee suggest, is that we have to look at each and every attribute of Earth, and re-estimate its importance for supporting life. Drake's equation is a statistical calculation, but with no other example for life, we're doing statistics with N=1.

Well then, what are the special attributes of Earth that we have to take into account when attempting to run this calculation?

• Proper distance from the star. If a planet orbits its sun too closely or too far away, liquid water would not exist. There isn't much margin for error here: a change of 5 to 15 percent in Earth's distance from the Sun would lead to the freezing, or boiling, of all water on Earth.
• Proper distance from the center of the galaxy. The density of stars near the center of the galaxy is so high, that the amount of cosmic radiation in that area would prevent the development of life.
• A star of a proper mass. A too-massive star would emit too much ultra-violet energy, preventing the development of life. A star that is too small would require the planet to be closer to it (in order to maintain liquid water). But such a close distance would result in tidal locking (where one face of the planet constantly faces the star, and the other always remains dark -- as with the moon in its orbit around Earth). In this case one side becomes too hot, the other too cold, and the planet's atmosphere escapes.
• A proper mass. A planet that is too small will not be able to maintain any atmosphere. A planet that is too massive would attract a larger number of asteroids, increasing the chances of life-destroying cataclysms.
• Oceans. The ability to maintain liquid water does not automatically imply that there will be any on the planet's surface. It looks like Earth acquired its own water from asteroids made of ice that crashed here billions of years ago. On the other hand, too much water (i.e., a planet with little or no land) will lead to an unstable atmosphere, unfit for maintaining life.
• A constant energy output from the star. If the star's energy output suddenly decreases, even for a relatively short while, all the water on the planet would freeze. This situation is irreversible, since when the star resumes its normal energy output, the planet's now-white surface will reflect most of this energy, and the ice will never melt. Conversely, if the stars energy output increases for a short while, all the oceans will evaporate and the result would be an irreversible greenhouse-effect, preventing the oceans from reforming.
• Successful evolution. Even if all of these conditions hold, and simple life evolves (which probably happens even if some of these conditions aren't met), this still does not imply that the result is animal (multi-cellular) life. The evolution of life on Earth included some surprising leaps; two worth mentioning are the move from simple, single-cellular life to cells which contain internal organs, and the appearance of calcium-based skeletons. It appears like the first of these leaps took more time than the evolution from complex single-celled life to full-blown humans.
• Avoiding disasters. Any number of disasters can lead to the complete extinction of all life on a planet. This include the supernova of a nearby star; a massive asteroid impact (like the one that probably caused the extinction of dinosaurs, and 70% of all other life-forms at the time); drastic changes of climate; and so on.

There are also a few attributes that seem, at first, to be completely unrelated to life and not required for its development. Ward and Brownlee argue strongly for the importance of the following attributes:

• The existence of a Jupiter-like planet in the system. Apparently, Jupiter's large mass attracted many of the asteroids that would have otherwise hit Earth. Could life evolve in a system with no Jovian planet? On the other hand, too many Jovian planets, or one that is too large, could lead to a non-stable solar system, sending the smaller planets into the central sun or ejecting them into the cold of space.
• The existence of a large, nearby moon. Luna, Earth's moon, is atypically large and close. Both of Mars's moons, for example, are minor rocks by comparison. What does this have to do with life? Well, it turns out that Luna kept (and still keeps) Earth's tilt stable. Without Luna, the tilt would have changed drastically over time, and no stable climate could exist. If the tilt would have stabilized on a too-large or too-small value, the results could also be disastrous; Earth's tilt is "just right."
• Plate tectonics. Surprisingly enough, it seems like plate tectonics are required for maintaining a stable atmosphere. Plate tectonics play an important role in a complex feedback system (explained in detail in the book) that prevents too many greenhouse gases from existing in the atmosphere. No other planet (except maybe for Jupiter's moon Europa) is known to have plate tectonics. Is this a rare phenomenon, but required for life?

The bottom line is that many additional factors must be added to Drake's equation. One must keep in mind that as any term in such an equation approaches zero, so too does the final product. For most terms, we have no way of reliably estimating their true value, but it seems like at least some of these values are extremely low.

Two important things should be noted about this book. First, about what it does not contain: although I am sure many people will see the Rare Earth Hypothesis as another proof for the existence of a god, this notion of a proof is completely unrelated to the authors' ideas. The hypothesis claims that the conditions for creating complex life are rare; but we know for a fact that at least in one case, all the required conditions were met. Additionally, anyone who insists on taking the ideas of this book as a proof for god's existence will also have to accept the authors' prepositions about the age of the universe, the age of planet Earth, and more importantly, the theory of evolution.

Second, about what the book does contain: the book discusses at length all the issues I've listed above, and more. The problem is that sometimes one gets the feeling that these issues are discussed in too much detail, and the authors tend to repeat themselves, or to delve too deep into some of the less-important aspects of their theory. This is certainly not your common popular-science book; it relies on very up-to-date research results (including some results that were not even published when the book went to press). The writing gets technical on many points in astrophysics, biology, chemistry, and geology (as well as the new field of astrobiology, of course). Over 25 pages of bibliography and references are included.

The theory's weakest point, however, is obvious. The authors admit (after 281 pages of discussion) that their base assumption was that every complex life-form would be similar in many ways to life on Earth: "We assume in this book that animal life will be somehow Earth-like. We take the perhaps jingoistic stance that Earth-life is every-life, that lessons from Earth are not only guides but also rules. We assume that DNA is the only way, rather than only one way" (p. 282).

For me, reading this book was a fascinating and awe-inspiring experience. The most important conclusion (apart from SETI being a huge waste of resources) is an unavoidable cliché, which the authors avoided presenting directly, even though it stares into the reader's face from every page and each paragraph: What we have here is rare, maybe even unique. We should try a little harder to make sure it survives.

Post Scriptum: A news item in the November/December 2001 issue of the Skeptical Inquirer (Vol. 25, No. 6) states that "David Darling, an astronomer who is a critic of the Rare Earth hypothesis, has revealed that one of the strongest influences on the authors, a young [...] astronomer who they acknowledge in their preface 'changed many of our views about planets and habitable zones', has a hidden, Earth-is-unique agenda motivated by strong 'intelligent design' religious views." That astronomer, Guillermo Gonzalez, published several articles in Connections, a quarterly newsletter published by Reasons to Believe, Inc. In one of these articles, co-authored with the creationist scientist Hugh Ross, Gonzalez writes: "The fact that the Sun's location is fine-tuned to permit the possibility of life [...] powerfully suggests divine design."

Darling published these findings, along with a detailed point-by-point scientific critique of the Rare Earth hypothesis, in his book Life Everywhere: The Maverick Science of Astrobiology . Skeptical Inquirer quotes Darling as saying, "What matters is not whether there's anything unusual about the Earth; there's going to be something idiosyncratic about every planet in space. What matters is whether any of Earth's circumstances are not only unusual but also essential for complex life. So far we've seen nothing to suggest there is."

For more about this book, please see this page. For additional book reviews, please visit Tal's bookshelf. You can purchase Rare Earth from bn.com. Want to see your own review here? Just read the book review guidelines, then use Slashdot's handy submission form.

Tal Cohen writes: "It is said that one of the most important skills a physicist needs is the ability to quickly make "back-of-the-envelope" calculations. For example, Jan Wolitzky (in Jon Bently's "Programming Pearls") tells about Enrico Fermi, Robert Oppenheimer, and the other Manhattan Project brass who were behind a low blast wall awaiting the detonation of the first nuclear device from a few thousand yards away. Fermi was tearing up sheets of paper into little pieces, which he tossed into the air when he saw the flash. After the shock wave passed, he paced off the distance traveled by the paper shreds, performed a quick "back-of-the-envelope" calculation, and arrived at a figure for the explosive yield of the bomb, which was confirmed much later by expensive monitoring equipment." Read on to find out what this has to do with the unusual characteristics of Earth, and how they could influence our search for life elsewhere in the universe. Rare Earth: Why Complex Life is Uncommon in the Universe author Peter D. Ward, Donald Brownlee pages 368 publisher Copernicus rating 7 reviewer Tal Cohen ISBN 0387987010 summary Maybe we are alone, after all.

But expensive monitoring equipment which can confirm the calculation does not always exist, and hence in some fields, our entire knowledge is based on back-of-the-envelope calculations and rough estimates.

Take, for example, the following question: "How many intelligent civilizations, capable of radio communications, currently exist in the Milky Way galaxy?". The worthwhileness of search projects (such as SETI) is closely related to the answer to this question. The number of positively known civilizations is exactly one: the human civilization. And yet, many scientists believe, or at least believed until recently, that the actual number is far, far higher.

This belief was based on various estimates, such as the calculation proposed by Frank Drake, now known as "The Drake Equation." This equation was popularized in Carl Sagan's remarkable TV series, "Cosmos". Sagan himself believed the calculation's result, and was one of the founders of SETI.

Drake's equation is easy to understand. Take the number of stars in the galaxy (about 200 to 300 billion, based on generally accepted estimates), and multiply it by: the percentage of stars that are similar to our Sun in the energy output and stability; the percentage of stars that have planets (since not every star has any); the percentage of planets orbiting their star in a proper distance (so they could hold liquid water, a necessity for maintaining life); the percentage of planets with liquid water on which life actually evolved; and finally, the percentage of life-bearing planets in which intelligent civilizations (i.e., those that can communicate by radio) eventually came to be. All in all, there are five or six factors in this product.

(Note: In my own copy of the book (2nd impression), page 267 states that "a good estimate for the number of stars in our galaxy [is] between 200 and 300 million" - one letter misspelled, and wrong by three orders of magnitude. I do hope the authors' actual calculations were based on the correct value.)

But what values should be used for the various percentages? Drake (and Sagan) chose what they considered to be a conservative approach, and estimated that only about 1 in 10 stars has any planets; only 1 in 10 planets is in the proper orbit, and so forth. Despite the conservative approach, the results were encouraging, indicating that there are thousands of intelligent civilizations in the Milky Way, and probably millions of them in the whole universe. Thus they concluded that there is intelligent life out there, in all likelihood; now we only have to look for it.

In their book Rare Earth, published by Copernicus Press in 2000, Peter Ward and Donald Brownlee point at Drake's (and other physicists') mistakes in a long and depressing discussion, a discussion that took the wind out of more than one SF author's sail.

The book presents what the authors call "the rare Earth hypothesis": simple (bacterial) life is very common in the universe; complex life (multi-cellular life forms, or animals -- let alone intelligent life) is very rare. The first part of the hypothesis is easy to understand, and few scientists will argue with it: indications of simple life were already discovered on rocks originating on Mars, and even here on Earth in conditions that were, until recently, considered completely hostile to life (such as temperatures higher than 100 degrees Celsius, in which 'extremophile' bacteria were found to exist). The second part is the interesting one, and it suggests that the existence of simple life does not necessarily lead to the evolutionary development of complex life, for any number of reasons.

Drake's mistake was basically in the assumption that all it takes for a planet to develop life is being in the proper distance from a proper star. The truth, Ward and Brownlee suggest, is that we have to look at each and every attribute of Earth, and re-estimate its importance for supporting life. Drake's equation is a statistical calculation, but with no other example for life, we're doing statistics with N=1.

Well then, what are the special attributes of Earth that we have to take into account when attempting to run this calculation?

• Proper distance from the star. If a planet orbits its sun too closely or too far away, liquid water would not exist. There isn't much margin for error here: a change of 5 to 15 percent in Earth's distance from the Sun would lead to the freezing, or boiling, of all water on Earth.
• Proper distance from the center of the galaxy. The density of stars near the center of the galaxy is so high, that the amount of cosmic radiation in that area would prevent the development of life.
• A star of a proper mass. A too-massive star would emit too much ultra-violet energy, preventing the development of life. A star that is too small would require the planet to be closer to it (in order to maintain liquid water). But such a close distance would result in tidal locking (where one face of the planet constantly faces the star, and the other always remains dark -- as with the moon in its orbit around Earth). In this case one side becomes too hot, the other too cold, and the planet's atmosphere escapes.
• A proper mass. A planet that is too small will not be able to maintain any atmosphere. A planet that is too massive would attract a larger number of asteroids, increasing the chances of life-destroying cataclysms.
• Oceans. The ability to maintain liquid water does not automatically imply that there will be any on the planet's surface. It looks like Earth acquired its own water from asteroids made of ice that crashed here billions of years ago. On the other hand, too much water (i.e., a planet with little or no land) will lead to an unstable atmosphere, unfit for maintaining life.
• A constant energy output from the star. If the star's energy output suddenly decreases, even for a relatively short while, all the water on the planet would freeze. This situation is irreversible, since when the star resumes its normal energy output, the planet's now-white surface will reflect most of this energy, and the ice will never melt. Conversely, if the stars energy output increases for a short while, all the oceans will evaporate and the result would be an irreversible greenhouse-effect, preventing the oceans from reforming.
• Successful evolution. Even if all of these conditions hold, and simple life evolves (which probably happens even if some of these conditions aren't met), this still does not imply that the result is animal (multi-cellular) life. The evolution of life on Earth included some surprising leaps; two worth mentioning are the move from simple, single-cellular life to cells which contain internal organs, and the appearance of calcium-based skeletons. It appears like the first of these leaps took more time than the evolution from complex single-celled life to full-blown humans.
• Avoiding disasters. Any number of disasters can lead to the complete extinction of all life on a planet. This include the supernova of a nearby star; a massive asteroid impact (like the one that probably caused the extinction of dinosaurs, and 70% of all other life-forms at the time); drastic changes of climate; and so on.

There are also a few attributes that seem, at first, to be completely unrelated to life and not required for its development. Ward and Brownlee argue strongly for the importance of the following attributes:

• The existence of a Jupiter-like planet in the system. Apparently, Jupiter's large mass attracted many of the asteroids that would have otherwise hit Earth. Could life evolve in a system with no Jovian planet? On the other hand, too many Jovian planets, or one that is too large, could lead to a non-stable solar system, sending the smaller planets into the central sun or ejecting them into the cold of space.
• The existence of a large, nearby moon. Luna, Earth's moon, is atypically large and close. Both of Mars's moons, for example, are minor rocks by comparison. What does this have to do with life? Well, it turns out that Luna kept (and still keeps) Earth's tilt stable. Without Luna, the tilt would have changed drastically over time, and no stable climate could exist. If the tilt would have stabilized on a too-large or too-small value, the results could also be disastrous; Earth's tilt is "just right."
• Plate tectonics. Surprisingly enough, it seems like plate tectonics are required for maintaining a stable atmosphere. Plate tectonics play an important role in a complex feedback system (explained in detail in the book) that prevents too many greenhouse gases from existing in the atmosphere. No other planet (except maybe for Jupiter's moon Europa) is known to have plate tectonics. Is this a rare phenomenon, but required for life?

The bottom line is that many additional factors must be added to Drake's equation. One must keep in mind that as any term in such an equation approaches zero, so too does the final product. For most terms, we have no way of reliably estimating their true value, but it seems like at least some of these values are extremely low.

Two important things should be noted about this book. First, about what it does not contain: although I am sure many people will see the Rare Earth Hypothesis as another proof for the existence of a god, this notion of a proof is completely unrelated to the authors' ideas. The hypothesis claims that the conditions for creating complex life are rare; but we know for a fact that at least in one case, all the required conditions were met. Additionally, anyone who insists on taking the ideas of this book as a proof for god's existence will also have to accept the authors' prepositions about the age of the universe, the age of planet Earth, and more importantly, the theory of evolution.

Second, about what the book does contain: the book discusses at length all the issues I've listed above, and more. The problem is that sometimes one gets the feeling that these issues are discussed in too much detail, and the authors tend to repeat themselves, or to delve too deep into some of the less-important aspects of their theory. This is certainly not your common popular-science book; it relies on very up-to-date research results (including some results that were not even published when the book went to press). The writing gets technical on many points in astrophysics, biology, chemistry, and geology (as well as the new field of astrobiology, of course). Over 25 pages of bibliography and references are included.

The theory's weakest point, however, is obvious. The authors admit (after 281 pages of discussion) that their base assumption was that every complex life-form would be similar in many ways to life on Earth: "We assume in this book that animal life will be somehow Earth-like. We take the perhaps jingoistic stance that Earth-life is every-life, that lessons from Earth are not only guides but also rules. We assume that DNA is the only way, rather than only one way" (p. 282).

For me, reading this book was a fascinating and awe-inspiring experience. The most important conclusion (apart from SETI being a huge waste of resources) is an unavoidable cliché, which the authors avoided presenting directly, even though it stares into the reader's face from every page and each paragraph: What we have here is rare, maybe even unique. We should try a little harder to make sure it survives.

Post Scriptum: A news item in the November/December 2001 issue of the Skeptical Inquirer (Vol. 25, No. 6) states that "David Darling, an astronomer who is a critic of the Rare Earth hypothesis, has revealed that one of the strongest influences on the authors, a young [...] astronomer who they acknowledge in their preface 'changed many of our views about planets and habitable zones', has a hidden, Earth-is-unique agenda motivated by strong 'intelligent design' religious views." That astronomer, Guillermo Gonzalez, published several articles in Connections, a quarterly newsletter published by Reasons to Believe, Inc. In one of these articles, co-authored with the creationist scientist Hugh Ross, Gonzalez writes: "The fact that the Sun's location is fine-tuned to permit the possibility of life [...] powerfully suggests divine design."

Darling published these findings, along with a detailed point-by-point scientific critique of the Rare Earth hypothesis, in his book Life Everywhere: The Maverick Science of Astrobiology . Skeptical Inquirer quotes Darling as saying, "What matters is not whether there's anything unusual about the Earth; there's going to be something idiosyncratic about every planet in space. What matters is whether any of Earth's circumstances are not only unusual but also essential for complex life. So far we've seen nothing to suggest there is."

For more about this book, please see this page. For additional book reviews, please visit Tal's bookshelf. You can purchase Rare Earth from bn.com. Want to see your own review here? Just read the book review guidelines, then use Slashdot's handy submission form.

Reader cpfeifer contributes the review below of O'Reilly's Programming Jabber: if your job (or hobby) includes instant messaging in all its glory, Jabber is a free-beer, free-speech framework for setting up instant messaging systems not bound to a single server in the middle. As cpfeifer points out, instant messaging can mean a lot more than popping an on-screen note to your friend in Des Moines -- machines and programs can use a general purpose communication system like this, with no human middleman required. Programming Jabber author D.J. Adams pages 4555 publisher O'Reilly rating 9 reviewer http://cpfeifer.blogspot.com ISBN 0596002025 summary A detailed guide for developers to understanding and extending the Jabber messaging framework. Examples in Perl, Python and Java. The Scenario

Jabber was first conceived by Jeremie Miller (pic) in early 1998 in an effort to unify the disparate instant messaging networks. Instant Messaging networks rely on the network effect to gain and retain marketshare. The concept is the same when applied to any sort of participatory network whether it's a junk exchange, or content exchange, the value of the network increases with the square of the number of participants.

If this is true, then doesn't it follow that it is in the best interests of the IM networks to establish peering agreements with each other so that their users can directly contact users on other networks without having to install each client?

Hello, Jabber.

When I first picked up this book, I expected to understand the Jabber protocol in sufficient depth to implement my own IM client. Instead, the approach this book takes is that Jabber isn't just an XML-based protocol strictly for IM, rather it is a general purpose event notification protocol that has some very nice message routing and user management features built into it. While i was reading about the messages that Jabber has defined as part of the protocol, I could easily see other applications/devices generating Jabber messages to notify subscribers (either other systems, or people) of events.

Part 1 of the book focuses on getting you up to speed on the basics of Jabber technology: motivation, major features, XML protocol sample and compiling/configuring your own Jabber server. Chapter 2 presents the "10,000 foot view" of Jabber technology. In here you will find a sample client-query request/response flow with full HTTP headers, discussed step by step. The next two chapters are a very in-depth discussion of installing and configuring your own Jabber server. When you dive into a custom configuration of a fleet of Jabber servers (a "constellation" in Jabber terminology), it really starts to hit home that the real problem Jabber solves is far deeper than just IM.

From there, part 2 kicks off with a detailed discussion of the most basic building blocks of Jabber technology: resource identifiers, XML handling mechanism and the set of XML elements/attributes that make up the vocabulary of the Jabber protocol. Each element/attribute is presented with an annotated example and sample client/server interactions where appropriate. Examples can make or break a technical book, and these examples do a good job of illustrating how the element/attribute is used.

The following chapters take you through using standard Jabber features, user registration/authorization, messages, presence, groupchat, components and the event model to enable new applications. One very interesting application presented is enabling developers to receive CVS commit notifications via Jabber.

What's Bad?

I know the /. community is suspicious of glowing book reviews where everything is wonderful and nothing could be done to improve the book, so I'll nitpick. My major problem with this book is that the overwhelming majority of the sample applications are written in PERL/TK. This isn't a problem in and of itself, but I'm not a PERL/TK developer. If I build a Jabber solution, it will be in java, so PERL/TK samples don't do me a lot of good. I think equal time should be given to implementing Jabber using the two most-used languages, as defined by the number and activity of open source projects using Jabber technology.

What's Good?

This book covers everything relevant to Jabber technology, from lowest level inner workings and extensibility examples for developers to configuration and deployment for admins. Most of the book is spent looking directly at the Jabber XML protocol, instead of a specific API implementation. This way, the book covers the technology and doesn't get lost in how one particular API models the protocol.

So What's In It For Me?

If you want to implement an inside-the-firewall IM solution for your company/group/tribe or investigate integrating event notification into an application, this is a great starting point. If you're just curious about Jabber and want to know how it works, then this will give you enough information to get you hooked.

Table of Contents

PART 1: Getting Started with Jabber

• Chapter 1. Introducing Jabber
• Chapter 2. Inside Jabber
• Chapter 3. Installing the Jabber Server
• Chapter 4. Server Architecture and Configuration

PART 2: Putting Jabber's Concepts to Work

• Chapter 5. Jabber Technology Basics
• Chapter 6. Jabber Namespaces
• Chapter 7. User Registration and Authorization
• Chapter 8. Using Messages and Presence
• Chapter 9. Groupchat, Components, and Event Models
• Chapter 10. Pointers for Further Development

Appendix A. The Jabber.xml Contents

Appendix B. The IQRPC Classes for JabberRPCResponder

Index

O'Reilly has posted other reviews of the book on their site. You can purchase Programming Jabber from bn.com. Want to see your own review here? Just read the book review guidelines, then use Slashdot's handy submission form.

In many workplaces, especially high-tech ones, managers and those they manage are operating on parallel tracks, with different sets of motivations, expectations and rewards. How to keep tech workers happy, given that they likely don't want the same things as their bosses, and certainly would choose different ways to achieve them? The long-suffering Jim Richards submitted this review of Managing Einsteins, a book which attempts to inject some sanity into the situation by clueing managers in on what it is their programmers and other tech workers might actually want in a workplace. Read on for his review. Managing Einsteins: Leading High-Tech Workers in the Digital Age author Dr. John M. Ivancevich and Dr. Thomas N. Duening pages 249 publisher McGraw-Hill rating 7 reviewer grumpy ISBN 0-07-137500-7 summary Good information for managers of IT workers

This book doesn't use terms like "nerd" or "geek" to describe IT workers: the authors hold that the stereotype of pocket protectors and coke-bottle glasses just doesn't fit any more. This is a book written for managers, and so the terminology and style (almost) always refers to Einsteins as "your workers," to the point that with the summary at the end states:

Referring to super-intelligent, curious, passionate, often introverted, talented individuals as "geeks" is outdated. Although Einsteins can call colleagues "geeks," it is not appropriate or cool for non-Einsteins to refer to computer, technology, systems or software geniuses as geeks. (page 217)

These are the difficult to work with, yet life-saving employees who can come up with answers when most people don't understand the question.

Several themes run through the book, so it can be summarised in a few simple statements. Many of which (to Einsteins) may seem pretty obvious. The book is written by "Management Professionals," though, so there's hope that managers may actually accept some of its wisdom.

The book is divided into three parts:

1. Realities of the Twenty-First Century - a brief summary covers the basic themes of the book and introduces the concept of an Einstein, the nature of Einsteins and how they fit into the work environment and the world.

2. Managing Einsteins: Challenges and Actions - this section, the bulk of the book, covers everything from recruiting Einsteins through to managing them on a daily basis, by paying attention to communication, teams and tribes, remuneration, etiquette and discipline.

3. Building for the Future - includes humour and fun at work, telecommuting and a final summary.

The book describes IT workers as highly motivated, intelligent (often more intelligent than their managers), introverted, tribal and independent.

The mains themes throughout the book are:

• Managers should be honest with their workers about the company's successes and failures
• The point of management is to guide and suggest not to be autocratic (the metaphor of herding cats was used to illustrate this)
• Let the Einsteins have freedom in work environment (location - there is a whole chapter on telecommuting, hours and style)
• Einsteins are project-focused, not job-focused
• They value training and education highly
• They require a stimulating and fun work place.

The issue of remuneration is covered -- and expanded to include the idea that Einsteins are not solely motivated by money (as sales people may be), and that other considerations should be taken into account (such as training, location, work conditions). Also that the traditional notion of promotion does not always work. An Einstein may not want to become a team leader, or move any higher in the management hierarchy. A manager should be wary of their Einsteins burning out, a temporary demotion or other measure may be in order to take the stress off an Einstein for a while.

The book includes short examples and case studies from various workplaces, and excerpts from newspapers and trade journals to help illustrate points. There are also highlighted points categorised as "Influence Tips," "Black Holes" and "Einstein Wisdom." which emphasise important things, such as:

Managers should be very cautious not to introduce projects that have a low likelihood of getting started. Einsteins abhor routine and crave novel projects. But they abhor being misled and crave honest leadership all the more. In staff meetings, when managers talk about upcoming projects, they should attach a probability of launch along with the projected launch date. The common term for this is "managing expectations." (page 70)

One good description of the nature of how Einsteins work is the concept of flow.

Flow is reported by individuals as a satisfying state they reach when they are completely absorbed in challenging yet achievable projects. (page 54)

Flow is an important concept for managers to understand. Once an Einstein starts a project, and becomes fully involved, there is nothing worse than being pulled off to attend a sales meeting, or other time consuming function. It interrupts the flow.

One pitfall: the book seems to have been started before the tech slump of 2000-2001 really started to dig in. So the book wavers between promoting how IT workers are highly mobile, but also that the job market is not that strong.

The other major shortcoming is the chapter on Etiquette and Manners. Now, I can understand the mannerisms and habits of Einsteins can be a little unpleasant at times, but it begs the question, why would a manager take one of these people out to a client dinner in the first place? If the client needs to meet the tech people to be convinced that a company can do the job, why not at the place of work? Or, take an Einstein who you know you can trust to behave and present well.

As this is the only book at the moment that deals directly with managing this class of workers, also get your manager to read Jon Katz's Geeks. Managing people is no longer about direct, micro-management or process line working. The nature of work has changed with the influence of new technology and so a new way of managing people should also be introduced. These books together will help management, or anyone, understand the mind set and working modes of IT workers.

You can purchase Managing Einsteins from bn.com. Want to see your own review here? Just read the book review guidelines, then use Slashdot's handy submission form.

canadian_right writes: "Philip Pullman has written a great fantasy adventure that children and adults will enjoy. A richly detailed alternate universe is presented in The Golden Compass, and we are introduced to the heroine of the three books, Lyra Belacqua. The story starts off quickly and holds your interest with a series of engaging and imaginative adventures for the length of the three novels. Philip Pullman pulls you effortlessly into these alternate worlds, and holds your attention with a wealth of detail that brings to life the sights and sounds of these new worlds. Some worlds are just a bit different from our own, while others are completely new." Read on for his brief review of the books in this trilogy. The Golden Compass, The Subtle Knife, The Amber Spyglass author Philip Pullman pages (See each) publisher Knopf rating 8 reviewer canadian_right ISBN (See each) summary A trilogy written for kids but deep enough for adults to enjoy.

Lyra soon finds herself at the centre of world shaking events, but unlike so many fantasy books, Philip Pullman has come up with a series of astounding, interlocking adventures, full of wonders, creatures, and worlds that will keep you guessing for the full length of the trilogy. All the main characters in the three books are fully fleshed out, with distinct personalities and motivations. There is a fairly large cast of characters, but the author deftly weaves their stories together, often to great dramatic effect.

This trilogy is marketed as children's literature, but this is a much more intense series than Harry Potter is. Battles are deadly, not glorious; good people that you have come to care about die. Certain unfortunate events unfold with ruthless logic. Organised religion is presented in a very bad light, which will turn off some readers. I wouldn't recommend this series to children under 12, but I enthusiastically recommend His Dark Materials to anyone who enjoys fantasy.

The Golden Compass

Lyra is a resourceful and vivacious young girl who lives at Jordan College -- left there by her rich and powerful Uncle, Lord Asriel. Lyra lives a carefree life doing pretty much as she pleases, but she loves adventure and is continually getting into trouble. Then she overhears a conversation about Dust -- a strange substance mysteriously associated with people. Something about Dust is causing great consternation with the Church and other powerful people. At the same time the gobblers are stealing children. Soon Lyra is propelled into the midst of a great conspiracy that takes her far from the comforting halls of Jordan College, and face to face with terrible danger. Lyra's resourceful optimism makes you want her to succeed, and the world she travels through evokes the wonder of things new, and events unknown.

The action will keep children enthralled, and the imaginative twists and turns will surprise and delight adults and children alike. Various peoples and cultures are met throughout the story, and all find a part to play in the epic battle that builds up over all three books.

The Subtle Knife

The Subtle Knife starts off in our familiar world, and introduces a new character: Will. Will is much more serious than Lyra, but their fates are soon intertwined. Will has lived a much more troubled life looking after his mother after his father's disappearance. Someone badly wants something of his father's, and Will's efforts to protect it quickly lead him from home and entangle him in the events started in the Golden Compass. A great war is brewing and Will is destined to play a key role, along side Lyra, in this conflict. A weapon is discovered that will tilt the balance in this war, and Will's search for his father lands him in the middle of the conflict.

Once again the story pulls you into the believable worlds so artfully drawn by Phillip Pullman. Adventure abounds, betrayal, heroic deeds, and dark conflicts drive the story forward.

The Amber Spyglass

The third book in the series draws the story to a satisfying end. Unlike some series, which seem to never end and leave you hanging at the end of each book in search of another sale, the Amber Spyglass reveals the mysteries alluded to throughout the story, and resolves the final conflict. But not before leading you through another set of breathtaking adventures, unforeseen turns, and an epic battle between good and evil.

I highly recommend this series to anyone over the age of 11 who enjoys excellent fantasy. This is a superior children's series that adults will also enjoy for its well-drawn characters, detailed worlds, and intricate plotting.

You can purchase The Golden Compass, The Subtle Knife and The Amber SpyGlass from B&N. Want to see your own review here? Just read the book review guidelines, then use Slashdot's handy submission form.

canadian_right writes: "Philip Pullman has written a great fantasy adventure that children and adults will enjoy. A richly detailed alternate universe is presented in The Golden Compass, and we are introduced to the heroine of the three books, Lyra Belacqua. The story starts off quickly and holds your interest with a series of engaging and imaginative adventures for the length of the three novels. Philip Pullman pulls you effortlessly into these alternate worlds, and holds your attention with a wealth of detail that brings to life the sights and sounds of these new worlds. Some worlds are just a bit different from our own, while others are completely new." Read on for his brief review of the books in this trilogy. The Golden Compass, The Subtle Knife, The Amber Spyglass author Philip Pullman pages (See each) publisher Knopf rating 8 reviewer canadian_right ISBN (See each) summary A trilogy written for kids but deep enough for adults to enjoy.

Lyra soon finds herself at the centre of world shaking events, but unlike so many fantasy books, Philip Pullman has come up with a series of astounding, interlocking adventures, full of wonders, creatures, and worlds that will keep you guessing for the full length of the trilogy. All the main characters in the three books are fully fleshed out, with distinct personalities and motivations. There is a fairly large cast of characters, but the author deftly weaves their stories together, often to great dramatic effect.

This trilogy is marketed as children's literature, but this is a much more intense series than Harry Potter is. Battles are deadly, not glorious; good people that you have come to care about die. Certain unfortunate events unfold with ruthless logic. Organised religion is presented in a very bad light, which will turn off some readers. I wouldn't recommend this series to children under 12, but I enthusiastically recommend His Dark Materials to anyone who enjoys fantasy.

The Golden Compass

Lyra is a resourceful and vivacious young girl who lives at Jordan College -- left there by her rich and powerful Uncle, Lord Asriel. Lyra lives a carefree life doing pretty much as she pleases, but she loves adventure and is continually getting into trouble. Then she overhears a conversation about Dust -- a strange substance mysteriously associated with people. Something about Dust is causing great consternation with the Church and other powerful people. At the same time the gobblers are stealing children. Soon Lyra is propelled into the midst of a great conspiracy that takes her far from the comforting halls of Jordan College, and face to face with terrible danger. Lyra's resourceful optimism makes you want her to succeed, and the world she travels through evokes the wonder of things new, and events unknown.

The action will keep children enthralled, and the imaginative twists and turns will surprise and delight adults and children alike. Various peoples and cultures are met throughout the story, and all find a part to play in the epic battle that builds up over all three books.

The Subtle Knife

The Subtle Knife starts off in our familiar world, and introduces a new character: Will. Will is much more serious than Lyra, but their fates are soon intertwined. Will has lived a much more troubled life looking after his mother after his father's disappearance. Someone badly wants something of his father's, and Will's efforts to protect it quickly lead him from home and entangle him in the events started in the Golden Compass. A great war is brewing and Will is destined to play a key role, along side Lyra, in this conflict. A weapon is discovered that will tilt the balance in this war, and Will's search for his father lands him in the middle of the conflict.

Once again the story pulls you into the believable worlds so artfully drawn by Phillip Pullman. Adventure abounds, betrayal, heroic deeds, and dark conflicts drive the story forward.

The Amber Spyglass

The third book in the series draws the story to a satisfying end. Unlike some series, which seem to never end and leave you hanging at the end of each book in search of another sale, the Amber Spyglass reveals the mysteries alluded to throughout the story, and resolves the final conflict. But not before leading you through another set of breathtaking adventures, unforeseen turns, and an epic battle between good and evil.

I highly recommend this series to anyone over the age of 11 who enjoys excellent fantasy. This is a superior children's series that adults will also enjoy for its well-drawn characters, detailed worlds, and intricate plotting.

You can purchase The Golden Compass, The Subtle Knife and The Amber SpyGlass from B&N. Want to see your own review here? Just read the book review guidelines, then use Slashdot's handy submission form.

canadian_right writes: "Philip Pullman has written a great fantasy adventure that children and adults will enjoy. A richly detailed alternate universe is presented in The Golden Compass, and we are introduced to the heroine of the three books, Lyra Belacqua. The story starts off quickly and holds your interest with a series of engaging and imaginative adventures for the length of the three novels. Philip Pullman pulls you effortlessly into these alternate worlds, and holds your attention with a wealth of detail that brings to life the sights and sounds of these new worlds. Some worlds are just a bit different from our own, while others are completely new." Read on for his brief review of the books in this trilogy. The Golden Compass, The Subtle Knife, The Amber Spyglass author Philip Pullman pages (See each) publisher Knopf rating 8 reviewer canadian_right ISBN (See each) summary A trilogy written for kids but deep enough for adults to enjoy.

Lyra soon finds herself at the centre of world shaking events, but unlike so many fantasy books, Philip Pullman has come up with a series of astounding, interlocking adventures, full of wonders, creatures, and worlds that will keep you guessing for the full length of the trilogy. All the main characters in the three books are fully fleshed out, with distinct personalities and motivations. There is a fairly large cast of characters, but the author deftly weaves their stories together, often to great dramatic effect.

This trilogy is marketed as children's literature, but this is a much more intense series than Harry Potter is. Battles are deadly, not glorious; good people that you have come to care about die. Certain unfortunate events unfold with ruthless logic. Organised religion is presented in a very bad light, which will turn off some readers. I wouldn't recommend this series to children under 12, but I enthusiastically recommend His Dark Materials to anyone who enjoys fantasy.

The Golden Compass

Lyra is a resourceful and vivacious young girl who lives at Jordan College -- left there by her rich and powerful Uncle, Lord Asriel. Lyra lives a carefree life doing pretty much as she pleases, but she loves adventure and is continually getting into trouble. Then she overhears a conversation about Dust -- a strange substance mysteriously associated with people. Something about Dust is causing great consternation with the Church and other powerful people. At the same time the gobblers are stealing children. Soon Lyra is propelled into the midst of a great conspiracy that takes her far from the comforting halls of Jordan College, and face to face with terrible danger. Lyra's resourceful optimism makes you want her to succeed, and the world she travels through evokes the wonder of things new, and events unknown.

The action will keep children enthralled, and the imaginative twists and turns will surprise and delight adults and children alike. Various peoples and cultures are met throughout the story, and all find a part to play in the epic battle that builds up over all three books.

The Subtle Knife

The Subtle Knife starts off in our familiar world, and introduces a new character: Will. Will is much more serious than Lyra, but their fates are soon intertwined. Will has lived a much more troubled life looking after his mother after his father's disappearance. Someone badly wants something of his father's, and Will's efforts to protect it quickly lead him from home and entangle him in the events started in the Golden Compass. A great war is brewing and Will is destined to play a key role, along side Lyra, in this conflict. A weapon is discovered that will tilt the balance in this war, and Will's search for his father lands him in the middle of the conflict.

Once again the story pulls you into the believable worlds so artfully drawn by Phillip Pullman. Adventure abounds, betrayal, heroic deeds, and dark conflicts drive the story forward.

The Amber Spyglass

The third book in the series draws the story to a satisfying end. Unlike some series, which seem to never end and leave you hanging at the end of each book in search of another sale, the Amber Spyglass reveals the mysteries alluded to throughout the story, and resolves the final conflict. But not before leading you through another set of breathtaking adventures, unforeseen turns, and an epic battle between good and evil.

I highly recommend this series to anyone over the age of 11 who enjoys excellent fantasy. This is a superior children's series that adults will also enjoy for its well-drawn characters, detailed worlds, and intricate plotting.

You can purchase The Golden Compass, The Subtle Knife and The Amber SpyGlass from B&N. Want to see your own review here? Just read the book review guidelines, then use Slashdot's handy submission form.

Mark Welch writes: "'The MouseDriver Chronicles' chronicles a modestly successful startup whose mission was to build a product and sell it at a profit -- a concept that seemed almost obscene when the authors launched their new business in mid-1999.) I saw 'The MouseDriver Chronicles' in several bookstores, and passed because it sounded like it would be yet another story of dot-com failure. But finally I decided it looked like a 'fun read' and bought it, and I'm glad I did." Mark has a more complete review, and ChrisD adds his own reaction, below. The Mousedriver Chronicles author John Lusk, Kyle Harrison pages 244 publisher Perseus Publishing rating (See reviews) reviewer Matt Welch, then chrisd ISBN 0738205737 summary Blow-by-blow account of a high-tech startup; either great or awful according to the reviews below.

I'm adding The MouseDriver Chronicles as my number-two title (after Dot.Bomb, by by J. David Kuo) on my "must read" book list for entrepreneurs.

Dot.Bomb was more fun to read, in part because it was about a dot-com company that crashed and burned, and it's always more fun to write about failure than success.

Though The MouseDriver Chronicles isn't quite as fun to read, it is more useful for potential entrepreneurs. The book recounts many logistical and planning issues, in an exceptionally well-written style, using straightforward language and sharing more details (business and personal) than I'd expected (though the details seem to fade in the later chapters, presumably to protect the trade secrets of the continuing company).

Most important, The MouseDriver Chronicles is not about a crash-and-burn dot-com failure.

It's about a modestly successful startup whose mission was to build a product and sell it at a profit, a concept that seemed almost obscene when Lusk and Harrison launched their business in mid-1999. In January 2002, that concept (build a product and sell it at a profit) sounds much better, making the book more timely. Even if there are fewer entrepreneurs this year, they all should profit from reading The MouseDriver Chronicles.

The authors especially deserve credit for admitting how "ignorant" they were (in many respects) when they received their MBA degrees from Wharton, even after earlier careers working for consulting firms. They frankly disclose some embarrassing experiences, which should profit wise readers who may experience fewer mistakes as a result.

My main gripe with the book is that it ends before the end. I expected the final chapter to recount the company's failure, or its sale to a larger company, or some other "exit strategy" that would provide "closure" for the book.

Instead, the book's chronology ends in early 2001, but the company continues even today. Ending the book a year before it reached bookstores (in January 2002) seemed quite unfair (but that is the reality of the book-publishing industry).

Fortunately, the MouseDriver.com web site contains an archive of the author's "Insider" newsletter updates, so I could read "the rest of the story" (which is still unfolding, since the company is still plodding along).

Meanwhile slashdot author/editor chrisd has a different view:

I read an advance copy of The MouseDriver Chronicles (Hereafter referred to as TMD to save me from typing too much) and disliked it immensely. I'd been studiously avoiding writing a review of it as I take no joy from writing about how little I like something. However, since reader Mark Welch was kind enough to write a review (something we here at /. appreciate, thanks Mark!), I couldn't post it without giving my two cents.

As Mark noted, TMD is an enthusiastically, conversationally written book about the founding of a company to capitalize on a single idea. That idea is to make and market a mouse shaped like a Golf Club (Driver) head. While I'm not going to talk about carpal tunnel or repetitive stress injuries, I will say that this is a bad book if you want to be excited and have a view into what starting and running a company is like.

Basically, TMD is a book about two guys, one a former Wharton MBA student and the other an Andersen (not Arthur) Consulting guy who left their respective stations "to the disdain of their friends" to start their company making silly and painful looking mice. "To keep themselves motivated," they kept a diary which they somehow convinced Perseus to publish as this book.

I had to keep reminding myself while reading that this book is not about the product they are trying to sell, so much as about their experiences starting out. I really tried. The point of such a book is to live vicariously through the protagonists and learn something along the way. The only thing I learned was that they were very excited. I really don't want to know these guys, nor do business with them. (Not that they're knocking on the door to buy ads on OSDN, but I digress.) You'll learn very little about business and starting a company from this book. You'll also really not care much about what they do to sell thier product. There just doesn't seem to be much at stake.

They take some measure of pride in some of the "guerilla" marketing they chose to employ. Including crashing a benefit party at the SF metreon and sending "Personalized email (not spam) to publications and organizations that might take an interest in MouseDriver." Ugh.

The book isn't all bad. I mean, the writing isn't bad, much better than is usually seen in management books, and it flows pretty well. You don't pick up a book like this expecting Updike. It succeeds as the kind of book meant to be read while waiting at red lights. Also, it is clear that they see the book is just further promotion for their product and their company, something not usually so straightforward in this kind of book, so it's not crass in that manner.

But in the end, it's an empty book, devoid of useful content. Sort of like caffeine-free Diet Coke. Once you're done with it, all you know is that your glass is empty and your stomach has something in it. I mention this because this is not a cheap book; Barnes and Noble retails this book at $19, you can buy any number of nice things for $19.

Maybe if I was a golf nut this book might have been better.

How about this, if you want a scrappy startup book, go read defunct GO Corp CEO Jerry Kaplans book Start-up or if you want exhausting pacing, a Michael Lewis book -- you'll get more out of a chapter in either than from The MouseDriver Chronicles.

You can purchase The MouseDriver Chronicles from bn.com. Want to see your own review here? Just read the book review guidelines, then use Slashdot's handy submission form.

Peter Wayner writes: "A long time ago, I posed for a portrait at a church fair. The priest wandered by, paused for a second, and then caught up to me later. "Do you like the picture?" he asked. When I said it was fine, he told me, "Oh, I think its terrible. It doesn't look like you at all. But that doesn't matter. The artist is supposed to create a picture of what you think you look like." Read on to see what this has to do with robots as Peter reviews Rod Brook's new book. Flesh and Machines: How Robots Will Change Us author Rod Brooks pages 260 publisher Pantheon Books rating 8 reviewer Peter Wayner ISBN 0375420797 summary A charming look at an unconventional (and powerful) way to think about and design robots.

In a way, robots are portraits of humans. Machines are just machines and assembly lines are just assembly lines. The buckets of bolts don't become robots until they start to take on some of the characteristics and a few of the jobs of humans. A drill for tightening a bolt may replace a biceps, but it's just a motor until it's on the end of a fancy mechanical arm that positions it automatically. Then it's a robot ready for a call from central casting.

Defining just what is and is not a robot is not an easy job for technologists because the replicants and androids are a touchstone and a benchmark for measuring our progress toward the future. It's 2002 and everyone is asking: Where's mad Hal steering a space craft to oblivion? Or more importantly: Why am I still vacuuming the floors and mowing the lawn by myself?

If you are asking these questions, then you might want to read the answers Rod Brooks, the director of MIT's Artificial Intelligence Laboratory, offers in his charming book, Flesh and Machines: How Robots will Change Us. The book is half a thoughtful biography of the various robots created by his graduate students and half a philosophical explanation of what to expect from the gradual emergence of robot butlers.

The biographical part is probably the most enjoyable. He and his students have produced more than a dozen memorable robots who've crawled, rolled and paced their way around MIT. One searched for Coke cans to recycle, one tried to give tours to visitors, and another just tried to hold a conversation. Brooks spends time outlining how and why each machine can into being. The successes and more importantly the failures become the basis for creating a new benchmark for what machines can and can't do.

An ideal version of this book should include a DVD or a video cassette with pictures of the robots in action because the movement is surprisingly lifelike. Brooks is something of a celebrity because a film maker named Errol Morris made a droll, deadpan documentary that cut between four eccentric geniuses talking about their work. One guy sculpted topiary, one tamed lions, one studied naked mole rats, and the fourth was Rod Brooks, the man who made robots. Brooks minted the title for the film, Fast, Cheap and Out of Control, a phrase he uses to describe his philosophy for creating robots. The movie tried to suss out the essence of genius, but it makes a perfect counterpoint for the book by providing some visual evidence of Brooks' success.

One of the stars of the movie was a six-legged robot called Genghis, a collection of high-torque RC airplane servo motors that Brooks feels is the best or most fully-realized embodiment of this fast and cheap approach. The robot marches along with a surprisingly life-like gait chasing after the right kind of radiation to tickle the IR and pyro-electric sensors mounted on whiskers. If you've seen the film, it's hard to forget his gait.

Brooks says that the secret to the success of Genghis is that there is no secret. The book's appendix provides an essential exploration of the design, which is short and very simple. The soul of the machine has 57 neuron-like subroutines, or "augmented finite state machines" in academic speak. For instance, one of the AFSMs responsible for balance constantly checks the force on a motor. If it is less than 7, the AFSM does nothing and if it is greater than 11, the AFSM reduces the force by three. That's doesn't seem like very much intelligence be it artificial or real, but 57 neuron-like subroutines like this are all it takes to create a fairly good imitation of a cockroach.

Brooks calls this a "subsumption architecture" and the book is most successful describing the days that he spent with his graduate students building robots and seeing what the architecture and a handful of AFSMs could do. He half mocks the roboticists who load up their machines with big computers trying to compute complex models of the world and all that is in it. In his eyes, the lumbering old-school machines just move a few inches and then devote a gazillion cycles to creating a detailed, digital description of every plant, brick or wayward child in the field of view. After a few more gazillion cycles, the machine chooses a path and moves a few more inches. Even when they find their way, time passes them by.

There are no complex control mechanisms sucking down cycles on the machines from Brooks' lab, the source of the claim that they're "out of control". It's just AFSMs wired together. One of the robots fakes human interaction by tracking fast motion and flesh colored pixels. Brooks marvels at how a few simple rules can produce a machine that is remarkably life-like. If you're not sure, they have video tapes of lab visitors holding conversations with the machine, who apparently takes part in the conversation with the patient interest of a well-bred host. As if by magic, the AFSMs are creating enough human-like movement and visitor in the tape begins treating the robot like a human!

If you're still not sure, you might buy a "My Real Baby" doll designed by Brooks with the help of the adept mechanical geniuses in Taiwan. The story of taking a highbrow concept from MIT to the local toy store is a great part of the book. The so-called toy is filled with AFSMs that tell it when to gurgle, when to pout, when to sleep, and when to demand sustenance. Alas, the toy makers tell Brooks that the market can't stomach so much innovation. One new thing at a time.

So are these machines truly successful simulacra? Are they infused with enough of the human condition to qualify as the science-fiction-grade robots or are they just cute parlor tricks? Some readers will probably point to the AFSMs and scoff. Seeing the code is like learning the secret to a magic trick.

Brooks, on the other hand, is sure that these machines are on the right track. In a sense, he makes it easier for his robots to catch up with humans by lowering the bar. On the back of the book, Brooks ladles out the schmaltz and proclaims, "We are machines, as are our spouses, our children and our dogs... I believe myself and my children all to be mere machines." That is, we're all just a slightly more involved collection of simple neurons that don't do much more than the balance mechanism of Genghis. You may think that you're deeply in love with the City of Florence, the ideal of democratic discourse, that raven-haired beauty three rows up, puppy dogs, or rainy nights cuddled under warm blankets, but according to the Brooks paradigm, you're just a bunch of AFSMs passing numbers back and forth.

If you think this extreme position means he's a few AFSMs short of a robot professor though, don't worry. Brooks backs away from this characterization when he takes on some of the bigger questions of what it means to be a human and what it means to be a machine. The latter part of the book focuses on what we can and can't do with artificial intelligence. He is very much a realist with the ability to admit what is working and what is failing. His machines definitely capture a spark, he notes, but they also fall short.

He notes with some chagrin that his robot lawnmower leaves behind tufts of uncut grass. Why? It uses a subsumption-like algorithm that doesn't bother creating a model of the yard. The robot just bounces around until the battery runs out. Eventually the laws of random chance mean that every blade should be snipped, but the batteries aren't strong enough to reach that point at infinity. A model might help prevent random lapses, but that still won't solve the problem. Alas, the machines themselves are limited by the lack of precision. One degree of error quickly turns into several feet by the other end of the yard. A robot wouldn't be able to follow a plan, even if it could compute one.

What's missing, Brooks decides, is some secret sauce he calls "the juice". Computation and AFSMs may work with cockroaches, but we need something more to get to the next level. Faster computers can do much more, but eventually we see through the mechanism. Genghis looks cool, but learning about the 57 AFSMs spoils the trick.

The standard criticism of Brooks' machines is that they don't scale. There is no superglue juice that can save a scaffolding built of toothpicks. The AFSM may produce good cockroaches, but that's just the beginning of the game. Humans are more than that. Eventually, the AFSMs become too unwieldy to be a stable programming paradigm. In fact, Brooks sort of agrees with this premise when he suggests that Genghis is his "most satisfying robot." It was also one of the first. The later models with more AFSMs just don't rank.

But humans and other living creatures don't scale either. We may be able to run 20 miles per hour, but only for 100 yards. We may be able to troll for flames on five bulletin boards, but eventually we get our pseudonyms confused. Limits are part of life and we only survive by forgiving them. To some extent, the lifelike qualities of his robots are direct results of the self-imposed limits of the AFSMs.

Your reaction to these machines will largely depend upon how many of the limits you are willing to forgive. Stern taskmasters may never be happy with a so-called robot, but a relaxed fellow traveller may ignore enough of the glitches to interface successfully. Some will see enough of themselves to be happy with the whirring gizmos as a portrait of human and others may never find what they're looking for. That's just the nature of portraits. For me, this book is an excellent portrait of a research program and the collection of questions it tried to answer. You may look in the mirror and want something different, but it's worth taking a look at these machines.

Peter Wayner is the author of two books appearing this spring: the second edition of Disappearing Cryptography , a book about steganography, and Translucent Databases , a book about adding extra security to databases. You can purchase Flesh and Machines from Barnes & Noble. Want to see your own review here? Just read the book review guidelines, then use Slashdot's handy submission form.

danny writes: "'Free as in Freedom: Richard Stallman's Crusade for Free Software' is an insightful biography of a figure whose mere name tends to start flame wars on Slashdot ..." Stallman may be one of the most interesting people alive right now: read on to see how well the biography is up to the task of describing him and his movement -- acccording to Danny, that may depend on the reader. Free as in Freedom: Richard Stallman's Crusade author Sam Williams pages 225 publisher O'Reilly rating 9 reviewer Danny Yee ISBN 0-596-00287-4 summary Life of Stallman

Free as in Freedom is a generally sympathetic but far from hagiographic biography of Richard Stallman, inspiration of the free software movement. While much of the material in it will be familiar to anyone actively involved with free software, there are, as Williams claims, "facts and quotes in here that one won't find in any Slashdot story or Google search." It is also an entertaining and accessible study, which I finished within a day of my review copy arriving.

Williams begins with the famous jamming printer and Stallman's encounter with a non-disclosure agreement that prevented him writing reporting software for it. He then jumps forwards to a speech given by Stallman in 2001, responding to attacks by Microsoft on the GNU GPL. Having used these episodes to introduce Stallman and explain the basic idea of free software, the rest of the work continues in a similar vein, mixing historical chapters with ones describing Williams' own meetings with Stallman.

Chapter three describes Stallman's childhood as a prodigy; chapter four his experiences at Harvard and MIT; chapter six the MIT AI Lab and the Emacs "commune"; chapter seven the death of the MIT hacker community and the first announcement of the GNU Project; chapter nine the GNU GPL; chapter ten the appearance of Linux and debates over GNU/Linux; and chapter eleven the coining of the term "open source" and the arguments over that. These contain quotes by everyone from Stallman's mother to the leading lights of free software, as well as plenty by Stallman himself. The narrative never strays too far from its subject, but becomes inextricably interwoven with the broader history and politics of free software and sometimes digresses to cover key figures and events with which Stallman wasn't directly involved.

Williams' first-hand accounts help give Stallman a human face: chapter five recounts a meeting in 1999 LinuxWorld, chapter eight a meeting in Hawaii, and chapter twelve a frustrating car trip with Stallman at the wheel. These give a feel for Stallman's personality and presence, his forthrightness and emotional intensity, his steadfastness and his abrasiveness, and his ability to unsettle. Chapter thirteen attempts to predict Stallman's status "in 100 years," quoting opinions from from Eben Moglen, John Gilmore, Eric Raymond, and Lawrence Lessig; it also suggests that Stallman's personality may be inseparable from his achievements.

Although I was already involved with free software advocacy, my first encounter with Richard Stallman came when he turned up to a rehearsal of my gamelan group; afterwards I tried without much success to explain to my fellow musicians just how important the strange bearded man they'd just met was. I don't think Free as in Freedom would help much with that: it jumps around too much and assumes too much general knowledge of the computer industry to be a good introduction for complete outsiders. Those already interested in the history and politics of free software and hacker culture, however, should relish it.

In an epilogue Williams talks about the writing of Free as in Freedom and the choice of copyright license. Despite the big fuss made about it being released under the GNU Free Documentation License, however, only a sample chapter is available online now and the rest will not, apparently, be put online until June. (This is not a violation of the OFDL, because Williams as copyright holder can allow O'Reilly to distribute the book in any way they like.) So if you don't want to buy a printed copy, you can either wait three months or hope someone OCRs the book sooner.

You can purchase Free as in Freedom from Barnes & Noble, read chapter three online, or check out Danny's 600 other book reviews. Want to see your own review here? Just read the book review guidelines, then use Slashdot's handy submission form.

Amy Rich writes: "If you're are, or want to be, a professional sysadmin, buy this book! I've been doing UNIX system administration for nearly ten years now, and I've never seen another book like this on the market. Limoncelli and Hogan do a fantastic job of describing the 'whys' behind many of the best practices in the systems and network administrator world. I wish this book had been around when I started out; it would have saved so many headaches as I 'learned the hard way.' Read on (below) for the reasons Amy is so enthusiastic about this book, and to see if it might fit your situation. The Practice of System and Network Administration author Thomas A. Limoncelli and Christine Hogan pages 773 publisher Addison Wesley rating 9.5 reviewer Amy Rich ISBN 0-201-70271-1 summary Fantastic high level book about successfully administrating computer systems and networks. Learn the best practices of the pros, developed through years of trial and error.

Though not a nitty gritty technical book, this volume is a must have for every professional sysadmin, regardless of skill level or the technology she uses. The book focuses on the methods used by successful system administrators to build, support, and grow their networks. For the novice admin, it offers a good big-picture look at the most important "whys" of system administration. For the intermediate admin, it has great advice on how to balance fire fighting with project work that will help strengthen the infrastructure and lead to less emergency handling. For the senior admin, there are gems of design wisdom and sections on how to deal with being in a managerial or team leader role. Because it's more high level, this book is even a good buy for people who manage sysadmins but are not themselves technical.

What's Covered

The book is broken down into four major parts, The Principles, The Processes, The Practices, and Management. The chapters in each section are conveniently split into the "basics," the "icing" (things to concentrate on after all of the basics have been accomplished), and some exercises at the end to help the reader apply the covered information to her own situation. The authors back up their sound advice with many case studies and, often tragically humorous, war stories that really drive home the salient points. The BOFHs among us will certainly love some of the follies that the book recounts.

The Principles

This chapter deals with fundamental issues sysadmins encounter and how to define a site-wide infrastructure. The topics range from desktop and server setup, to security, debugging, and ethics. Of particular interest to me were the latter three. I was hoping that the security section would give a bit more detail about a layered security approach as part of the policy. The authors offered good pointers on developing a site security policy without going into specifics, though. The debugging section was spot on, and something that even your help desk people should read. Instead of the hit-or-miss technique that so many inexperienced people use to diagnose problems, this gave a thorough outline of how to methodically determine and fix a problem. In light of the current Enron fiasco, the ethics section was quite timely. How do you do the right thing (or even determine what that is) and then not get stuck as the scapegoat? Though they're not lawyers, Limoncelli and Hogan offer some sound advice and quote from the SAGE Code of Ethics.

The Processes

This section entails how to create the framework for making successful changes to your infrastructure. Topic highlights include change management and revision control, server upgrades, maintenance windows, and service conversions. Change management is one of the most perilously neglected portions of the system administration field today. How should changes be made to the systems so that they are as seamless as possible? Who changed what, when? How do you get back to a known state? My one nit is that I would have liked to see a bit more about automation (rsync, cfengine, et al) discussed in this chapter, especially in dealing with upgrades and service conversions.

The Practices

The authors choose a few important services to discuss in detail here:

• The helpdesk
• Customer care
• Data centers
• Networks
• Email service
• Print service
• Data recovery
• Remote access
• Software depots
• Service monitoring

These topics were well covered, but the one omission from this section was web service (and possibly a section on Usenet, though that's waning in popularity these days). The namesapces chapter from the Principles section would have also flowed better as part of a DNS chapter in this section. One especially amusing story in the monitoring chapter describes an alarm system in a machine room calling the on-duty sysadmin in the wee hours of the morning to tell him, in a sultry female voice, I'm hot. I'm wet. Too bad his wife answers and thinks it's a prank call when it's really a broken HVAC system!

Management

This section covers how to best deal with the human side of system administration and really explores how people can actually like their jobs instead of just slogging through them every day. There's some outstanding advice on how to deal with difficult situations (time management, difficult people, professional development, keeping people motivated and managing them well, etc). This is also the first book that I know of that includes salary negotiating tips for sysadmins. The management section could almost stand alone as a book geared towards the particular problems that many sysadmins experience.

Other bits

Unlike most other books, the introduction and the appendices are also very worthwhile reads. The introduction covers the three fundamental things that ever site should already be doing: using a ticketing system, handling quick requests right, and starting every host in a known state. The first two appendices cover the various hats that sysadmins wear and "what to do when..." situations. The latter is extremely valuable, and is also available from the book's web site.

In all, this book receives an enthusiastic thumbs up!"

You can purchase The Practice of System and Network Administration from bn.com. Want to see your own review here? Just read the book review guidelines, then use Slashdot's handy submission form.

ctar writes: "Following is my review of O'Reilly's new book : "T1: A Survival Guide" by Matthew S. Gast. The short and sweet is, this book definitely fell short of my expectations." Read on to see what ctar found lacking, and a few bright spots as well. T1: A Survival Guide author Matthew S. Gast. pages 263 publisher O'Reilly and Associates rating 6 reviewer ctar ISBN 0-596-00127-4 summary A potentially useful but disappointing book; skimps on the details that a book for T1 administrators should be full of.

What a great age we live in, where you can teach YOURSELF your entire profession! As a self-taught network engineer with a major market data firm, I have great respect for some of today's tech writers who have single handedly taught me TCP/IP, Ethernet, Cisco routers, and Linux! The only aspect of my job for which I have had to rely solely on experience, (and the meager amount of information on the web) is T1s and synchronous circuits/leased lines. As far as I know, the only books which discussed the technical details of T1 and synchronous circuits are general telecommuncations text books. None are written from a contemporary network administrator's point of view. So, you understand my excitement at seeing O'Reilly take a stab at just such a book!

The book starts off at a good pace, talking about the history of the telephone network and its evolution into the digital age (the reason we have T1 available as a data service). It discusses the different terminology related to T1's, and the equipment that connects them to our routers, but makes very few analogies or examples to solidify the relationship of these terms to each other or to the big picture of networking. After discussing the physical and logical layout of T1 and its physical interface with our routers, Gast spends the next 40 pages on the nitty gritty details of T1: Timing, Framing, Coding, and the lights on the CSU/DSU. All the important aspects of T1 are discussed in a logical order. Unfortunately, it's not enough; Gast breezes through the most important and mysterious aspects of T1 without so much as one good analogy or explanation to develop the ideas. The diagrams are equally disappointing. They have a lot of information, but do little to clarify the subject matter. The T1 framing sections, especially did not get enough attention. This is the heart of T1, and really wasn't explained well enough.

After getting what seemed to be an introduction to the subject matter, I expected the rest of the book to go into further detail about the intricacies of T1 framing and coding, and ways to hash out possible problems on T1 circuits. Instead, the next 60 pages give the boring and useless details of the three most common link-layer protocols run over T1s: HDLC, PPP, and Frame Relay. Gast continues to litter the pages with confusing and uninformative diagrams, and then spends time explaining the details of each one step-by-step. Good diagrams don't need step-by-step explanation; they speak for themselves!

The level of detail he goes into for each of these protocols is similar to what you might find in a general Data Networking text. He discusses different principles of data communication as well as the specific frame formats of these protocols, but doesn't explain how these protocols specifically interact with T1. Although he gives the frame formats of these different WAN protocols, he doesn't give enough information or suggestions on using the information in any effective way. The oversimplification of many of the diagrams makes the book less useful than the RFCs which will give you the exact frame formats.

Gast assumes that if you don't work for one of the telcos, the only way you may come across a T1 is as a small business network administrator responsible for maintaining internet access via T1. That is not the case anymore; many large companies manage their own backbone and have access to leased lines, and T1 testers. The only time a T1 tester is mentioned, it's described as 'a handheld device with lots of buttons and blinking lights on it.' The principles behind T1 testing are quickly covered, but the intricacies of testing T1s and using T1 testers are not. This is unfortunate, as many Cisco routers have built in test pattern generation and loopback capabilities! (As do most standalone CSU/DSUs.)

It's obvious, as it is in many poorly written tech books, that the author knows his subject! The problem is, he doesn't consider the fact that we, the reader, may not. The book wasn't a complete waste of time; there is a lot of good information in here. Information on signaling and different types of alarms on T1s is present. The majority of it is just not explained very well, and too much time is spent on the link-layer protocols. I probably wouldn't be so down on this book if it didn't have O'Reilly's name on it.

You can purchase T1: A Survival Guide from bn.com. Want to see your own review here? Just read the book review guidelines, then use Slashdot's handy submission form.

Reader Mike N. contributed this review of The Mystery Of Capital: Why Capitalism Triumphs in the West and Fails Everywhere Else. Hernando de Soto, for those unfamiliar, is an interesting character in his own right.

The Mystery of Capital author Hernado de Soto pages 276 publisher Basic Books rating 8.5 reviewer Mike N ISBN 0465016146 summary A take on the abstraction of 'Capital' We read about the new economy, cyber-squatting, e-cash, intellectual property, and the Wild West on the internet. How can we intelligently consider these concepts if we are unclear about what the old economy, or cash, or physical property (let alone the real Wild West) is?

Hernado de Soto addresses the latter questions while making the case for his central thesis: that Western property law and administrative infrastructure is the reason for the ascendency of the Western economy.

The book is framed as an investigation of the 'Five Mysteries of Capital' during which the author enthusiastically demonstrates the shortcomings of common knowledge on the subjects of poverty, money, law, and history.

De Soto's mysteries are, in short:

1. The Mystery of Missing Information. How much poverty, and conversely, how much property is there in poor countries, and how do we measure it? Huge numbers of people live and work off the books: they have no clear title to their land and possessions, they pay no taxes, they have no credit. We're not talking about subsistence farming here, but about buses and taxis, repair shops, and light industry. This 'Shadow Economy' is explored, and the 'Dark Capital' bound to undocumented resources is examined.

2. The Mystery of Capital. What is Capital, where does it come from? De Soto views capital as not just a proxy for physical assets, but as a side effect of of property laws and infrastructure. His explanation of capital amplification derived from the standardization, globality, and liquidity that is given to property by standard protocols and infrastructure echoes common reflections on the internet phenomenon.

3. The Mystery of Political Awareness. Why have so many governments failed so badly at economic reform? Simply because they do not realize they are in the midst of their own Industrial Revolution, 200 years late. De Soto argues that the true extent of the shadow economy was unknown until recently, and methods of dealing with it are in process. It is refreshing to read something on this subject that acknowledges the hard work and sincerity of many of these governments, rather than rehashing accusations of incompetence and corruption.

   4. The Missing Lessons of U.S. History. How did the U.S develop an infrastructure that nurtures successful Capitalism? This section is an entertaining overview of the evolution of U.S. property law (believe it or not). What I found interesting was the way that 'law' would spontaneously arise in circumstances where the existing system was inadequate or non-existent. Also of interest were the examples of legislation chasing and converging (roughly) with reality over a century long period.

   5. The Mystery of Legal Failure. What legislation is required to = enfranchise the people of the Third World? Again, the author makes an argument for law tracking reality. In the Roman legal tradition, laws are not created, they are 'discovered'; the best laws are those that fit existing practice. Well intentioned land reform measures fail because they do not reflect the actual situation. People do not want to be uprooted, they want title to what they believe is theirs.

If anyone believes the answer to any these questions is either simple or boring, they are mistaken. De Soto addresses topics such as the nature of cash, the importance of responsibility, and the impregnability of badly designed bureaucracies in the course of his arguments. An especially harrowing read is his description of research detailing the steps required to get title to property in Haiti, the Philippines, and several other countries. Ith can take decades (decades!) and hundreds of transactions with dozens of bureaucracies to get clear title to land that a family may have lived on for generations.

De Soto tells a story about walking through rice paddies in Indonesia - = there were no survey markers or fences, but he knew whenever he crossed a property line - a different dog barked at him. He tells a group of ministers working on land reform to start at the bottom; listen to the dogs. and work up from there. His message is simple -- discover the law, then write it.

In each of these sections the author firms up his arguments with a = unique perspective based on solid research as much as theory. The final section of the book gives sober and well thought out step-by-step directions to lift people out of poverty and invisibility, again based on experience in field programs, rather than ideology.

This book is infused with a sort of passion that gives the arguments and figures an unexpected fascination. It is neither an anti-globaliztion rail nor a 'greed is good' apologia, but a well thought out investigation into a subject the author cares deeply about. For myself, I care little for economics, but I am familiar with engineering. De Soto approaches his topic like an engineer; he is interested not in promoting a theory, but in solving a problem.

I would recommend this book to two audiences: anyone interested in world poverty or economics, or those interested in the interaction and evolution of laws (ill-informed or not) and the Web. I would also recommend that we start barking.

You may find out more about the author at www.ild.org.pe.

You can purchase The Mystery of Capitalism from bn.com. Slashdot welcomes readers' book reviews. To see your own review here, carefully read the book review guidelines, then visit the submission page.