Slashdot Mirror

An anonymous reader writes: The Atlantic has a story with some video of a traffic simulator showing just how the roads can be jammed up by people looking for a place to park. (You can play with the simulator too.) This has been suspected for a long time by many traffic researchers and city planners, but the simulator shows just how quickly the roads jam up after just a few of the blocks fill up with parked cars. The good news is that autonomous cars don't need to park-- they just go give someone else a ride. They could change city life forever.

theodp writes "It was the best of movies; it was the worst of movies. GeekWire reports that The Internship — the new comedy starring Vince Vaughn and Owen Wilson as two 40-something guys who get internships at Google — is getting high praise from Googlers but low marks from movie critics. Google CEO Larry Page called the movie 'a lot of fun' in his Google+ post, while fellow Google exec Vic Gundotra gushed, 'I laughed a lot while watching this movie!' After screening a sneak preview with Google companions, Wired's Steven Levy wrote, 'From Google's point of view, the movie could not possibly be better.' USA Today's take, on the other hand, is that 'Google has never looked lamer thanks to The Internship.' And the NY Daily News calls the movie 'an unfunny valentine to Google.' But perhaps the unkindest cut of all comes from the NY Post, who suggests that 'maybe The Internship was secretly funded by Bing.' Ouch." Update: 06/07 20:02 GMT by T : Peter Wayner saw the movie (a "harmless bit of summer fluff"), and his full-length take below takes on some of the tech-company misconceptions that the film-makers gleefully adopted as script material. While there have been a handful of movies about hacking (“War Games”, “Hackers”) and every heist movie seems to stick at least one programmer on the team, there are few films devoted to craft of building software. Who would want to spend two hours staring at beautiful actors stuck in cubicles staring at lines of code? “The Internship”, thankfully, isn’t that movie, although it is set at Google’s mothership where the average day is filled with days staring at lines of code. It’s a harmless bit of summer fluff that sails blithely along in its own carefully edited version of reality pretending that building software is anything but staring at screens. It’s a nice journey to a happy ending with only a few veiled hints of darker trends and deeper issues buried underneath the fun.

The movie is a buddy comedy pairing Owen Wilson and Vince Vaughn, the dynamic duo who were last seen together in “The Wedding Crashers” as fast-talking scammers sneaking into receptions. This time, they’re washed up watch salesmen fast-talking their way into a job at Google. Someone finally noticed that mobile phones took over the job of telling time. The Hollywood executives who develop movies with lambda expressions probably called it “The Google Crashers.”

The two actors are likeable rogues that are playing the same game. They may be older but they understand people, unlike the nerds at the Googleplex. They’ve got an answer for everything and that answer is usually something that will keep them afloat in the rapidly changing economy. It’s sort of “Glengarry Glen Ross” or “Death of a Salesman” without the adultery or the kind of lefty talk that attracts the attention of the House Un-American Activities Committee.

For them, Google is the promised land, the Emerald City, the Big Rock Candy Mountain, a role that the company plays happily, almost too happily. The company reportedly traded access to the Googleplex for some control of the script and they reportedly wielded this knife to slice away a scene showing a crash of their now famous self-driving cars. Claire Cain Miller at the NY Times reported that the company even created the credits and packed them full of ads for Google’s famous and not-so-famous products. There’s only a bit of irony in the way that the company that once made its name by creating tasteful, small and very focused ads could put its name on such an endless, loud and extravagant act of branding.

Naturally, the list of which Google features makes the closing credits is highly selective. There’s no mention of the direct link that the US Government claims to have to Google’s huge files on all of us or any discussion of the ongoing morass of the lawsuit from the book authors. There is also no questioning of Google’s vision of the social compact where you and I do the work of creating the content and they enjoy the fruits of the advertising that pays for most of the luxuries seen in the movie. It’s not “Enemy of the State” and certainly not “Office Space.” The pro-business crowd that is always asking Hollywood for some good corporate characters has finally gotten its wish.

But Slashdot readers will be a bit disappointed because the Google shown in the movie is just another company from central casting. There are occasional references to HTML5, CSS3 and “building an app” but most of the audience will walk away thinking that answer to creating software is eating pizza, going to a strip club, or drinking alcohol. Just as Hollywood injected scenes of drunken programming into “The Social Network”, Hollywood can’t seem to believe that software is made with logic, precision and concentration. The secret of success, at least according to the movie, is the same as the secret to diabetes: plenty of carbs and plenty of alcohol.

It may be too much to expect Hollywood to confront some of the deeper issues about Google’s work place because the movie is a comedy, not a remake of “Norma Rae”. The characters make a brief reference the downside and the brutal, winner-take-all game that they’re playing. 95% of the interns won’t get a paying job and most people who get paying jobs won’t get stock options worth very much. It’s like “The Hunger Games” but played for laughs.

Sitting around moaning about the way that Google (and the Internet) is destroying so many jobs wouldn’t make for a fun movie. Instead the characters revel in the free food and the non-stop buffet without recognizing that the benefits are a bit of a clever trap. Feeding someone $20 in food is a good deal if it keeps them working for three to six more hours.

The script writers apparently didn’t get the memo that the company has slowly been cutting back on the fancy extras. In 2008, the IPO millionaires boosted the cost of day care so high that there was open sobbing from the post-IPO engineers who couldn’t afford it. While many outsiders think movies like this are accurate, insiders complain that they can’t afford the day care which costs thousands of dollars per kid per month. It’s a not-so-subtle message that kids are a high cost that get in the way of software development.

And then in 2009 Google started clamping down on the free food, especially the clever employees who would take home big containers of food on Friday to make it through the weekend without a trip to the office. Larry Page told reporters at a news conference then, “I think it’s important to reset the culture from time to time. we decided to, for example, we significantly cut down all the snacks that had been available.” This new version made the film because Vaughn learns, to his chagrin, that he can’t take home the seven bagels he got for free. Once again, the food is just a carrot to keep people in front of the screens.

The movie certainly suggests that Google, like “Logan’s Run”, is filled with 20-somethings on an extended summer camp sleepover with fat salaries to make it even more fun. One of the managers is said to be 23 and already seasoned because he’s spent 4 years with the company.

Is this really accurate or just another bit of Hollywood frosting on the free cookie? Alas, Google has endured at least one high-profile age discrimination lawsuit from a manager who lost millions in stock options after being fired. The ex-employee’s lawyers dug up incriminating emails saying, among other things, that the guy was an “old man”, an “old guy” and an “old fuddy-duddy”. That attitude is heard again and again here although with less precision.

When I’ve spoken with people who’ve worked there, they have cautiously suggested that age discrimination is a real issue, especially to anyone who grows up, has kids, and starts working shorter hours. Somehow, the older folks seem to get replaced by someone who is young. Then, when their contract ends, they’re given a “severance deal” that effectively buys their silence. They’ll only mention the issue of age discrimination in bars far away from any Glassholes wearing Google Glass recording everything.

Still, this view doesn’t jibe with my experiences. Many of the people I’ve met at Google are older and some even sport grey beards. The engineering teams and some of the development teams are run by seasoned veterans with years of experience in the valley. For every 22 year old twerp in the movie, I’ve met some 40-somethings who know a thing or two and work at Google.

Indeed, the founders of Google are now about as old as Vaughn and Wilson. Larry Page turned 40 on March 26th and Sergey Brin joins him on August 21st. Long ago, the founders joked that their first corporate jet was going to be a “party plane” with king-sized beds, but today they are married and live in the suburbs. One equally old Googler told me about how touched he was to have one of the founders roll up to a party in a Honda Odyssey driven by the founder, not a robot. In other words, they were very normal, they just happened to have plenty of money.

This fiction that Silicon Valley is powered by youth is an old game played by Silicon Valley. Almost every startup run by a teenage sensation has a greyhaired venture capitalist pulling the puppet strings. Arthur Rock, Mike Markkula and Andy Grove put up plenty of money to fund Apple Computer but somehow the story was always about Jobs and Wozniak. In most cases, the youth are run ragged on the hamster wheels with stock options dangled in front of them.

It’s a nice story that sells so well that Google and Vince Vaughn decided to repackage it as a movie. The kids do okay. They get fancy meals and decent salaries. But the movie doesn’t want to spend too much time dwelling upon the accuracy of this fiction. Just as Alfred Hitchcock said, “For me, the cinema is not a slice of life, but a piece of cake.” This movie takes that aphorism and improves it by making the cake free. If only life were that simple.

Bio: Peter Wayner is the author of more than dozen books and his latest are a history of "Death of a Salesman" and a forward-looking exploration of the impact of the self-driving car.

WrongSizeGlass writes "A team of computer scientists at two University of California campuses has been looking deeply into the nature of spam, and they think found a 'choke point' [PDF] that could greatly reduce the flow of spam. It turned out that 95 percent of the credit card transactions for the spam-advertised drugs and herbal remedies they bought were handled by just three financial companies — one based in Azerbaijan, one in Denmark and one in Nevis, in the West Indies. If a handful of companies like these refused to authorize online credit card payments to the merchants, 'you'd cut off the money that supports the entire spam enterprise,' said one of the scientists." Frequent Slashdot contributor (and author of a book on Digital Cash) Peter Wayner wonders if "the way to get a business shut down is to send out a couple billion spam messages in its name."

An anonymous reader writes "New York magazine has a story about some of the flashy new ideas that are coming out of the labs of the New York Times. The piece prompted Peter Wayner to dig up some of the old Java applets he wrote to explore whether more promiscuity really stops AIDS and whether baseball can do anything to speed up the games. He notes that these took a great deal of work to produce and it's not possible to do them on a daily basis. Furthermore, they're cranky and fragile, perhaps thanks to Java. Are cool, interactive features the future of journalism on the web? Or will simple ASCII text continue to be the most efficient way for us to mingle our thoughts, especially when ASCII text won't generate a classloading error?"

An anonymous reader writes "New York magazine has a story about some of the flashy new ideas that are coming out of the labs of the New York Times. The piece prompted Peter Wayner to dig up some of the old Java applets he wrote to explore whether more promiscuity really stops AIDS and whether baseball can do anything to speed up the games. He notes that these took a great deal of work to produce and it's not possible to do them on a daily basis. Furthermore, they're cranky and fragile, perhaps thanks to Java. Are cool, interactive features the future of journalism on the web? Or will simple ASCII text continue to be the most efficient way for us to mingle our thoughts, especially when ASCII text won't generate a classloading error?"

An anonymous reader writes "New York magazine has a story about some of the flashy new ideas that are coming out of the labs of the New York Times. The piece prompted Peter Wayner to dig up some of the old Java applets he wrote to explore whether more promiscuity really stops AIDS and whether baseball can do anything to speed up the games. He notes that these took a great deal of work to produce and it's not possible to do them on a daily basis. Furthermore, they're cranky and fragile, perhaps thanks to Java. Are cool, interactive features the future of journalism on the web? Or will simple ASCII text continue to be the most efficient way for us to mingle our thoughts, especially when ASCII text won't generate a classloading error?"

peterwayner writes "If you're jazzed by the communitarian impulses driving Wikis, idea agora, Web 2.0 and other collaborative happenings, you'll be pleased to know that the new book Wikinomics is a great gift for that boss, spouse, or friend who doesn't quite grok it yet. The only logic bomb hidden in this statement is that much of what is wonderful in this book is wonderful because it's a book printed on pulp and written by two and only two authors. That is, the book is good because it's not a wiki." Read the rest of Peter's review. Wikinomics: How Mass Collaboration Changes Everything author Don Tapscott, Anthony D. Williams pages 320 publisher Penguin Group rating 8 reviewer Peter Wayner ISBN 1591841380 summary The pros and cons of wikis and their place in business

This statement isn't exactly true. The authors, Don Tapscott and Anthony Williams, have a wiki site at www.wikinomics.com devoted to the book. You can edit the wiki and have your say, but that's not what they're asking folks to buy. For the price of the book, you get a well-designed collection of thoughtful anecdotes stitched together by two talented business writers and polished by a good editor. They've made a good attempt to cover most aspects of the topic and they do an excellent job of explaining why the ideas are important for CEOs that are struggling to move their business forward. All of this is almost as portable as an iPod , dramatically less expensive and guaranteed never to need new batteries.

The tone of the book is bright and optimistic about how openness and wiki principles will help companies. We hear about how the wikipedia covered the London subway explosions, the way that Innocentive is opening up the R&D process for companies and the surprising inventiveness of Google maps users. The descriptions are thorough and well-researched, as far as they go, and when they're done going, the writers summarize them well. It's clear that the writers feel that the word "wikis" should be the new one word answer that CEOs should trot out when faced with the kind an impossible question, the kind of question that they the answered with "Internet" during the 1990s and "China" after the turn of the millenium.

The great advantages of the pulp-bound book become clear as you work your way through the text. In one section, for instance, Tapscott and Williams dismiss Jaron Lanier's worry that wikis can devolve when a smart mob develops the the same kind of "mass stupidity" that brought us Pol Pot or the Stalinist movement. "The winners will outnumber the losers", say the authors and conclude that Lanier "ran afoul". I don't really agree with the easy way that they dismissed the danger and if I had a wiki edit button in front of me, I would change the text to amplify Lanier's warnings. I've watched the mob rule delete perfectly good information from the wikipedia for no other reason than it wasn't "notable". The revision wars are legendary and any savvy wiki reader knows that skirmishes are more common than we would like. The well-meaning editors at the Wikipedia have probably destroyed more knowledge in the name of notability than the book burners of history. At least it's still there in the article history. But since Tapscott and Williams wrote a book that doesn't come with a wiki edit button, the text is better off because I didn't glue in my own divergent rant.

The optimism of the book is contagious and it would be a shame for it to be limited by a neutral point of view. Wikis organize casual information like how to install software, and this is the kind of job that is very important to business. Wikis may just be the wrong tool for, say, capturing political truthiness, but the book gives several good examples of how they energize corporations by making it easier for divisions, groups, and project teams to cooperate without going through traditional channels. If a business wants to formalize its collective intelligence, a wiki offers an ideal amount of flexibility.

If the book needs any editing, it would be to add more skepticism. At the beginning, they hint that they will address the kind of concerns that led Bill Gates to wonder about how society will pay for innovation if there's no profit incentive, but analyzing the limitations of the wikiworld isn't really their goal. There's little discussion of endeavors that have largely failed like Wikinews. That experiment with collaborative reporting had two articles on the day I wrote this and one article on the day before. (December 19 and 20th).

I've begun to feel lately that there is a real danger that free information will drive out paid information in much the same way that economists note that cheap money drives out the dear.

It's probably too early for us to have a firm grasp on the downsides to the wiki world and so it might be unfair to expect the book to be much of a buzz kill. One of the biggest logical problems I've found with the wikipedia is the inconsistent way that the movement treats traditional scholarship. On one hand, we're supposed to revel in the way that the wikipedia is often better than traditional mechanisms, but on the other hand the wikipedia gives more weight to outside sources. On the day I wrote this, the guide counseled, "Avoid weasel words such as, `Some people say ...' Instead, make your writing verifiable: find a specific person or group who holds that opinion and give a citation to a reputable publication in which they express that opinion." If the wikis become good enough to rival if not replace original sources, where will the wikis find the outside beacons of authority? Any strict logician will realize that there's a danger of proving 1=0 with this system, although I realize that all grown ups know that life is filled with logical inconsistencies like that.

The book, for instance, doesn't really question why the Wikipedia worked but the Wikinews didn't, something that no one may really know. The tone is closer to Ray Kinsella than Crash Davis. It celebrates Cory Doctorow, the famous editor of BoingBoing.net, a wonderful blog that I read daily. The authors explain how Doctorow gives away digital copies of his books because "his problem isn't piracy, it's obscurity."

Perhaps that's true, but a deeper question is how the wikis, mashups, and mixes will find their benchmarks of authority, their geodetic markers in memespace, their means of support. To test this danger, I wrote this greasemonkey script to count the words in a webpage between certain tags. On the day I wrote this, the admittedly imprecise script found 11788 words on the front page of Boing Boing, of which 6472 were between <blockquote> tags. That's about 50% borrowed text.

So far, this non-stop homage, this pantheon of fair use sells ads and seems to do quite well — Wikinomics suggests that BoingBoing's "readership now eclipses most mainstream media outlets." So why bother playing by the old school rules when you can just let others do the work while you push the boundaries of fair use and make money? There is a real danger that the original sources will find themselves starved for air as the Wikipedia and others fair use devotees suck up the top search rankings.

This may be why I think the book was right to bring these wiki worlds to the business community. At first I thought it was rather cynical to package up the wiki ideals into a neat bundle for the business leaders, but now I think that businesses are the ones who can really use and support the ideals. We now know that wikis can't be trusted for important, contentious areas of truthiness like politics, news, history, or any place where there's a difference of opinion about the facts, but it can still be ideal for semi-closed environments with outside means of support. I can imagine that wikis would be great for a corporation that needed to manage communication between the two divisions in different states. Openness gets rid of the natural inertia of bureaucracies. And it's clear that every company should have a wiki devoted to the user's guide so the customers can add what the manual writers never anticipated. Wikis allows one group to move ahead without asking another "mother may I". The umbrella business can pay the bills for keeping the lights on.

My guess is the folks in business who need to get things done may be the only ones who support the wikiconomy in the long term after the average joe gets a bit bored and tosses the wikis onto the pile of amusing distractions with the CB radios. The businesses are the ones with the real incentives to embrace the values of wikiness. And if you've spent a few years in the cubicle trenches, you know that words like "truthiness" have a certain ring to them.

Peter Wayner is the author of Translucent Databases and 12 other books.

You can purchase Wikinomics: How Mass Collaboration Changes Everything from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

peterwayner writes "If you're jazzed by the communitarian impulses driving Wikis, idea agora, Web 2.0 and other collaborative happenings, you'll be pleased to know that the new book Wikinomics is a great gift for that boss, spouse, or friend who doesn't quite grok it yet. The only logic bomb hidden in this statement is that much of what is wonderful in this book is wonderful because it's a book printed on pulp and written by two and only two authors. That is, the book is good because it's not a wiki." Read the rest of Peter's review. Wikinomics: How Mass Collaboration Changes Everything author Don Tapscott, Anthony D. Williams pages 320 publisher Penguin Group rating 8 reviewer Peter Wayner ISBN 1591841380 summary The pros and cons of wikis and their place in business

This statement isn't exactly true. The authors, Don Tapscott and Anthony Williams, have a wiki site at www.wikinomics.com devoted to the book. You can edit the wiki and have your say, but that's not what they're asking folks to buy. For the price of the book, you get a well-designed collection of thoughtful anecdotes stitched together by two talented business writers and polished by a good editor. They've made a good attempt to cover most aspects of the topic and they do an excellent job of explaining why the ideas are important for CEOs that are struggling to move their business forward. All of this is almost as portable as an iPod , dramatically less expensive and guaranteed never to need new batteries.

The tone of the book is bright and optimistic about how openness and wiki principles will help companies. We hear about how the wikipedia covered the London subway explosions, the way that Innocentive is opening up the R&D process for companies and the surprising inventiveness of Google maps users. The descriptions are thorough and well-researched, as far as they go, and when they're done going, the writers summarize them well. It's clear that the writers feel that the word "wikis" should be the new one word answer that CEOs should trot out when faced with the kind an impossible question, the kind of question that they the answered with "Internet" during the 1990s and "China" after the turn of the millenium.

The great advantages of the pulp-bound book become clear as you work your way through the text. In one section, for instance, Tapscott and Williams dismiss Jaron Lanier's worry that wikis can devolve when a smart mob develops the the same kind of "mass stupidity" that brought us Pol Pot or the Stalinist movement. "The winners will outnumber the losers", say the authors and conclude that Lanier "ran afoul". I don't really agree with the easy way that they dismissed the danger and if I had a wiki edit button in front of me, I would change the text to amplify Lanier's warnings. I've watched the mob rule delete perfectly good information from the wikipedia for no other reason than it wasn't "notable". The revision wars are legendary and any savvy wiki reader knows that skirmishes are more common than we would like. The well-meaning editors at the Wikipedia have probably destroyed more knowledge in the name of notability than the book burners of history. At least it's still there in the article history. But since Tapscott and Williams wrote a book that doesn't come with a wiki edit button, the text is better off because I didn't glue in my own divergent rant.

The optimism of the book is contagious and it would be a shame for it to be limited by a neutral point of view. Wikis organize casual information like how to install software, and this is the kind of job that is very important to business. Wikis may just be the wrong tool for, say, capturing political truthiness, but the book gives several good examples of how they energize corporations by making it easier for divisions, groups, and project teams to cooperate without going through traditional channels. If a business wants to formalize its collective intelligence, a wiki offers an ideal amount of flexibility.

If the book needs any editing, it would be to add more skepticism. At the beginning, they hint that they will address the kind of concerns that led Bill Gates to wonder about how society will pay for innovation if there's no profit incentive, but analyzing the limitations of the wikiworld isn't really their goal. There's little discussion of endeavors that have largely failed like Wikinews. That experiment with collaborative reporting had two articles on the day I wrote this and one article on the day before. (December 19 and 20th).

I've begun to feel lately that there is a real danger that free information will drive out paid information in much the same way that economists note that cheap money drives out the dear.

It's probably too early for us to have a firm grasp on the downsides to the wiki world and so it might be unfair to expect the book to be much of a buzz kill. One of the biggest logical problems I've found with the wikipedia is the inconsistent way that the movement treats traditional scholarship. On one hand, we're supposed to revel in the way that the wikipedia is often better than traditional mechanisms, but on the other hand the wikipedia gives more weight to outside sources. On the day I wrote this, the guide counseled, "Avoid weasel words such as, `Some people say ...' Instead, make your writing verifiable: find a specific person or group who holds that opinion and give a citation to a reputable publication in which they express that opinion." If the wikis become good enough to rival if not replace original sources, where will the wikis find the outside beacons of authority? Any strict logician will realize that there's a danger of proving 1=0 with this system, although I realize that all grown ups know that life is filled with logical inconsistencies like that.

The book, for instance, doesn't really question why the Wikipedia worked but the Wikinews didn't, something that no one may really know. The tone is closer to Ray Kinsella than Crash Davis. It celebrates Cory Doctorow, the famous editor of BoingBoing.net, a wonderful blog that I read daily. The authors explain how Doctorow gives away digital copies of his books because "his problem isn't piracy, it's obscurity."

Perhaps that's true, but a deeper question is how the wikis, mashups, and mixes will find their benchmarks of authority, their geodetic markers in memespace, their means of support. To test this danger, I wrote this greasemonkey script to count the words in a webpage between certain tags. On the day I wrote this, the admittedly imprecise script found 11788 words on the front page of Boing Boing, of which 6472 were between <blockquote> tags. That's about 50% borrowed text.

So far, this non-stop homage, this pantheon of fair use sells ads and seems to do quite well — Wikinomics suggests that BoingBoing's "readership now eclipses most mainstream media outlets." So why bother playing by the old school rules when you can just let others do the work while you push the boundaries of fair use and make money? There is a real danger that the original sources will find themselves starved for air as the Wikipedia and others fair use devotees suck up the top search rankings.

This may be why I think the book was right to bring these wiki worlds to the business community. At first I thought it was rather cynical to package up the wiki ideals into a neat bundle for the business leaders, but now I think that businesses are the ones who can really use and support the ideals. We now know that wikis can't be trusted for important, contentious areas of truthiness like politics, news, history, or any place where there's a difference of opinion about the facts, but it can still be ideal for semi-closed environments with outside means of support. I can imagine that wikis would be great for a corporation that needed to manage communication between the two divisions in different states. Openness gets rid of the natural inertia of bureaucracies. And it's clear that every company should have a wiki devoted to the user's guide so the customers can add what the manual writers never anticipated. Wikis allows one group to move ahead without asking another "mother may I". The umbrella business can pay the bills for keeping the lights on.

My guess is the folks in business who need to get things done may be the only ones who support the wikiconomy in the long term after the average joe gets a bit bored and tosses the wikis onto the pile of amusing distractions with the CB radios. The businesses are the ones with the real incentives to embrace the values of wikiness. And if you've spent a few years in the cubicle trenches, you know that words like "truthiness" have a certain ring to them.

Peter Wayner is the author of Translucent Databases and 12 other books.

You can purchase Wikinomics: How Mass Collaboration Changes Everything from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

peterwayner writes "If you're jazzed by the communitarian impulses driving Wikis, idea agora, Web 2.0 and other collaborative happenings, you'll be pleased to know that the new book Wikinomics is a great gift for that boss, spouse, or friend who doesn't quite grok it yet. The only logic bomb hidden in this statement is that much of what is wonderful in this book is wonderful because it's a book printed on pulp and written by two and only two authors. That is, the book is good because it's not a wiki." Read the rest of Peter's review. Wikinomics: How Mass Collaboration Changes Everything author Don Tapscott, Anthony D. Williams pages 320 publisher Penguin Group rating 8 reviewer Peter Wayner ISBN 1591841380 summary The pros and cons of wikis and their place in business

This statement isn't exactly true. The authors, Don Tapscott and Anthony Williams, have a wiki site at www.wikinomics.com devoted to the book. You can edit the wiki and have your say, but that's not what they're asking folks to buy. For the price of the book, you get a well-designed collection of thoughtful anecdotes stitched together by two talented business writers and polished by a good editor. They've made a good attempt to cover most aspects of the topic and they do an excellent job of explaining why the ideas are important for CEOs that are struggling to move their business forward. All of this is almost as portable as an iPod , dramatically less expensive and guaranteed never to need new batteries.

The tone of the book is bright and optimistic about how openness and wiki principles will help companies. We hear about how the wikipedia covered the London subway explosions, the way that Innocentive is opening up the R&D process for companies and the surprising inventiveness of Google maps users. The descriptions are thorough and well-researched, as far as they go, and when they're done going, the writers summarize them well. It's clear that the writers feel that the word "wikis" should be the new one word answer that CEOs should trot out when faced with the kind an impossible question, the kind of question that they the answered with "Internet" during the 1990s and "China" after the turn of the millenium.

The great advantages of the pulp-bound book become clear as you work your way through the text. In one section, for instance, Tapscott and Williams dismiss Jaron Lanier's worry that wikis can devolve when a smart mob develops the the same kind of "mass stupidity" that brought us Pol Pot or the Stalinist movement. "The winners will outnumber the losers", say the authors and conclude that Lanier "ran afoul". I don't really agree with the easy way that they dismissed the danger and if I had a wiki edit button in front of me, I would change the text to amplify Lanier's warnings. I've watched the mob rule delete perfectly good information from the wikipedia for no other reason than it wasn't "notable". The revision wars are legendary and any savvy wiki reader knows that skirmishes are more common than we would like. The well-meaning editors at the Wikipedia have probably destroyed more knowledge in the name of notability than the book burners of history. At least it's still there in the article history. But since Tapscott and Williams wrote a book that doesn't come with a wiki edit button, the text is better off because I didn't glue in my own divergent rant.

The optimism of the book is contagious and it would be a shame for it to be limited by a neutral point of view. Wikis organize casual information like how to install software, and this is the kind of job that is very important to business. Wikis may just be the wrong tool for, say, capturing political truthiness, but the book gives several good examples of how they energize corporations by making it easier for divisions, groups, and project teams to cooperate without going through traditional channels. If a business wants to formalize its collective intelligence, a wiki offers an ideal amount of flexibility.

If the book needs any editing, it would be to add more skepticism. At the beginning, they hint that they will address the kind of concerns that led Bill Gates to wonder about how society will pay for innovation if there's no profit incentive, but analyzing the limitations of the wikiworld isn't really their goal. There's little discussion of endeavors that have largely failed like Wikinews. That experiment with collaborative reporting had two articles on the day I wrote this and one article on the day before. (December 19 and 20th).

I've begun to feel lately that there is a real danger that free information will drive out paid information in much the same way that economists note that cheap money drives out the dear.

It's probably too early for us to have a firm grasp on the downsides to the wiki world and so it might be unfair to expect the book to be much of a buzz kill. One of the biggest logical problems I've found with the wikipedia is the inconsistent way that the movement treats traditional scholarship. On one hand, we're supposed to revel in the way that the wikipedia is often better than traditional mechanisms, but on the other hand the wikipedia gives more weight to outside sources. On the day I wrote this, the guide counseled, "Avoid weasel words such as, `Some people say ...' Instead, make your writing verifiable: find a specific person or group who holds that opinion and give a citation to a reputable publication in which they express that opinion." If the wikis become good enough to rival if not replace original sources, where will the wikis find the outside beacons of authority? Any strict logician will realize that there's a danger of proving 1=0 with this system, although I realize that all grown ups know that life is filled with logical inconsistencies like that.

The book, for instance, doesn't really question why the Wikipedia worked but the Wikinews didn't, something that no one may really know. The tone is closer to Ray Kinsella than Crash Davis. It celebrates Cory Doctorow, the famous editor of BoingBoing.net, a wonderful blog that I read daily. The authors explain how Doctorow gives away digital copies of his books because "his problem isn't piracy, it's obscurity."

Perhaps that's true, but a deeper question is how the wikis, mashups, and mixes will find their benchmarks of authority, their geodetic markers in memespace, their means of support. To test this danger, I wrote this greasemonkey script to count the words in a webpage between certain tags. On the day I wrote this, the admittedly imprecise script found 11788 words on the front page of Boing Boing, of which 6472 were between <blockquote> tags. That's about 50% borrowed text.

So far, this non-stop homage, this pantheon of fair use sells ads and seems to do quite well — Wikinomics suggests that BoingBoing's "readership now eclipses most mainstream media outlets." So why bother playing by the old school rules when you can just let others do the work while you push the boundaries of fair use and make money? There is a real danger that the original sources will find themselves starved for air as the Wikipedia and others fair use devotees suck up the top search rankings.

This may be why I think the book was right to bring these wiki worlds to the business community. At first I thought it was rather cynical to package up the wiki ideals into a neat bundle for the business leaders, but now I think that businesses are the ones who can really use and support the ideals. We now know that wikis can't be trusted for important, contentious areas of truthiness like politics, news, history, or any place where there's a difference of opinion about the facts, but it can still be ideal for semi-closed environments with outside means of support. I can imagine that wikis would be great for a corporation that needed to manage communication between the two divisions in different states. Openness gets rid of the natural inertia of bureaucracies. And it's clear that every company should have a wiki devoted to the user's guide so the customers can add what the manual writers never anticipated. Wikis allows one group to move ahead without asking another "mother may I". The umbrella business can pay the bills for keeping the lights on.

My guess is the folks in business who need to get things done may be the only ones who support the wikiconomy in the long term after the average joe gets a bit bored and tosses the wikis onto the pile of amusing distractions with the CB radios. The businesses are the ones with the real incentives to embrace the values of wikiness. And if you've spent a few years in the cubicle trenches, you know that words like "truthiness" have a certain ring to them.

Peter Wayner is the author of Translucent Databases and 12 other books.

You can purchase Wikinomics: How Mass Collaboration Changes Everything from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

peterwayner writes "There are few corners of the world that are more closely associated with the word "nerd" than comic books and physics. Despite the large overlap in the fan base, the two disciplines seem doomed to live forever in different corners of our minds. Superheroes don't have to obey the laws of physics and that's probably what makes them so attractive to the poor physicists who labor long and hard in the hope of making those laws work correctly. James Kakalios, a physics professor at the University of Minnesota, has produced a book, "The Physics of Superheroes" (now in paperback). The surprise is that the two don't behave like matter and anti-matter. They don't explode on contact." Read the rest of Peter's review. The Physics of Superheroes author James Kakilios pages 340 publisher Gotham Books rating 9 reviewer Peter Wayner ISBN 1-59240242-9 summary Why superman isn't as far fetched as it may seem.

There's no reason to spoil the book. You'll have to read it if you want to know why Superman can't change history, how Magneto becomes Electro when he runs, and whether Spiderman could really do those amazing things with spider silk. Some of the chapters are devoted to celebrating the accuracy of the comic strips by working through the physical equations. Much of what the comic book writers imagined is actually pretty reasonable. These sections bring new discipline to those old debates over who's stronger, bigger or most capable.

Other sections spell out just how wrong some of the assumptions are. Even when he's deflating the hopes of those kids who wish they could fly like Superman, he uses the disconnection with reality as a chance to riff on some what-if questions. What if Superman came from a planet that had a gravitational field 15 times stronger than earth? Would he be able to leap tall buildings? And then what would happen to a planet that was 15 times denser than earth? Would it fly apart as it rotated? Could you build one by just making a bigger version of Earth? What if you put some superdense material in the center of your new Earth? These are the questions that Kakalios works through.

The core theorem or narrative device of the book (choose your point of view) is that comic book authors can't bend too many rules. In fact, they usually can't get away with breaking more one or two. Then the hero must live a conventional life in our world and that's what makes it interesting. Spiderman may have a superstrong webbing, but he's still as vulnerable to depression as the next man. Batman may have unlimited wealth, but that won't bring back his parents. To paraphrase Robert Frost, comic book authors aren't playing tennis without a net.

In this world, science and comic narrative aren't bizarro versions of each other. Stories are sort of like free-form experiments where the scientist tries to change just one thing and measure the results. From this viewpoint, there's little difference between the two disciplines. A comic book is just a shorthand version of a scientific experiment.

This link implies an interesting and perhaps dangerous notion: science is just a longhand version of comic books. Sure, the folks at the cell phone companies have been striving mightily to make real that button on James T. Kirk's chest. That's the good news. But what about the darker notions? Anyone who's dealt with the side-effects of supposedly safe drugs like Vioxx knows that the bench scientists are as constrained as the comic book authors. They've got to come up with research that satisfies their customers and provide a simple resolution before that customer loses interest. (And won't those scientists come up with an ending for the debate about the link between cell phone-brain cancer before a jury does?)

But such speculation may kill the fun in the book. It's really just an excuse to toss around some equations and ask "what if" with a bit more rigor. This book may not be a grand, unifying theorem for the big plots of comic books and the big theories of science, but it's a neat first cut. It's as fascinating as much for its nuts and bolts description of physics as its offhand way of mixing together mathematical frameworks with narrative understanding.

Bio: Peter Wayner is the author of 13 books like Translucent Databases and Disappearing Cryptography .

You can purchase The Physics of Superheroes from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

peterwayner writes "There are few corners of the world that are more closely associated with the word "nerd" than comic books and physics. Despite the large overlap in the fan base, the two disciplines seem doomed to live forever in different corners of our minds. Superheroes don't have to obey the laws of physics and that's probably what makes them so attractive to the poor physicists who labor long and hard in the hope of making those laws work correctly. James Kakalios, a physics professor at the University of Minnesota, has produced a book, "The Physics of Superheroes" (now in paperback). The surprise is that the two don't behave like matter and anti-matter. They don't explode on contact." Read the rest of Peter's review. The Physics of Superheroes author James Kakilios pages 340 publisher Gotham Books rating 9 reviewer Peter Wayner ISBN 1-59240242-9 summary Why superman isn't as far fetched as it may seem.

There's no reason to spoil the book. You'll have to read it if you want to know why Superman can't change history, how Magneto becomes Electro when he runs, and whether Spiderman could really do those amazing things with spider silk. Some of the chapters are devoted to celebrating the accuracy of the comic strips by working through the physical equations. Much of what the comic book writers imagined is actually pretty reasonable. These sections bring new discipline to those old debates over who's stronger, bigger or most capable.

Other sections spell out just how wrong some of the assumptions are. Even when he's deflating the hopes of those kids who wish they could fly like Superman, he uses the disconnection with reality as a chance to riff on some what-if questions. What if Superman came from a planet that had a gravitational field 15 times stronger than earth? Would he be able to leap tall buildings? And then what would happen to a planet that was 15 times denser than earth? Would it fly apart as it rotated? Could you build one by just making a bigger version of Earth? What if you put some superdense material in the center of your new Earth? These are the questions that Kakalios works through.

The core theorem or narrative device of the book (choose your point of view) is that comic book authors can't bend too many rules. In fact, they usually can't get away with breaking more one or two. Then the hero must live a conventional life in our world and that's what makes it interesting. Spiderman may have a superstrong webbing, but he's still as vulnerable to depression as the next man. Batman may have unlimited wealth, but that won't bring back his parents. To paraphrase Robert Frost, comic book authors aren't playing tennis without a net.

In this world, science and comic narrative aren't bizarro versions of each other. Stories are sort of like free-form experiments where the scientist tries to change just one thing and measure the results. From this viewpoint, there's little difference between the two disciplines. A comic book is just a shorthand version of a scientific experiment.

This link implies an interesting and perhaps dangerous notion: science is just a longhand version of comic books. Sure, the folks at the cell phone companies have been striving mightily to make real that button on James T. Kirk's chest. That's the good news. But what about the darker notions? Anyone who's dealt with the side-effects of supposedly safe drugs like Vioxx knows that the bench scientists are as constrained as the comic book authors. They've got to come up with research that satisfies their customers and provide a simple resolution before that customer loses interest. (And won't those scientists come up with an ending for the debate about the link between cell phone-brain cancer before a jury does?)

But such speculation may kill the fun in the book. It's really just an excuse to toss around some equations and ask "what if" with a bit more rigor. This book may not be a grand, unifying theorem for the big plots of comic books and the big theories of science, but it's a neat first cut. It's as fascinating as much for its nuts and bolts description of physics as its offhand way of mixing together mathematical frameworks with narrative understanding.

Bio: Peter Wayner is the author of 13 books like Translucent Databases and Disappearing Cryptography .

You can purchase The Physics of Superheroes from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Peter Wayner writes: "When jury duty called, I was lucky enough to have a copy of Larry Lessig's new book, Free Culture: How Big Media Uses Technology and the Law to Lock Down Culture and Control Creativity, to take along. The Mitchell Courthouse in Baltimore is one of the most beautiful and ambitious marble allegories for how the law can be elegant, ornate, and permanently imposing. It was the perfect place to read a new book devoted to stopping the old guard media czars from using law to keep the couch potatoes down." Read on for the rest of Wayner's review of the book -- which is released today in hardcover, but also available for free online. Free Culture: How Big Media Uses Technology and the Law to Lock Down Culture and Control Creativity author Lawrence Lessig pages 388 publisher Penguin rating 9 reviewer Peter Wayner ISBN 0375505784 summary Lessig takes a serious but accessible look at how law has been subverted by Big Media and proposes workable steps for taking it back.

Lessig is now famous for a number of reasons, including his two previous books, Code and Other Laws of Cyberspace and The Future of Ideas : The Fate of the Commons in a Connected World. In the first, he was one of the first to affirm what many Slashdot readers know almost instinctively: whomever writes the code determines how the world works. Making the right decisions about power and control when designing a computer system is just as important as writing laws for the future. In the second, he writes of the importance of a vast cultural commons which acts as the wellspring for our expression and the grounding plate for our souls.

His new book is his most casual and most accessible. His prose is improving as he drops the footnote-heavy habit of legal writing and adopts a bloggier style driven by anecdotes and personal revelation. And what anecdotes he has -- Lessig's years on the barricades have given a surprisingly large collection of tales that will make any artist or citizen cringe. Time and time again, the powerful warlords of the entertainment conglomerates have banded together to try to stomp out the sharing and cooperation emerging from the Internet. After years of amassing a strangehold on the world's culture, the conglomerates aren't letting this cheap, fast and out-of-control technology sweep it all away.

My favorite anecdote, if one could be said to stand out, comes from a film maker documenting an opera company. When the camera caught a snippet of the stagehands watching the Simpsons with the sound turned down, the director wanted to add a four-second clip to the movie. Matt Groening said "Yes." The lawyers said it was clearly fair use. But Fox's executives responded with the kind of obscenity that doesn't upset the FCC: pay us $10,000. The clip didn't make the film because the director couldn't afford to go head-to-head with the Fox legal department.

This is just one of a number of stories of how interesting, invigorating content and innovation was strangled at birth by old guard. The anecdotes are, I think, an effort to atone for his loss in the Eldred case and reargue it. He presented the Supreme Court with a very logical and legal reading of why it was wrong for Congress to continue extending the length of a copyright monopoly and the court didn't buy it. A friend of his said that this tack was wrong because the court wanted to feel the depths of the injustice. The justices didn't want laws and footnotes, they wanted something human. Lessig blames his loss on not taking this advice. (As an aside, Lessig's personal description of taking a case to the Supreme Court is a good way to understand just how human the game can be.)

This time around, he piles the examples on top of more examples to show just how the conglomerates can hurt the artist and culture in general. After this case failed, Lessig tried another compromise that exposed the true goals of the copyright czars. Lessig describes his efforts to recreate a copyright registration system. If someone wanted to keep a copyright in force after 50 years, Lessig suggested getting them to pay a $1 fee. This would help everyone keep the copyright straight and make it simpler for everyone to understand just who has what rights to an art work. Any art work that goes unregistered flops into the public domain. Anyone who's tried to clear rights to a project will see this as a step in the right direction. The copyright industry, however, rejected this structure in a way that Lessig suggests illustrates how much this is about power and control, not creativity and expression.

Lessig has other tricks up his sleeve. If he can't convince the U.S. government to change the law, he can appeal to the artists themselves who have the ultimate control. He started his Creative Commons project several years ago and now artists can use several boilerplate licenses that reserve some of the rights while releasing others.

This new book itself is also available for free (PDF) under the license, a tactic that has worked well for Cory Doctorow and myself in the past. When I released Free for All under the license several years after the book was published, I watched the asking price on Amazon's used book market rise more than 40%. It wasn't a big jump, but it was still a bit counterintuitive. The freely available text encouraged people to buy the more readable printed version. I think Lessig will see the same effect. The sales driven by the people who read the electronic version will be greater than the sales lost to the people who just read the downloaded copy.

The good news is that the markets and the consumers are already heeding Lessig's advice because they instinctively disdain a monopoly. The power of the old networks is rapidly disappearing and the increasing concentration among the old guard is as much an illustration of the last ditch effort by the executives to cash out by taking large bonuses from the transactions. Some worry about the concentration of power in the radio world by companies like Clear Channel. But who listens to radio for music any longer? One Clear Channel station near my house plays traffic reports every 10 minutes during the day because their audience is dominated by people trapped on aptly named "parkways". The station may play as few as three songs an hour between 6:30am and 9am. The rest of the time, they yak about movies or the weather and their influence upon music continues to drop.

There are surprisingly good alternatives developing to take over the space. Lessig does an excellent job describing how the Internet radio stations were mugged with unfair regulations, but it's important to remember that they continue to exist because they offer something better than endless traffic reports. Furthermore, competition is coming from strange places. Starbucks is just one such company selling commercial- free mix tapes that are, for almost all intents and purposes, just a plastic disk version of a cool DJ. More and more radio-like venues are appearing.

There are other reasons why the concentration is backfiring. Lessig does a good job explaining how the television networks are squeezing out competition from independent producers. He describes how Norman Lear was only able to bring us "All in the Family" because he was free to take his work from ABC to CBS. That freedom disappeared after Congress repealed the laws forbidding the networks from owning stakes in the shows they broadcast. Now, if you want to get on CBS, it helps to sell a part of your show to CBS or, even better, just sell the whole thing.

But is this strategy really working for the networks? Their ratings continue to plummet. There's a reason why there are so many drug commercials for arthritis remedies on network air. That generation is the last one who watches network television almost instinctively. Lessig likes to complain about the "soviet" nature of these networks. It's a wonderful word that reads on many levels. The more they squeeze out competition and aggregate power in the committees, the more they lose the fluid competition that lets cream rise to the top.

So, who really cares if CBS isn't available on the Dish network? There are hundreds of other channels offering good fare. It was a different story in the 1970's when there were only three networks and CBS offered shows like "All in the Family" and "Mary Tyler Moore". Then, they controlled the heart of our popular culture. Today, the network ratings are so low on Saturday night that all of the networks are looking for a way to stop broadcasting on that day. Aside from the NCAA basketball tournament, I've lived without CBS for years without missing a thing. (Even then, I get most sports news from the websites.) The DVD player is a very, very powerful and destructive technology. When you can buy 50 movies for $30, who even needs CBS, the Dish network or HBO?

All of these idea swirled through my mind as I read Lessig's book and waited during jury duty. Are things getting worse or better? Are the 40+ million plus fileswapping pirates winning, or are the draconian laws crushing our creativity like a jackboot? I spent my time thinking of this balance while waiting for the judge and the attorneys to sift through 150 people to find the right 12 folks to render a fair and impartial verdict. On one hand, it was remarkable that society was being so careful before imprisoning someone for attempted murder. On the other, it was clear that the effort can't be sustained for the 40 million+ file sharing pirates who are thumbing their nose at the law.

Lessig understands this. One of his most persuasive arguments is that the current law becomes more marginalized as it becomes increasingly less fair. Prohibition of alcohol corroded the law and now the increasing prohibition of fair use is eroding respect for copyright.You only need to travel a few blocks from the Mitchell court house to end up in dangerous regions of Baltimore where the marble and the pomp can't do much to protect you. Lessig, the lawyer, knows the law can only work when it is fair and equitable. This new book is a strong and passionate argument for how we can restore some sanity to the system and restore our faith in copyright law. Some people think that Lessig is trying to "smash" the copyright system, but I think he's just trying to restore its ability to function.

Peter Wayner is the author of Free for All , a book on the open source movement and Policing Online Games, a book on how to build the Mitchell courthouse in cyberspace. You can purchase Free Culture: How Big Media Uses Technology and the Law to Lock Down Culture and Control Creativity from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page. mpawlo points out you can get the book free and gratis via Bittorrent.

Peter Wayner writes: "When jury duty called, I was lucky enough to have a copy of Larry Lessig's new book, Free Culture: How Big Media Uses Technology and the Law to Lock Down Culture and Control Creativity, to take along. The Mitchell Courthouse in Baltimore is one of the most beautiful and ambitious marble allegories for how the law can be elegant, ornate, and permanently imposing. It was the perfect place to read a new book devoted to stopping the old guard media czars from using law to keep the couch potatoes down." Read on for the rest of Wayner's review of the book -- which is released today in hardcover, but also available for free online. Free Culture: How Big Media Uses Technology and the Law to Lock Down Culture and Control Creativity author Lawrence Lessig pages 388 publisher Penguin rating 9 reviewer Peter Wayner ISBN 0375505784 summary Lessig takes a serious but accessible look at how law has been subverted by Big Media and proposes workable steps for taking it back.

Lessig is now famous for a number of reasons, including his two previous books, Code and Other Laws of Cyberspace and The Future of Ideas : The Fate of the Commons in a Connected World. In the first, he was one of the first to affirm what many Slashdot readers know almost instinctively: whomever writes the code determines how the world works. Making the right decisions about power and control when designing a computer system is just as important as writing laws for the future. In the second, he writes of the importance of a vast cultural commons which acts as the wellspring for our expression and the grounding plate for our souls.

His new book is his most casual and most accessible. His prose is improving as he drops the footnote-heavy habit of legal writing and adopts a bloggier style driven by anecdotes and personal revelation. And what anecdotes he has -- Lessig's years on the barricades have given a surprisingly large collection of tales that will make any artist or citizen cringe. Time and time again, the powerful warlords of the entertainment conglomerates have banded together to try to stomp out the sharing and cooperation emerging from the Internet. After years of amassing a strangehold on the world's culture, the conglomerates aren't letting this cheap, fast and out-of-control technology sweep it all away.

My favorite anecdote, if one could be said to stand out, comes from a film maker documenting an opera company. When the camera caught a snippet of the stagehands watching the Simpsons with the sound turned down, the director wanted to add a four-second clip to the movie. Matt Groening said "Yes." The lawyers said it was clearly fair use. But Fox's executives responded with the kind of obscenity that doesn't upset the FCC: pay us $10,000. The clip didn't make the film because the director couldn't afford to go head-to-head with the Fox legal department.

This is just one of a number of stories of how interesting, invigorating content and innovation was strangled at birth by old guard. The anecdotes are, I think, an effort to atone for his loss in the Eldred case and reargue it. He presented the Supreme Court with a very logical and legal reading of why it was wrong for Congress to continue extending the length of a copyright monopoly and the court didn't buy it. A friend of his said that this tack was wrong because the court wanted to feel the depths of the injustice. The justices didn't want laws and footnotes, they wanted something human. Lessig blames his loss on not taking this advice. (As an aside, Lessig's personal description of taking a case to the Supreme Court is a good way to understand just how human the game can be.)

This time around, he piles the examples on top of more examples to show just how the conglomerates can hurt the artist and culture in general. After this case failed, Lessig tried another compromise that exposed the true goals of the copyright czars. Lessig describes his efforts to recreate a copyright registration system. If someone wanted to keep a copyright in force after 50 years, Lessig suggested getting them to pay a $1 fee. This would help everyone keep the copyright straight and make it simpler for everyone to understand just who has what rights to an art work. Any art work that goes unregistered flops into the public domain. Anyone who's tried to clear rights to a project will see this as a step in the right direction. The copyright industry, however, rejected this structure in a way that Lessig suggests illustrates how much this is about power and control, not creativity and expression.

Lessig has other tricks up his sleeve. If he can't convince the U.S. government to change the law, he can appeal to the artists themselves who have the ultimate control. He started his Creative Commons project several years ago and now artists can use several boilerplate licenses that reserve some of the rights while releasing others.

This new book itself is also available for free (PDF) under the license, a tactic that has worked well for Cory Doctorow and myself in the past. When I released Free for All under the license several years after the book was published, I watched the asking price on Amazon's used book market rise more than 40%. It wasn't a big jump, but it was still a bit counterintuitive. The freely available text encouraged people to buy the more readable printed version. I think Lessig will see the same effect. The sales driven by the people who read the electronic version will be greater than the sales lost to the people who just read the downloaded copy.

The good news is that the markets and the consumers are already heeding Lessig's advice because they instinctively disdain a monopoly. The power of the old networks is rapidly disappearing and the increasing concentration among the old guard is as much an illustration of the last ditch effort by the executives to cash out by taking large bonuses from the transactions. Some worry about the concentration of power in the radio world by companies like Clear Channel. But who listens to radio for music any longer? One Clear Channel station near my house plays traffic reports every 10 minutes during the day because their audience is dominated by people trapped on aptly named "parkways". The station may play as few as three songs an hour between 6:30am and 9am. The rest of the time, they yak about movies or the weather and their influence upon music continues to drop.

There are surprisingly good alternatives developing to take over the space. Lessig does an excellent job describing how the Internet radio stations were mugged with unfair regulations, but it's important to remember that they continue to exist because they offer something better than endless traffic reports. Furthermore, competition is coming from strange places. Starbucks is just one such company selling commercial- free mix tapes that are, for almost all intents and purposes, just a plastic disk version of a cool DJ. More and more radio-like venues are appearing.

There are other reasons why the concentration is backfiring. Lessig does a good job explaining how the television networks are squeezing out competition from independent producers. He describes how Norman Lear was only able to bring us "All in the Family" because he was free to take his work from ABC to CBS. That freedom disappeared after Congress repealed the laws forbidding the networks from owning stakes in the shows they broadcast. Now, if you want to get on CBS, it helps to sell a part of your show to CBS or, even better, just sell the whole thing.

But is this strategy really working for the networks? Their ratings continue to plummet. There's a reason why there are so many drug commercials for arthritis remedies on network air. That generation is the last one who watches network television almost instinctively. Lessig likes to complain about the "soviet" nature of these networks. It's a wonderful word that reads on many levels. The more they squeeze out competition and aggregate power in the committees, the more they lose the fluid competition that lets cream rise to the top.

So, who really cares if CBS isn't available on the Dish network? There are hundreds of other channels offering good fare. It was a different story in the 1970's when there were only three networks and CBS offered shows like "All in the Family" and "Mary Tyler Moore". Then, they controlled the heart of our popular culture. Today, the network ratings are so low on Saturday night that all of the networks are looking for a way to stop broadcasting on that day. Aside from the NCAA basketball tournament, I've lived without CBS for years without missing a thing. (Even then, I get most sports news from the websites.) The DVD player is a very, very powerful and destructive technology. When you can buy 50 movies for $30, who even needs CBS, the Dish network or HBO?

All of these idea swirled through my mind as I read Lessig's book and waited during jury duty. Are things getting worse or better? Are the 40+ million plus fileswapping pirates winning, or are the draconian laws crushing our creativity like a jackboot? I spent my time thinking of this balance while waiting for the judge and the attorneys to sift through 150 people to find the right 12 folks to render a fair and impartial verdict. On one hand, it was remarkable that society was being so careful before imprisoning someone for attempted murder. On the other, it was clear that the effort can't be sustained for the 40 million+ file sharing pirates who are thumbing their nose at the law.

Lessig understands this. One of his most persuasive arguments is that the current law becomes more marginalized as it becomes increasingly less fair. Prohibition of alcohol corroded the law and now the increasing prohibition of fair use is eroding respect for copyright.You only need to travel a few blocks from the Mitchell court house to end up in dangerous regions of Baltimore where the marble and the pomp can't do much to protect you. Lessig, the lawyer, knows the law can only work when it is fair and equitable. This new book is a strong and passionate argument for how we can restore some sanity to the system and restore our faith in copyright law. Some people think that Lessig is trying to "smash" the copyright system, but I think he's just trying to restore its ability to function.

Peter Wayner is the author of Free for All , a book on the open source movement and Policing Online Games, a book on how to build the Mitchell courthouse in cyberspace. You can purchase Free Culture: How Big Media Uses Technology and the Law to Lock Down Culture and Control Creativity from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page. mpawlo points out you can get the book free and gratis via Bittorrent.

Peter Wayner writes: "When jury duty called, I was lucky enough to have a copy of Larry Lessig's new book, Free Culture: How Big Media Uses Technology and the Law to Lock Down Culture and Control Creativity, to take along. The Mitchell Courthouse in Baltimore is one of the most beautiful and ambitious marble allegories for how the law can be elegant, ornate, and permanently imposing. It was the perfect place to read a new book devoted to stopping the old guard media czars from using law to keep the couch potatoes down." Read on for the rest of Wayner's review of the book -- which is released today in hardcover, but also available for free online. Free Culture: How Big Media Uses Technology and the Law to Lock Down Culture and Control Creativity author Lawrence Lessig pages 388 publisher Penguin rating 9 reviewer Peter Wayner ISBN 0375505784 summary Lessig takes a serious but accessible look at how law has been subverted by Big Media and proposes workable steps for taking it back.

Lessig is now famous for a number of reasons, including his two previous books, Code and Other Laws of Cyberspace and The Future of Ideas : The Fate of the Commons in a Connected World. In the first, he was one of the first to affirm what many Slashdot readers know almost instinctively: whomever writes the code determines how the world works. Making the right decisions about power and control when designing a computer system is just as important as writing laws for the future. In the second, he writes of the importance of a vast cultural commons which acts as the wellspring for our expression and the grounding plate for our souls.

His new book is his most casual and most accessible. His prose is improving as he drops the footnote-heavy habit of legal writing and adopts a bloggier style driven by anecdotes and personal revelation. And what anecdotes he has -- Lessig's years on the barricades have given a surprisingly large collection of tales that will make any artist or citizen cringe. Time and time again, the powerful warlords of the entertainment conglomerates have banded together to try to stomp out the sharing and cooperation emerging from the Internet. After years of amassing a strangehold on the world's culture, the conglomerates aren't letting this cheap, fast and out-of-control technology sweep it all away.

My favorite anecdote, if one could be said to stand out, comes from a film maker documenting an opera company. When the camera caught a snippet of the stagehands watching the Simpsons with the sound turned down, the director wanted to add a four-second clip to the movie. Matt Groening said "Yes." The lawyers said it was clearly fair use. But Fox's executives responded with the kind of obscenity that doesn't upset the FCC: pay us $10,000. The clip didn't make the film because the director couldn't afford to go head-to-head with the Fox legal department.

This is just one of a number of stories of how interesting, invigorating content and innovation was strangled at birth by old guard. The anecdotes are, I think, an effort to atone for his loss in the Eldred case and reargue it. He presented the Supreme Court with a very logical and legal reading of why it was wrong for Congress to continue extending the length of a copyright monopoly and the court didn't buy it. A friend of his said that this tack was wrong because the court wanted to feel the depths of the injustice. The justices didn't want laws and footnotes, they wanted something human. Lessig blames his loss on not taking this advice. (As an aside, Lessig's personal description of taking a case to the Supreme Court is a good way to understand just how human the game can be.)

This time around, he piles the examples on top of more examples to show just how the conglomerates can hurt the artist and culture in general. After this case failed, Lessig tried another compromise that exposed the true goals of the copyright czars. Lessig describes his efforts to recreate a copyright registration system. If someone wanted to keep a copyright in force after 50 years, Lessig suggested getting them to pay a $1 fee. This would help everyone keep the copyright straight and make it simpler for everyone to understand just who has what rights to an art work. Any art work that goes unregistered flops into the public domain. Anyone who's tried to clear rights to a project will see this as a step in the right direction. The copyright industry, however, rejected this structure in a way that Lessig suggests illustrates how much this is about power and control, not creativity and expression.

Lessig has other tricks up his sleeve. If he can't convince the U.S. government to change the law, he can appeal to the artists themselves who have the ultimate control. He started his Creative Commons project several years ago and now artists can use several boilerplate licenses that reserve some of the rights while releasing others.

This new book itself is also available for free (PDF) under the license, a tactic that has worked well for Cory Doctorow and myself in the past. When I released Free for All under the license several years after the book was published, I watched the asking price on Amazon's used book market rise more than 40%. It wasn't a big jump, but it was still a bit counterintuitive. The freely available text encouraged people to buy the more readable printed version. I think Lessig will see the same effect. The sales driven by the people who read the electronic version will be greater than the sales lost to the people who just read the downloaded copy.

The good news is that the markets and the consumers are already heeding Lessig's advice because they instinctively disdain a monopoly. The power of the old networks is rapidly disappearing and the increasing concentration among the old guard is as much an illustration of the last ditch effort by the executives to cash out by taking large bonuses from the transactions. Some worry about the concentration of power in the radio world by companies like Clear Channel. But who listens to radio for music any longer? One Clear Channel station near my house plays traffic reports every 10 minutes during the day because their audience is dominated by people trapped on aptly named "parkways". The station may play as few as three songs an hour between 6:30am and 9am. The rest of the time, they yak about movies or the weather and their influence upon music continues to drop.

There are surprisingly good alternatives developing to take over the space. Lessig does an excellent job describing how the Internet radio stations were mugged with unfair regulations, but it's important to remember that they continue to exist because they offer something better than endless traffic reports. Furthermore, competition is coming from strange places. Starbucks is just one such company selling commercial- free mix tapes that are, for almost all intents and purposes, just a plastic disk version of a cool DJ. More and more radio-like venues are appearing.

There are other reasons why the concentration is backfiring. Lessig does a good job explaining how the television networks are squeezing out competition from independent producers. He describes how Norman Lear was only able to bring us "All in the Family" because he was free to take his work from ABC to CBS. That freedom disappeared after Congress repealed the laws forbidding the networks from owning stakes in the shows they broadcast. Now, if you want to get on CBS, it helps to sell a part of your show to CBS or, even better, just sell the whole thing.

But is this strategy really working for the networks? Their ratings continue to plummet. There's a reason why there are so many drug commercials for arthritis remedies on network air. That generation is the last one who watches network television almost instinctively. Lessig likes to complain about the "soviet" nature of these networks. It's a wonderful word that reads on many levels. The more they squeeze out competition and aggregate power in the committees, the more they lose the fluid competition that lets cream rise to the top.

So, who really cares if CBS isn't available on the Dish network? There are hundreds of other channels offering good fare. It was a different story in the 1970's when there were only three networks and CBS offered shows like "All in the Family" and "Mary Tyler Moore". Then, they controlled the heart of our popular culture. Today, the network ratings are so low on Saturday night that all of the networks are looking for a way to stop broadcasting on that day. Aside from the NCAA basketball tournament, I've lived without CBS for years without missing a thing. (Even then, I get most sports news from the websites.) The DVD player is a very, very powerful and destructive technology. When you can buy 50 movies for $30, who even needs CBS, the Dish network or HBO?

All of these idea swirled through my mind as I read Lessig's book and waited during jury duty. Are things getting worse or better? Are the 40+ million plus fileswapping pirates winning, or are the draconian laws crushing our creativity like a jackboot? I spent my time thinking of this balance while waiting for the judge and the attorneys to sift through 150 people to find the right 12 folks to render a fair and impartial verdict. On one hand, it was remarkable that society was being so careful before imprisoning someone for attempted murder. On the other, it was clear that the effort can't be sustained for the 40 million+ file sharing pirates who are thumbing their nose at the law.

Lessig understands this. One of his most persuasive arguments is that the current law becomes more marginalized as it becomes increasingly less fair. Prohibition of alcohol corroded the law and now the increasing prohibition of fair use is eroding respect for copyright.You only need to travel a few blocks from the Mitchell court house to end up in dangerous regions of Baltimore where the marble and the pomp can't do much to protect you. Lessig, the lawyer, knows the law can only work when it is fair and equitable. This new book is a strong and passionate argument for how we can restore some sanity to the system and restore our faith in copyright law. Some people think that Lessig is trying to "smash" the copyright system, but I think he's just trying to restore its ability to function.

Peter Wayner is the author of Free for All , a book on the open source movement and Policing Online Games, a book on how to build the Mitchell courthouse in cyberspace. You can purchase Free Culture: How Big Media Uses Technology and the Law to Lock Down Culture and Control Creativity from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page. mpawlo points out you can get the book free and gratis via Bittorrent.

Peter Wayner writes with a review of O'Reilly's Security Warrior: "Close the doors and they come in the windows. Bar the windows and they slip through some cracks in the foundation. Seal those up and the find another way in through the door. Computer security is an odd pursuit because it's just not possible to have a strong, theory of everything when cracks can appear anywhere. Into this field comes Security Warrior, a book on the topic with a wide ranging collection of tidbits and suggestions on sealing as many holes as you can find." Read on for the rest. Security Warrior author Cyrus Peikari and Anton Chuvakin pages 531 publisher O'Reilly rating 7 reviewer Peter Wayner ISBN 0596005458 summary Not a deep approach to security, but a great bag of tricks every sysadmin should have at hand.

The book comes lightly packaged in a metaphor about the training of samurai. A security warrior, it is said, must avoid a "superficial study of the subject" because that leads to a "deterioration of the samurai spirit." To avoid this, the authors plunge deeply into a wide variety of ways that attackers might break into your system. The book is meant to help you "know your enemy" and "see through an attacker's eyes."

This chestbeating fluff disappears pretty quickly because the authors dive into reading assembly code in the first chapter and start talking about the registers of the CPU by page 4. The rest of the first part of the book explores reverse engineering software by reading assembly dumps and using good tools to decipher it.

After poking around in binary code, they turn to the bits floating around the network. Chapters 6 through 10 explore how to sit on one end of the Internet and pry your way into another computer. Chapters 11 through 17 dive deeper into the specific defenses of platforms like UNIX, Windows, SOAP and SQL. The rest of the book, Chapters 18 through 22, explore how to figure out just what the attackers may be doing by setting up honeypots and log analysis tools.

Covering all of these topics in 531 pages is clearly not possible and the book reads more like a survey or a catalog of what can go wrong. If you use PHP, for instance, as a frontend to your database, you might want to be sure that some "script kiddie" won't slip in some extra SQL in the form fields. Each topic isn't built up from some bedrock foundation with perfect mathematical pedagogy, it's just defined as a list of bad things that you should avoid doing.

The authors seem to be aware of how this might be misinterpreted. There are many good tricks in the book and it wouldn't be hard to rename it Al K Da's 1337 Haxor Tips . So the authors stress how learning about the enemy is the only way to defeat the hordes.

I think the problem is deeper and more philosophical. There's no way to prove a negative. There are no good mathematical tools that make it easy to prove statements like P!=NP or big numbers can't be factored quickly. In a larger sense, it's not really possible to prove that someone can't break into a system. A more traditional, ground-up approach to the topic can offer some assurances, but books like this one are always necessary. Anyone doing battle against unknowable and unpredictable adversaries must look between the cracks.

If you look at it this way, the book is a good collection of tips and hints that will help someone keep their network a bit more secure. It doesn't provide a deep, elegant and rigorous explication of the topic, but I don't think that is possible. It's a great collection of tricks that should be part of a good warrior's training.

Peter Wayner is the author of Translucent Databases and Policing Online Games . You can purchase Security Warrior from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Peter Wayner writes with a review of O'Reilly's Security Warrior: "Close the doors and they come in the windows. Bar the windows and they slip through some cracks in the foundation. Seal those up and the find another way in through the door. Computer security is an odd pursuit because it's just not possible to have a strong, theory of everything when cracks can appear anywhere. Into this field comes Security Warrior, a book on the topic with a wide ranging collection of tidbits and suggestions on sealing as many holes as you can find." Read on for the rest. Security Warrior author Cyrus Peikari and Anton Chuvakin pages 531 publisher O'Reilly rating 7 reviewer Peter Wayner ISBN 0596005458 summary Not a deep approach to security, but a great bag of tricks every sysadmin should have at hand.

The book comes lightly packaged in a metaphor about the training of samurai. A security warrior, it is said, must avoid a "superficial study of the subject" because that leads to a "deterioration of the samurai spirit." To avoid this, the authors plunge deeply into a wide variety of ways that attackers might break into your system. The book is meant to help you "know your enemy" and "see through an attacker's eyes."

This chestbeating fluff disappears pretty quickly because the authors dive into reading assembly code in the first chapter and start talking about the registers of the CPU by page 4. The rest of the first part of the book explores reverse engineering software by reading assembly dumps and using good tools to decipher it.

After poking around in binary code, they turn to the bits floating around the network. Chapters 6 through 10 explore how to sit on one end of the Internet and pry your way into another computer. Chapters 11 through 17 dive deeper into the specific defenses of platforms like UNIX, Windows, SOAP and SQL. The rest of the book, Chapters 18 through 22, explore how to figure out just what the attackers may be doing by setting up honeypots and log analysis tools.

Covering all of these topics in 531 pages is clearly not possible and the book reads more like a survey or a catalog of what can go wrong. If you use PHP, for instance, as a frontend to your database, you might want to be sure that some "script kiddie" won't slip in some extra SQL in the form fields. Each topic isn't built up from some bedrock foundation with perfect mathematical pedagogy, it's just defined as a list of bad things that you should avoid doing.

The authors seem to be aware of how this might be misinterpreted. There are many good tricks in the book and it wouldn't be hard to rename it Al K Da's 1337 Haxor Tips . So the authors stress how learning about the enemy is the only way to defeat the hordes.

I think the problem is deeper and more philosophical. There's no way to prove a negative. There are no good mathematical tools that make it easy to prove statements like P!=NP or big numbers can't be factored quickly. In a larger sense, it's not really possible to prove that someone can't break into a system. A more traditional, ground-up approach to the topic can offer some assurances, but books like this one are always necessary. Anyone doing battle against unknowable and unpredictable adversaries must look between the cracks.

If you look at it this way, the book is a good collection of tips and hints that will help someone keep their network a bit more secure. It doesn't provide a deep, elegant and rigorous explication of the topic, but I don't think that is possible. It's a great collection of tricks that should be part of a good warrior's training.

Peter Wayner is the author of Translucent Databases and Policing Online Games . You can purchase Security Warrior from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Peter Wayner writes: "The novel Paranoia begins with one of the most tantalizing premises I've read in some time. Young Adam Cassidy was just sliding by as a junior product line manager in the router division of Wyatt Telecom, when he discovered that the company wasn't doing much for the retirement of his pal down on the loading dock. So he impersonated the VP of corporate events, faked a few invoices, and booked the same caterer who brought in the steaks and lobster for the executive suite. Alas, Nicholas Wyatt, the CEO, wasn't happy with the steep bill and gave Cassidy a choice of 20 years in prison or life as a corporate spy. In no time, Cassidy decides he's quite willing to go undercover and find out just what the heck is going on the skunk works over at their competitor, Trion." Read on for the rest of Wayner's review. Paranoia author Joseph Finder pages 432 publisher St. Martin's rating 9 reviewer Peter Wayner ISBN 0312319142 summary A fast-paced thriller about a young router engineer who is

It may be hard for anyone who's endured the economic downturn in the computer industry and the ascendance of the DRM lawyers to see the romance of tech, but the computer business continues to be one of the most exciting and explosive corners of the zeitgeist. Fortunes are made and lost in days; products depend upon the synergy of the hackers and the marketeers; and everything turns on the information passed along in IMs, emails and whispers. This world is a rich backdrop for the new thriller by Joe Finder, the spy novelist who set his previous books in the world of the three-letter agencies and the military justice system. This time he's plumbing the depths of corporate politics and industrial espionage with his story of a company racing to deliver the next big Palm Pilot replacement.

The thriller is a reminder that electronic gizmos continue to be a tumultuous and exciting domain where creative people with whip-smart minds can change the company's destiny. I suppose it would be possible to set a similar novel in, say, the auto industry, but it just wouldn't have the same resonance. No engineer, designer, or bright employee is going to make much of a difference at Ford or General Motors. Much of their future is dictated by the cost of medical care for the retired workers and the problems are not about cars qua cars. Producing great cars would be nice, but it's not the main challenge for the companies. At least in Silicon Valley, there can be some direct link between action and reaction. Newton's law still holds.

The beginning of the book is an irresistable hook. Who wouldn't want to throw a party on the corporation's dime?

Many of the elements of Silicon Valley's mythology appear here. There's a boss who keeps stable of young, blonde administrative assistants around. There's another boss who works out of the same size cubicle as everyone else. Secret research labs to develop the next generation of gadgets are locked away in a perimeter guarded by other gadgets that scan eyeballs or examine fingerprints. All of the characters drive slick cars and worry about the quality of their real estate.

As the novel unfolds, Cassidy's allegiance and soul is pulled in a tug-of-war. Who deserves the information he's gathering? Is there right and wrong in corporate espionage? Which company deserves to win?

The novel is similar in tone and structure to John Grisham's The Firm or Michael Crichton's Disclosure, two other novels that mused about the nature of the modern workplace. Finder's characters are richer and better drawn, at least than Grisham's earlier works. The search for the next gadget isn't really the point of Cassidy journey in the labyrinth, it's just an excuse to work through the modern world of corporations and the way they organize people and their creations. The book is not filled with the neo-Marxist questioning of the capitalist system that comes from places like the Baffler , but there are similar themes that echo in the cubicle bins.

This is, of course, because it's a thriller, not some postmodern master's degree thesis. The twists are well-handled, the pacing is good, and the ending may open the doors to debates. I spent some time wondering whether it was the best ending on many different levels. That kind of resolution is something that doesn't come from standard thrillers by people like Tom Clancy or James Paterson. In those books, the author's point of view is as solid and fixed as, say, those opinion shows on Fox TV. Someone's always dying or trying to destroy America in those books and stopping the murder or saving the country is the only possible resolution.

Finder's earlier books delved into the mirror world of espionage and the realm of three-letter agencies. Moscow Club focused on a coup and an assassination in Soviet Russia. Extraordinary Powers explored the possibility that various spy agencies could tap clairvoyance and other extra-sensory powers-- a premise that David Moorhouse later confirmed was very real in his book, Psychic Warrior . The world of covert assassination in Latin America took center stage in High Crimes.

The tone is also much lighter than Finder's early books, with their heavy body count. After watching the movie version of High Crimes, I kept wishing someone would write a nice comedy for Ashley Judd. She deserved it, after the blood and betrayal. This time, death isn't part of the stakes, and this leaves Finder a bit more room to maneuver and play people and allegiances off each other. Cutting down on the raw danger gives him the freedom to build suspense with action and character. The book is really a light-hearted romp through a semi-mythical world where fortunes are huge, dreams are made real through engineering, and everyone drives a slick car. I say "semi-mythical," because despite the downturn, there's still plenty of money in some corners of technology. Will it always be there? Well, that's not the point of this book.

It's worth commending Finder for his insight into the technology world. His background is more in Russian literature and spy things, not in programming. Yet, the tech world he creates is as true to life in Silicon Valley as books like Po Bronson's The First 10 Million is the Hardest and Douglas Coupland's Microserfs. Technology is a wonderful domain for a novelist to work within, and we should be glad he came in from the cold to check it out.

Peter Wayner is the author of 13 thrilling technical books on topics like building secure databases ( Translucent Databases ), steganography ( Disappearing Cryptography ), and stopping cheating ( Policing Online Games ). You can purchase Paranoia from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Peter Wayner writes: "The novel Paranoia begins with one of the most tantalizing premises I've read in some time. Young Adam Cassidy was just sliding by as a junior product line manager in the router division of Wyatt Telecom, when he discovered that the company wasn't doing much for the retirement of his pal down on the loading dock. So he impersonated the VP of corporate events, faked a few invoices, and booked the same caterer who brought in the steaks and lobster for the executive suite. Alas, Nicholas Wyatt, the CEO, wasn't happy with the steep bill and gave Cassidy a choice of 20 years in prison or life as a corporate spy. In no time, Cassidy decides he's quite willing to go undercover and find out just what the heck is going on the skunk works over at their competitor, Trion." Read on for the rest of Wayner's review. Paranoia author Joseph Finder pages 432 publisher St. Martin's rating 9 reviewer Peter Wayner ISBN 0312319142 summary A fast-paced thriller about a young router engineer who is

It may be hard for anyone who's endured the economic downturn in the computer industry and the ascendance of the DRM lawyers to see the romance of tech, but the computer business continues to be one of the most exciting and explosive corners of the zeitgeist. Fortunes are made and lost in days; products depend upon the synergy of the hackers and the marketeers; and everything turns on the information passed along in IMs, emails and whispers. This world is a rich backdrop for the new thriller by Joe Finder, the spy novelist who set his previous books in the world of the three-letter agencies and the military justice system. This time he's plumbing the depths of corporate politics and industrial espionage with his story of a company racing to deliver the next big Palm Pilot replacement.

The thriller is a reminder that electronic gizmos continue to be a tumultuous and exciting domain where creative people with whip-smart minds can change the company's destiny. I suppose it would be possible to set a similar novel in, say, the auto industry, but it just wouldn't have the same resonance. No engineer, designer, or bright employee is going to make much of a difference at Ford or General Motors. Much of their future is dictated by the cost of medical care for the retired workers and the problems are not about cars qua cars. Producing great cars would be nice, but it's not the main challenge for the companies. At least in Silicon Valley, there can be some direct link between action and reaction. Newton's law still holds.

The beginning of the book is an irresistable hook. Who wouldn't want to throw a party on the corporation's dime?

Many of the elements of Silicon Valley's mythology appear here. There's a boss who keeps stable of young, blonde administrative assistants around. There's another boss who works out of the same size cubicle as everyone else. Secret research labs to develop the next generation of gadgets are locked away in a perimeter guarded by other gadgets that scan eyeballs or examine fingerprints. All of the characters drive slick cars and worry about the quality of their real estate.

As the novel unfolds, Cassidy's allegiance and soul is pulled in a tug-of-war. Who deserves the information he's gathering? Is there right and wrong in corporate espionage? Which company deserves to win?

The novel is similar in tone and structure to John Grisham's The Firm or Michael Crichton's Disclosure, two other novels that mused about the nature of the modern workplace. Finder's characters are richer and better drawn, at least than Grisham's earlier works. The search for the next gadget isn't really the point of Cassidy journey in the labyrinth, it's just an excuse to work through the modern world of corporations and the way they organize people and their creations. The book is not filled with the neo-Marxist questioning of the capitalist system that comes from places like the Baffler , but there are similar themes that echo in the cubicle bins.

This is, of course, because it's a thriller, not some postmodern master's degree thesis. The twists are well-handled, the pacing is good, and the ending may open the doors to debates. I spent some time wondering whether it was the best ending on many different levels. That kind of resolution is something that doesn't come from standard thrillers by people like Tom Clancy or James Paterson. In those books, the author's point of view is as solid and fixed as, say, those opinion shows on Fox TV. Someone's always dying or trying to destroy America in those books and stopping the murder or saving the country is the only possible resolution.

Finder's earlier books delved into the mirror world of espionage and the realm of three-letter agencies. Moscow Club focused on a coup and an assassination in Soviet Russia. Extraordinary Powers explored the possibility that various spy agencies could tap clairvoyance and other extra-sensory powers-- a premise that David Moorhouse later confirmed was very real in his book, Psychic Warrior . The world of covert assassination in Latin America took center stage in High Crimes.

The tone is also much lighter than Finder's early books, with their heavy body count. After watching the movie version of High Crimes, I kept wishing someone would write a nice comedy for Ashley Judd. She deserved it, after the blood and betrayal. This time, death isn't part of the stakes, and this leaves Finder a bit more room to maneuver and play people and allegiances off each other. Cutting down on the raw danger gives him the freedom to build suspense with action and character. The book is really a light-hearted romp through a semi-mythical world where fortunes are huge, dreams are made real through engineering, and everyone drives a slick car. I say "semi-mythical," because despite the downturn, there's still plenty of money in some corners of technology. Will it always be there? Well, that's not the point of this book.

It's worth commending Finder for his insight into the technology world. His background is more in Russian literature and spy things, not in programming. Yet, the tech world he creates is as true to life in Silicon Valley as books like Po Bronson's The First 10 Million is the Hardest and Douglas Coupland's Microserfs. Technology is a wonderful domain for a novelist to work within, and we should be glad he came in from the cold to check it out.

Peter Wayner is the author of 13 thrilling technical books on topics like building secure databases ( Translucent Databases ), steganography ( Disappearing Cryptography ), and stopping cheating ( Policing Online Games ). You can purchase Paranoia from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Peter Wayner writes: "The novel Paranoia begins with one of the most tantalizing premises I've read in some time. Young Adam Cassidy was just sliding by as a junior product line manager in the router division of Wyatt Telecom, when he discovered that the company wasn't doing much for the retirement of his pal down on the loading dock. So he impersonated the VP of corporate events, faked a few invoices, and booked the same caterer who brought in the steaks and lobster for the executive suite. Alas, Nicholas Wyatt, the CEO, wasn't happy with the steep bill and gave Cassidy a choice of 20 years in prison or life as a corporate spy. In no time, Cassidy decides he's quite willing to go undercover and find out just what the heck is going on the skunk works over at their competitor, Trion." Read on for the rest of Wayner's review. Paranoia author Joseph Finder pages 432 publisher St. Martin's rating 9 reviewer Peter Wayner ISBN 0312319142 summary A fast-paced thriller about a young router engineer who is

It may be hard for anyone who's endured the economic downturn in the computer industry and the ascendance of the DRM lawyers to see the romance of tech, but the computer business continues to be one of the most exciting and explosive corners of the zeitgeist. Fortunes are made and lost in days; products depend upon the synergy of the hackers and the marketeers; and everything turns on the information passed along in IMs, emails and whispers. This world is a rich backdrop for the new thriller by Joe Finder, the spy novelist who set his previous books in the world of the three-letter agencies and the military justice system. This time he's plumbing the depths of corporate politics and industrial espionage with his story of a company racing to deliver the next big Palm Pilot replacement.

The thriller is a reminder that electronic gizmos continue to be a tumultuous and exciting domain where creative people with whip-smart minds can change the company's destiny. I suppose it would be possible to set a similar novel in, say, the auto industry, but it just wouldn't have the same resonance. No engineer, designer, or bright employee is going to make much of a difference at Ford or General Motors. Much of their future is dictated by the cost of medical care for the retired workers and the problems are not about cars qua cars. Producing great cars would be nice, but it's not the main challenge for the companies. At least in Silicon Valley, there can be some direct link between action and reaction. Newton's law still holds.

The beginning of the book is an irresistable hook. Who wouldn't want to throw a party on the corporation's dime?

Many of the elements of Silicon Valley's mythology appear here. There's a boss who keeps stable of young, blonde administrative assistants around. There's another boss who works out of the same size cubicle as everyone else. Secret research labs to develop the next generation of gadgets are locked away in a perimeter guarded by other gadgets that scan eyeballs or examine fingerprints. All of the characters drive slick cars and worry about the quality of their real estate.

As the novel unfolds, Cassidy's allegiance and soul is pulled in a tug-of-war. Who deserves the information he's gathering? Is there right and wrong in corporate espionage? Which company deserves to win?

The novel is similar in tone and structure to John Grisham's The Firm or Michael Crichton's Disclosure, two other novels that mused about the nature of the modern workplace. Finder's characters are richer and better drawn, at least than Grisham's earlier works. The search for the next gadget isn't really the point of Cassidy journey in the labyrinth, it's just an excuse to work through the modern world of corporations and the way they organize people and their creations. The book is not filled with the neo-Marxist questioning of the capitalist system that comes from places like the Baffler , but there are similar themes that echo in the cubicle bins.

This is, of course, because it's a thriller, not some postmodern master's degree thesis. The twists are well-handled, the pacing is good, and the ending may open the doors to debates. I spent some time wondering whether it was the best ending on many different levels. That kind of resolution is something that doesn't come from standard thrillers by people like Tom Clancy or James Paterson. In those books, the author's point of view is as solid and fixed as, say, those opinion shows on Fox TV. Someone's always dying or trying to destroy America in those books and stopping the murder or saving the country is the only possible resolution.

Finder's earlier books delved into the mirror world of espionage and the realm of three-letter agencies. Moscow Club focused on a coup and an assassination in Soviet Russia. Extraordinary Powers explored the possibility that various spy agencies could tap clairvoyance and other extra-sensory powers-- a premise that David Moorhouse later confirmed was very real in his book, Psychic Warrior . The world of covert assassination in Latin America took center stage in High Crimes.

The tone is also much lighter than Finder's early books, with their heavy body count. After watching the movie version of High Crimes, I kept wishing someone would write a nice comedy for Ashley Judd. She deserved it, after the blood and betrayal. This time, death isn't part of the stakes, and this leaves Finder a bit more room to maneuver and play people and allegiances off each other. Cutting down on the raw danger gives him the freedom to build suspense with action and character. The book is really a light-hearted romp through a semi-mythical world where fortunes are huge, dreams are made real through engineering, and everyone drives a slick car. I say "semi-mythical," because despite the downturn, there's still plenty of money in some corners of technology. Will it always be there? Well, that's not the point of this book.

It's worth commending Finder for his insight into the technology world. His background is more in Russian literature and spy things, not in programming. Yet, the tech world he creates is as true to life in Silicon Valley as books like Po Bronson's The First 10 Million is the Hardest and Douglas Coupland's Microserfs. Technology is a wonderful domain for a novelist to work within, and we should be glad he came in from the cold to check it out.

Peter Wayner is the author of 13 thrilling technical books on topics like building secure databases ( Translucent Databases ), steganography ( Disappearing Cryptography ), and stopping cheating ( Policing Online Games ). You can purchase Paranoia from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Michael Yuan writes "Enterprise JavaBean (EJB) is one of the most widely used technologies in enterprise Java. It is designed to be a scalable and flexible distributed framework. In EJB, almost everything can be done in several different ways and it offers the developer the maximum flexibility to choose the right approach for the project in hand." Yuan provides a review, below, of Bitter EJB, to guide programmers interested in large-scale Java development. Update: 10/27 18:27 GMT by T : Peter Wayner provides a somewhat deeper look at the book as well, also below. Bitter EJB author Bruce Tate, Mike Clark, Bob Lee, Patrick Linskey pages 412 publisher Manning rating 9 reviewer Michael Yuan, Peter Wayner ISBN 1930110952 summary Anti-patterns in Enterprise JavaBean development

However, every coin has two sides: the other side of "freedom of choice" is "complexity". Although EJB is an incredibly powerful tool in the hands of experience architects, it is subject to a lot of misuse by novice developers who do not make sound choices. For example, some developers might use a BMP entity bean to map each database table in the system; or access entity beans directly from a distributed layer; or store large amount of data in session objects ... The list goes on. Although those approaches are technically possible, they are hardly the most efficient ways in most cases. Such problems have not only caused many projects to fail but also tarnished EJB's reputation. In fact, the complexity of EJB is often quoted as an argument for other enterprise platforms.

For EJB developers, it is crucial to learn from other people's experiences and follow proven best practices. That helps to reduce the complexity of the platform. Manning's "Bitter EJB" is a very timely book written by well-known experts in the EJB field: Bruce Tate, Mike Clark, Bob Lee and Patrick Linskey. Unlike other "architectural" books, Bitter EJB teaches best practices through common mistakes (anti-patterns). It focuses on "what not to do" but still encourages developers to come up with liberal (everything not forbidden is OK) and innovative solutions. After all, EJB is about flexibility and freedom of choices.

Part I of the book is an overview of anti-patterns in the EJB specification. The EJB specification itself has several major design problems when it first came out in March 1998. EJB v1.1 and v2.0 have gone great length to fix the anti-patterns in the specification. But early adopters may have already developed some anti-patterns in their applications. For new developers, the history also serves as a valuable lesson on what EJB is really for and how different components in the specification fall into their current places. In this part, the authors also provide an excellent recount on what went wrong in the high profile TSS Java PetStore benchmark.

Part II is about session and message-driven beans. Those beans are mainly used in the integration layers. Topics covered in this part include how to deal with large database results, whether to maintain session states, the limitations of XML and much more.

Part III covers EJB persistence. Entity EJBs are probably the most confusing types of components. Many experts have advocated to abolish entity EJBs altogether in favor of other simpler persistence frameworks such as the JDO or even simple JDBC facades. The authors discuss the pros and cons of entity EJBs and covers most leading alternatives. For those who must use entity EJBs, this book also offers useful advices on a range of topics including how to reduce round trips, shorten primary keys and handle expensive database joins etc.

Part IV covers broader topics including performance tuning, testing, building and packaging. One big problem that even EJB developer can recognize the complex deployment descriptors. One chapter of the book is dedicated to reduce code duplication, automate the deployment process and avoid the "integration hell". The last chapter of the book provides an overview of "what's next" in the EJB space.

Overall, it is an excellent book for all EJB developers and other enterprise developers who want to learn from the successes and failures of EJBs."

Peter Wayner's review:

Although there may be as many 36 plots in all of literature, the compartively new world of computer books has really had only one: this new technology is simple, very simple, and it will make your life better and your teeth whiter. Bruce Tate opened up a second plot in his book Bitter Java by exploring just how even the best programming ideas have dark sides. Now he's back with three other authors exploring the world of Bitter EJB.

This book is more fruit from the same tree. Or, to hack the Java MemeStream even more, more beans for the same mill. If you use Enterprise Java Beans (EJB), or think about using them, you should read this book to see what can go wrong. The title shows how naming schemes can be misleading because either the authors aren't really that bitter, or because they're focused entirely on EJBs. This book does not belong in the same camp with the Java==SUV crowd. These authors are really admirers who just want to warn people how to avoid problems with Java and EJB.

Tate and his new co-authors, Mike Clark, Bob Lee, and Patrick Linskey are all consultants who seem to use Java a lot, at least when they're not cheating death. One of the cuter grace notes in the book is a collection of war stories from extreme sports that are mixed in as an allegorical taste of what's to come. Before exploring the problems with a Java concept known as enterprise beans, they tell a kayaking story that ends with the sentence, "Then we hear a loud crunch and look up to see Eric's stern stationary at the top of the drop, revealing the sitaution that every kayaker dreads the most -- the vertical pin."

After stories like this, the book goes on to explore just how the very fancy enterprise beans toolkit can produce an application that moves slower than a stream filled with honey. Each chapter is filled with antipatterns, or lessons about the software learned the hard way. They're sort of like points on the map that say, "There be dragons here."

The book is divided into four parts. The first section, termed "The Basics," explores the simple ways that EJB technology goes bad. The toolkit was heavily hyped as the perfect solution for building business websites that interface seamlessly with large databases. As the business grew, new servers could be added without grief. Alas, as this section points out, there are many reasons why an elephant gun can be the wrong weapon for getting rid of mice in your house.

The next section on "Networks and Messages" describes how good ideas can turn into slow code when people misuse the fancy tools for scaling EJBs. In theory, the EJB toolkit will split up processes simply across multiple machines to handle more customers, but in practice all of the communication can slow things down considerably.
The section on "EJB Persistence" describes how the much-hyped system for seamlessly storing away enterprise beans in databases can weigh down a system. My only beef is that they left out much information on Prevayler, a much-maligned and misunderstood ultra-light toolkit that is like an anti-EJB persistence layer in every possible way. I'm enamored with it, if only because it's such a radical move away from the monolithic APIs like EJBs. While they liken using EJBs to snowboarding in fresh powder with a 100lb pack on your back, Prevayler is sort of like boots-only hiking.


The last section isn't about EJBs per se, but similar toolkits and projects that often get used with EJB. There are antipatterns to avoid with JUnitPref and Ant, too. Some of these suggestions, like some in the rest of the book, aren't terribly new or brillant, but it can't hurt to get another lecture on the importance of testing your code.

The book shines when it's exploring what goes on behind the slick facade of the API. Sure, the EJB toolkit will dutifully load up data from any object on any server in your farm, but you better be careful invoking some of these these methods because the network is slow. The book often points out how invoking that one simple method from the sales literature can start up dozens of sluggish threads. Peeling away the layers helps understand and explain why the system fails.

Many of these lessons aren't limited to Java or EJB. I wouldn't be surprised if the group of authors was busy rewriting the book with examples from .NET. Unfortunately, some programming problems are very hard, and building a toolkit with a simple API won't make them go away. In fact, the simple appearance can cause more trouble when the programmer can't understand what the secret mechanism inside is doing. Almost all of the problems in this book arise from programmers who believe the sales literature when it tells them not to pay attention to what that little bot behind the curtain is doing. If you're working in the world of EJB consulting on big iron, then you've got no choice but to start thinking about what's behind that curtain.

You can purchase the Bitter EJB from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page. Peter Wayner is the author of 13 books including Java RAMBO Manifesto and Translucent Databases.

Michael Yuan writes "Enterprise JavaBean (EJB) is one of the most widely used technologies in enterprise Java. It is designed to be a scalable and flexible distributed framework. In EJB, almost everything can be done in several different ways and it offers the developer the maximum flexibility to choose the right approach for the project in hand." Yuan provides a review, below, of Bitter EJB, to guide programmers interested in large-scale Java development. Update: 10/27 18:27 GMT by T : Peter Wayner provides a somewhat deeper look at the book as well, also below. Bitter EJB author Bruce Tate, Mike Clark, Bob Lee, Patrick Linskey pages 412 publisher Manning rating 9 reviewer Michael Yuan, Peter Wayner ISBN 1930110952 summary Anti-patterns in Enterprise JavaBean development

However, every coin has two sides: the other side of "freedom of choice" is "complexity". Although EJB is an incredibly powerful tool in the hands of experience architects, it is subject to a lot of misuse by novice developers who do not make sound choices. For example, some developers might use a BMP entity bean to map each database table in the system; or access entity beans directly from a distributed layer; or store large amount of data in session objects ... The list goes on. Although those approaches are technically possible, they are hardly the most efficient ways in most cases. Such problems have not only caused many projects to fail but also tarnished EJB's reputation. In fact, the complexity of EJB is often quoted as an argument for other enterprise platforms.

For EJB developers, it is crucial to learn from other people's experiences and follow proven best practices. That helps to reduce the complexity of the platform. Manning's "Bitter EJB" is a very timely book written by well-known experts in the EJB field: Bruce Tate, Mike Clark, Bob Lee and Patrick Linskey. Unlike other "architectural" books, Bitter EJB teaches best practices through common mistakes (anti-patterns). It focuses on "what not to do" but still encourages developers to come up with liberal (everything not forbidden is OK) and innovative solutions. After all, EJB is about flexibility and freedom of choices.

Part I of the book is an overview of anti-patterns in the EJB specification. The EJB specification itself has several major design problems when it first came out in March 1998. EJB v1.1 and v2.0 have gone great length to fix the anti-patterns in the specification. But early adopters may have already developed some anti-patterns in their applications. For new developers, the history also serves as a valuable lesson on what EJB is really for and how different components in the specification fall into their current places. In this part, the authors also provide an excellent recount on what went wrong in the high profile TSS Java PetStore benchmark.

Part II is about session and message-driven beans. Those beans are mainly used in the integration layers. Topics covered in this part include how to deal with large database results, whether to maintain session states, the limitations of XML and much more.

Part III covers EJB persistence. Entity EJBs are probably the most confusing types of components. Many experts have advocated to abolish entity EJBs altogether in favor of other simpler persistence frameworks such as the JDO or even simple JDBC facades. The authors discuss the pros and cons of entity EJBs and covers most leading alternatives. For those who must use entity EJBs, this book also offers useful advices on a range of topics including how to reduce round trips, shorten primary keys and handle expensive database joins etc.

Part IV covers broader topics including performance tuning, testing, building and packaging. One big problem that even EJB developer can recognize the complex deployment descriptors. One chapter of the book is dedicated to reduce code duplication, automate the deployment process and avoid the "integration hell". The last chapter of the book provides an overview of "what's next" in the EJB space.

Overall, it is an excellent book for all EJB developers and other enterprise developers who want to learn from the successes and failures of EJBs."

Peter Wayner's review:

Although there may be as many 36 plots in all of literature, the compartively new world of computer books has really had only one: this new technology is simple, very simple, and it will make your life better and your teeth whiter. Bruce Tate opened up a second plot in his book Bitter Java by exploring just how even the best programming ideas have dark sides. Now he's back with three other authors exploring the world of Bitter EJB.

This book is more fruit from the same tree. Or, to hack the Java MemeStream even more, more beans for the same mill. If you use Enterprise Java Beans (EJB), or think about using them, you should read this book to see what can go wrong. The title shows how naming schemes can be misleading because either the authors aren't really that bitter, or because they're focused entirely on EJBs. This book does not belong in the same camp with the Java==SUV crowd. These authors are really admirers who just want to warn people how to avoid problems with Java and EJB.

Tate and his new co-authors, Mike Clark, Bob Lee, and Patrick Linskey are all consultants who seem to use Java a lot, at least when they're not cheating death. One of the cuter grace notes in the book is a collection of war stories from extreme sports that are mixed in as an allegorical taste of what's to come. Before exploring the problems with a Java concept known as enterprise beans, they tell a kayaking story that ends with the sentence, "Then we hear a loud crunch and look up to see Eric's stern stationary at the top of the drop, revealing the sitaution that every kayaker dreads the most -- the vertical pin."

After stories like this, the book goes on to explore just how the very fancy enterprise beans toolkit can produce an application that moves slower than a stream filled with honey. Each chapter is filled with antipatterns, or lessons about the software learned the hard way. They're sort of like points on the map that say, "There be dragons here."

The book is divided into four parts. The first section, termed "The Basics," explores the simple ways that EJB technology goes bad. The toolkit was heavily hyped as the perfect solution for building business websites that interface seamlessly with large databases. As the business grew, new servers could be added without grief. Alas, as this section points out, there are many reasons why an elephant gun can be the wrong weapon for getting rid of mice in your house.

The next section on "Networks and Messages" describes how good ideas can turn into slow code when people misuse the fancy tools for scaling EJBs. In theory, the EJB toolkit will split up processes simply across multiple machines to handle more customers, but in practice all of the communication can slow things down considerably.
The section on "EJB Persistence" describes how the much-hyped system for seamlessly storing away enterprise beans in databases can weigh down a system. My only beef is that they left out much information on Prevayler, a much-maligned and misunderstood ultra-light toolkit that is like an anti-EJB persistence layer in every possible way. I'm enamored with it, if only because it's such a radical move away from the monolithic APIs like EJBs. While they liken using EJBs to snowboarding in fresh powder with a 100lb pack on your back, Prevayler is sort of like boots-only hiking.


The last section isn't about EJBs per se, but similar toolkits and projects that often get used with EJB. There are antipatterns to avoid with JUnitPref and Ant, too. Some of these suggestions, like some in the rest of the book, aren't terribly new or brillant, but it can't hurt to get another lecture on the importance of testing your code.

The book shines when it's exploring what goes on behind the slick facade of the API. Sure, the EJB toolkit will dutifully load up data from any object on any server in your farm, but you better be careful invoking some of these these methods because the network is slow. The book often points out how invoking that one simple method from the sales literature can start up dozens of sluggish threads. Peeling away the layers helps understand and explain why the system fails.

Many of these lessons aren't limited to Java or EJB. I wouldn't be surprised if the group of authors was busy rewriting the book with examples from .NET. Unfortunately, some programming problems are very hard, and building a toolkit with a simple API won't make them go away. In fact, the simple appearance can cause more trouble when the programmer can't understand what the secret mechanism inside is doing. Almost all of the problems in this book arise from programmers who believe the sales literature when it tells them not to pay attention to what that little bot behind the curtain is doing. If you're working in the world of EJB consulting on big iron, then you've got no choice but to start thinking about what's behind that curtain.

You can purchase the Bitter EJB from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page. Peter Wayner is the author of 13 books including Java RAMBO Manifesto and Translucent Databases.

Peter Wayner writes: "One of the greatest mysteries of today is whether a pirate is good or bad. On one hand, Disney campaigns against digital piracy while making a movie ( "Pirates of the Caribbean") pushing a theme park ride that celebrates life under the Jolly Roger. On one hand, we celebrate Talk Like a Pirate Day, while on the other hand this fine, upstanding investment company was fined $19.7m for copyright infringement and no one used the word 'Pirate.' This is the world that greets the paperback edition of Pirate Hunter, Richard Zacks's excellent history of the late so-called pirate, Captain William Kidd." Read on for the rest of Peter's review. Pirate Hunter author Richard Zacks pages 426 publisher Hyperion rating 8 reviewer Peter Wayner ISBN 0786884517 summary The life and times of an real pirate.

While Kidd's name may be synonymous with piracy in our culture's muddled collective memory, the book establishes that the sailor was nothing of the sort. If anything, he was framed by powerful forces trying to maintain a struggling business model. Why does that sound familiar?

This book is a wonderful example of what a talented writer and a relentless researcher can do with records that date from the 17th century. Kidd was born in Scotland in 1654, lived to see the 18th century, and recorded some of his daily life in log books that were sometimes sketchy and sometimes voluminous. By synthesizing the information from Kidd's papers, various British archives, ships logs, correspondence and other ephemera, Zacks was able to build a detailed narrative around Kidd's last major voyage. Did you know that in 1699, the going price for fine silks and other exotic fabrics was about 3 yards per piece of eight? Or perhaps that Cotton Mather preached to Kidd on January 21, 1700 on Jeremiah 17:11? I shudder to think what someone will be able to do with the Wayback machine.

By 1696 when the book begins, Kidd was one of the wealthiest landowners in the United States living in a river front mansion near Wall Street. His block and tackle helped build Trinity Church where his family sat in the fourth row each Sunday. Kidd married well and his wife gave him a child. Kidd was, according to his marriage certificate, a gentleman. Still, as Richard Grasso found out, this wasn't enough to stop the political winds from turning an seemingly honest dollar into ill-gotten plunder.

The pirate world, on the other hand, was a different place from the tip of Manhattan. The men on a true pirate ship sailed hard, tortured the weak ships they could find, and then spent their earnings on rum and women in sketchy ports of call that asked no questions. It was, according to the dreaded pirate Bartholomew Roberts , "A merry life and a short one."

Still, despite the disrespect for the rules of property, the pirate life offered many other socially advanced customs that outdistanced the civilized world where the Kings and Queens proclaimed they ruled by divine right. Zacks points out that pirate ships were run as strict democracies and the captains could be deposed at any time by a recall election known as a parlay. "All food and liquor was to be shared equally, a mind-boggling concept for sailors long used to watching officers dine and guzzle for hours on end," he notes.

So why did Kidd leave his comfortable New York home and head to sea again? Zacks establishes that Kidd was given a commission by four lords in the British admirality. Kidd received a new ship, a crew, and the instructions to capture any of the pirates who were plaguing the British East India companies. Kidd was to be a pirate hunter, a fighter for good, not evil, who would conveniently split his takings with his four backers. Some details of the commission were kept secret because the backers were going to keep the treasure and avoid giving the goods back to the rightful owners who lost the treasure to the pirates in the first place. This was a cousin to the doctrine proclaiming that two wrongs make a right.

The book sails through Kidd's voyage in exquisite detail. It's a pirate story that sometimes wilder and sometimes slower than any fiction writer could offer. Somewhere along the trip, the rumors begin to circulate that Kidd had turned pirate. Zacks suggests the whispers began as an act of treachery by one of his old partners who did dabble in piracy. The partners could cover their own tracks by blaming Kidd. The rumors fed into the Royal Navy's faulty intelligence network which dutifully hyped the size of the pirate world in order to serve its own ends.

Along the way, it becomes clear that piracy was as much a different political system as a violent crime against property. When the laws and strictures of society grow too binding, men might slip them off and sail into the sunset. Piracy was a decision to forgo the social contract that most had never signed in the first place, in most cases because the social contract offered by the official government was not particular gracious. Zacks compares life on a pirate ship to life under the British flag when the opportunity presents itself.

Who received a greater share of the wealth? Which class structure was more rigid? Who was responsible for more privation and inhumanity? It's impossible to do the calculus, but Zacks makes it clear that the pirates understood something of what Bob Dylan's theorem that you must be honest to live outside the law. At one bitterly ironic point, the black so-called pirates on Kidd's ship are treated with much more respect than the white ones, but only because the captors know that the black ones will fetch a nice price at the slave market in London.

In Kidd's case, the question of his piracy oscillates in a mechanism of a war between political factions. Zacks suggests that the English East India company, which was sort of the Microsoft of the day when sea trade was high tech, fanned the rumors of Kidd's departure from fair society to ingratiate itself before the Grand Moghul in India. Kidd's commission to take so-called pirate ships put him at odds with the work of the trading company which launched merchant ships skirting their own set of rules.

So the book evolves on two levels. The men fight with guns and ships that are all just extensions of lawyers and corporations. Kidd's struggle to gain a fortune, repay his backers, and return to his wife in New York gets caught in the middle of the greater evolution of English law, American rebellion, French imperialism, and old fashioned greed, . Was he a pirate or gentleman? Does he plunder enough pirates to repay his backers? Does he survive to clear his name? It would be a shame to ruin this fine story by revealing the ending of the book. Of course, the deeper questions of the true nature of piracy and its hold on our imagination, continue to resonate today.

Peter Wayner is the author of Policing Online Games , a book about pirate hunting of a sort, and Java RAMBO Manifesto , an exploration of how to live without a database. You can purchase Pirate Hunter from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Peter Wayner writes: "One of the greatest mysteries of today is whether a pirate is good or bad. On one hand, Disney campaigns against digital piracy while making a movie ( "Pirates of the Caribbean") pushing a theme park ride that celebrates life under the Jolly Roger. On one hand, we celebrate Talk Like a Pirate Day, while on the other hand this fine, upstanding investment company was fined $19.7m for copyright infringement and no one used the word 'Pirate.' This is the world that greets the paperback edition of Pirate Hunter, Richard Zacks's excellent history of the late so-called pirate, Captain William Kidd." Read on for the rest of Peter's review. Pirate Hunter author Richard Zacks pages 426 publisher Hyperion rating 8 reviewer Peter Wayner ISBN 0786884517 summary The life and times of an real pirate.

While Kidd's name may be synonymous with piracy in our culture's muddled collective memory, the book establishes that the sailor was nothing of the sort. If anything, he was framed by powerful forces trying to maintain a struggling business model. Why does that sound familiar?

This book is a wonderful example of what a talented writer and a relentless researcher can do with records that date from the 17th century. Kidd was born in Scotland in 1654, lived to see the 18th century, and recorded some of his daily life in log books that were sometimes sketchy and sometimes voluminous. By synthesizing the information from Kidd's papers, various British archives, ships logs, correspondence and other ephemera, Zacks was able to build a detailed narrative around Kidd's last major voyage. Did you know that in 1699, the going price for fine silks and other exotic fabrics was about 3 yards per piece of eight? Or perhaps that Cotton Mather preached to Kidd on January 21, 1700 on Jeremiah 17:11? I shudder to think what someone will be able to do with the Wayback machine.

By 1696 when the book begins, Kidd was one of the wealthiest landowners in the United States living in a river front mansion near Wall Street. His block and tackle helped build Trinity Church where his family sat in the fourth row each Sunday. Kidd married well and his wife gave him a child. Kidd was, according to his marriage certificate, a gentleman. Still, as Richard Grasso found out, this wasn't enough to stop the political winds from turning an seemingly honest dollar into ill-gotten plunder.

The pirate world, on the other hand, was a different place from the tip of Manhattan. The men on a true pirate ship sailed hard, tortured the weak ships they could find, and then spent their earnings on rum and women in sketchy ports of call that asked no questions. It was, according to the dreaded pirate Bartholomew Roberts , "A merry life and a short one."

Still, despite the disrespect for the rules of property, the pirate life offered many other socially advanced customs that outdistanced the civilized world where the Kings and Queens proclaimed they ruled by divine right. Zacks points out that pirate ships were run as strict democracies and the captains could be deposed at any time by a recall election known as a parlay. "All food and liquor was to be shared equally, a mind-boggling concept for sailors long used to watching officers dine and guzzle for hours on end," he notes.

So why did Kidd leave his comfortable New York home and head to sea again? Zacks establishes that Kidd was given a commission by four lords in the British admirality. Kidd received a new ship, a crew, and the instructions to capture any of the pirates who were plaguing the British East India companies. Kidd was to be a pirate hunter, a fighter for good, not evil, who would conveniently split his takings with his four backers. Some details of the commission were kept secret because the backers were going to keep the treasure and avoid giving the goods back to the rightful owners who lost the treasure to the pirates in the first place. This was a cousin to the doctrine proclaiming that two wrongs make a right.

The book sails through Kidd's voyage in exquisite detail. It's a pirate story that sometimes wilder and sometimes slower than any fiction writer could offer. Somewhere along the trip, the rumors begin to circulate that Kidd had turned pirate. Zacks suggests the whispers began as an act of treachery by one of his old partners who did dabble in piracy. The partners could cover their own tracks by blaming Kidd. The rumors fed into the Royal Navy's faulty intelligence network which dutifully hyped the size of the pirate world in order to serve its own ends.

Along the way, it becomes clear that piracy was as much a different political system as a violent crime against property. When the laws and strictures of society grow too binding, men might slip them off and sail into the sunset. Piracy was a decision to forgo the social contract that most had never signed in the first place, in most cases because the social contract offered by the official government was not particular gracious. Zacks compares life on a pirate ship to life under the British flag when the opportunity presents itself.

Who received a greater share of the wealth? Which class structure was more rigid? Who was responsible for more privation and inhumanity? It's impossible to do the calculus, but Zacks makes it clear that the pirates understood something of what Bob Dylan's theorem that you must be honest to live outside the law. At one bitterly ironic point, the black so-called pirates on Kidd's ship are treated with much more respect than the white ones, but only because the captors know that the black ones will fetch a nice price at the slave market in London.

In Kidd's case, the question of his piracy oscillates in a mechanism of a war between political factions. Zacks suggests that the English East India company, which was sort of the Microsoft of the day when sea trade was high tech, fanned the rumors of Kidd's departure from fair society to ingratiate itself before the Grand Moghul in India. Kidd's commission to take so-called pirate ships put him at odds with the work of the trading company which launched merchant ships skirting their own set of rules.

So the book evolves on two levels. The men fight with guns and ships that are all just extensions of lawyers and corporations. Kidd's struggle to gain a fortune, repay his backers, and return to his wife in New York gets caught in the middle of the greater evolution of English law, American rebellion, French imperialism, and old fashioned greed, . Was he a pirate or gentleman? Does he plunder enough pirates to repay his backers? Does he survive to clear his name? It would be a shame to ruin this fine story by revealing the ending of the book. Of course, the deeper questions of the true nature of piracy and its hold on our imagination, continue to resonate today.

Peter Wayner is the author of Policing Online Games , a book about pirate hunting of a sort, and Java RAMBO Manifesto , an exploration of how to live without a database. You can purchase Pirate Hunter from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Peter Wayner writes: "If you're looking for a quick way to test the difference between reading text online and reading it in a book, turn to Steal This Computer Book 3 by Wallace Wang, the third edition of a popular series that promises to tell you 'what they won't tell you about the Internet.' All of the information in the book can be gathered from Google for free, but the crisp writing, clean presentation and printed format make the book a good deal. It's possible to curl up in a chair out of WiFi range and cruise the best parts of the Internet without leaving a trail of cookies." Read on below for the rest of Peter's review -- it's free! Steal This Computer Book 3 author Wallace Wang pages 358 publisher No Starch Press rating 9 reviewer Peter Wayner ISBN 1593270003 summary An irreverant

The book is a travelog of many of the most interesting or inflammatory corners of the Internet. There are chapters on hacktivism, hate crime, con games, spam, phone phreaking and dozens of other topics. If someone's spent time flaming about it, banning it, subpoenaing it, or demonizing it, there's probably a section on it here. All of the sections come with screen shots and URLs for further digging.

I found reading the book to be an odd pleasure. There was no way to click on the sites or try any of the software without heading for a computer, but that didn't seem to matter. If anything, it was nice to skip over the links and put off heading down alternate paths until later. The more I experience books like this, the more I begin to wonder if there's much in the hyper-fragmented, postmodern view of a narrative built out of multiply forking paths. This book offers one fairly simple arc that carries us through the most talked about corners of the web and it does it fairly gracefully. That's a pleasure unto itself.

The book comes with a rebellious gloss and semiotic history. The title was stolen from Steal This Book a collection of anarchist schemes written by Abbie Hoffman in the 1960s. Despite the title, that book became a bestseller -- offering a glimpse of the longterm prospects for Hoffman's revolution. All of the prole sheep dutifully bought a book filled with bombmaking techniques that promises to show you where "exactly to place the dynamite that will destroy the walls."

Hoffman's book showed that people will buy something they value even when they're told to steal it. The prole sheep intuitively understand that books cost money to create. But maybe that was a different era, before the web existed. This website offers the text even though there are four editions for sale at Amazon. I wonder who holds the rights?

Wang's book is nowhere near as radical or as dangerous. Hoffman wrote sentences like "The purpose of part two is not to fuck the system, but destroy it." Wang generally avoids such antagonistic language and speaks generally about anti-social behavior in the third person: "When hackers use social engineering, they often masquerade as a consultant or temporary worker..."

Much of the book, in fact, is filled with techniques that are presented as tools for protecting your privacy and your personal information. The back cover asks, "Is your computer safe from computer viruses and malicious hackers?" It's only partially aimed at helping people do asocial things on the Net. Helping people protect themselves from the evil hordes is a large part of it. Given that identity theft is a booming business, this edition is practically an anti-crime book.

What does this mean for the this Internet revolution? Will the current file trading yippies overthrow the copyright system? Will file sharing actually become the norm? Or will all of the Napsterites follow the paths of Hoffman's proteges and grow up, have kids, move to the burbs, and start paying for their content? Well, they might if the content is as comfortable as this book in the hands while sitting in a La-Z-Boy recliner. No popup windows. No flash graphics. No registration required. Just pure content. Hmmm.

Peter Wayner is the author of books like Policing Online Games, Translucent Databases and Java RAMBO Manifesto. Please don't steal them. You can purchase Steal This Computer Book 3 from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Peter Wayner writes: "If you're looking for a quick way to test the difference between reading text online and reading it in a book, turn to Steal This Computer Book 3 by Wallace Wang, the third edition of a popular series that promises to tell you 'what they won't tell you about the Internet.' All of the information in the book can be gathered from Google for free, but the crisp writing, clean presentation and printed format make the book a good deal. It's possible to curl up in a chair out of WiFi range and cruise the best parts of the Internet without leaving a trail of cookies." Read on below for the rest of Peter's review -- it's free! Steal This Computer Book 3 author Wallace Wang pages 358 publisher No Starch Press rating 9 reviewer Peter Wayner ISBN 1593270003 summary An irreverant

The book is a travelog of many of the most interesting or inflammatory corners of the Internet. There are chapters on hacktivism, hate crime, con games, spam, phone phreaking and dozens of other topics. If someone's spent time flaming about it, banning it, subpoenaing it, or demonizing it, there's probably a section on it here. All of the sections come with screen shots and URLs for further digging.

I found reading the book to be an odd pleasure. There was no way to click on the sites or try any of the software without heading for a computer, but that didn't seem to matter. If anything, it was nice to skip over the links and put off heading down alternate paths until later. The more I experience books like this, the more I begin to wonder if there's much in the hyper-fragmented, postmodern view of a narrative built out of multiply forking paths. This book offers one fairly simple arc that carries us through the most talked about corners of the web and it does it fairly gracefully. That's a pleasure unto itself.

The book comes with a rebellious gloss and semiotic history. The title was stolen from Steal This Book a collection of anarchist schemes written by Abbie Hoffman in the 1960s. Despite the title, that book became a bestseller -- offering a glimpse of the longterm prospects for Hoffman's revolution. All of the prole sheep dutifully bought a book filled with bombmaking techniques that promises to show you where "exactly to place the dynamite that will destroy the walls."

Hoffman's book showed that people will buy something they value even when they're told to steal it. The prole sheep intuitively understand that books cost money to create. But maybe that was a different era, before the web existed. This website offers the text even though there are four editions for sale at Amazon. I wonder who holds the rights?

Wang's book is nowhere near as radical or as dangerous. Hoffman wrote sentences like "The purpose of part two is not to fuck the system, but destroy it." Wang generally avoids such antagonistic language and speaks generally about anti-social behavior in the third person: "When hackers use social engineering, they often masquerade as a consultant or temporary worker..."

Much of the book, in fact, is filled with techniques that are presented as tools for protecting your privacy and your personal information. The back cover asks, "Is your computer safe from computer viruses and malicious hackers?" It's only partially aimed at helping people do asocial things on the Net. Helping people protect themselves from the evil hordes is a large part of it. Given that identity theft is a booming business, this edition is practically an anti-crime book.

What does this mean for the this Internet revolution? Will the current file trading yippies overthrow the copyright system? Will file sharing actually become the norm? Or will all of the Napsterites follow the paths of Hoffman's proteges and grow up, have kids, move to the burbs, and start paying for their content? Well, they might if the content is as comfortable as this book in the hands while sitting in a La-Z-Boy recliner. No popup windows. No flash graphics. No registration required. Just pure content. Hmmm.

Peter Wayner is the author of books like Policing Online Games, Translucent Databases and Java RAMBO Manifesto. Please don't steal them. You can purchase Steal This Computer Book 3 from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Peter Wayner writes: "If you're looking for a quick way to test the difference between reading text online and reading it in a book, turn to Steal This Computer Book 3 by Wallace Wang, the third edition of a popular series that promises to tell you 'what they won't tell you about the Internet.' All of the information in the book can be gathered from Google for free, but the crisp writing, clean presentation and printed format make the book a good deal. It's possible to curl up in a chair out of WiFi range and cruise the best parts of the Internet without leaving a trail of cookies." Read on below for the rest of Peter's review -- it's free! Steal This Computer Book 3 author Wallace Wang pages 358 publisher No Starch Press rating 9 reviewer Peter Wayner ISBN 1593270003 summary An irreverant

The book is a travelog of many of the most interesting or inflammatory corners of the Internet. There are chapters on hacktivism, hate crime, con games, spam, phone phreaking and dozens of other topics. If someone's spent time flaming about it, banning it, subpoenaing it, or demonizing it, there's probably a section on it here. All of the sections come with screen shots and URLs for further digging.

I found reading the book to be an odd pleasure. There was no way to click on the sites or try any of the software without heading for a computer, but that didn't seem to matter. If anything, it was nice to skip over the links and put off heading down alternate paths until later. The more I experience books like this, the more I begin to wonder if there's much in the hyper-fragmented, postmodern view of a narrative built out of multiply forking paths. This book offers one fairly simple arc that carries us through the most talked about corners of the web and it does it fairly gracefully. That's a pleasure unto itself.

The book comes with a rebellious gloss and semiotic history. The title was stolen from Steal This Book a collection of anarchist schemes written by Abbie Hoffman in the 1960s. Despite the title, that book became a bestseller -- offering a glimpse of the longterm prospects for Hoffman's revolution. All of the prole sheep dutifully bought a book filled with bombmaking techniques that promises to show you where "exactly to place the dynamite that will destroy the walls."

Hoffman's book showed that people will buy something they value even when they're told to steal it. The prole sheep intuitively understand that books cost money to create. But maybe that was a different era, before the web existed. This website offers the text even though there are four editions for sale at Amazon. I wonder who holds the rights?

Wang's book is nowhere near as radical or as dangerous. Hoffman wrote sentences like "The purpose of part two is not to fuck the system, but destroy it." Wang generally avoids such antagonistic language and speaks generally about anti-social behavior in the third person: "When hackers use social engineering, they often masquerade as a consultant or temporary worker..."

Much of the book, in fact, is filled with techniques that are presented as tools for protecting your privacy and your personal information. The back cover asks, "Is your computer safe from computer viruses and malicious hackers?" It's only partially aimed at helping people do asocial things on the Net. Helping people protect themselves from the evil hordes is a large part of it. Given that identity theft is a booming business, this edition is practically an anti-crime book.

What does this mean for the this Internet revolution? Will the current file trading yippies overthrow the copyright system? Will file sharing actually become the norm? Or will all of the Napsterites follow the paths of Hoffman's proteges and grow up, have kids, move to the burbs, and start paying for their content? Well, they might if the content is as comfortable as this book in the hands while sitting in a La-Z-Boy recliner. No popup windows. No flash graphics. No registration required. Just pure content. Hmmm.

Peter Wayner is the author of books like Policing Online Games, Translucent Databases and Java RAMBO Manifesto. Please don't steal them. You can purchase Steal This Computer Book 3 from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Peter Wayner writes: "When I mentioned the Mad Scientist Club short stories to a co-worker, he rolled up his sleeve and showed me the burn scars on his arm. The books, he said, did this to him. Not literally, but by misguided inspiration. In one of the tales, the boys in the Club launch a fleet of fake flying saucers to frighten their hometown of Mamouth Falls. The scars came when the colleague tried to imitate the book, but used real gasoline to add a bit of zip to plastic cleaner bags turned UFOs. Now, that the rediscovered full-length novel about the Club, The Big Kerplop is being republished with a bit of a splash, some adults may look at stories like this and decided that there's a danger that kids might start imitating the novels. The bigger danger, though, may come if they don't." Read on for the rest of Peter's review. The Big Kerplop author Bertrand R. Brinley pages 217 publisher Purple House Press rating 9 reviewer Peter Wayner ISBN 1930900228 summary The Mad Scientists rediscovered, in greater depth -- fun reading for kids and adults.

This novel isn't really new, although it is for all practical purposes. The author, Bertrand Brinley, had much success with the collections of short stories about the seven boys who dreamed of being scientists one day. The short stories continued to stay in print and even seemed to inspire a hack Disney adaptation, but only rumors about The Big Kerplop circulated on the Internet. When the copies of The Big Kerplop would trade on Ebay, they often closed at prices in the hundreds of dollars. Free markets can't ignore messages like that and the Purple House Press purchased the rights and relaunched the books.

It's easy for a Slashdot reader to understand how the stories could command such affection. The boys in the stories live in the netherworld between capability and responsibility. (Enjoy it if you're still there.) They have ham radio sets, fishing boats, weather balloons, and plenty of other gadgets to put to use in tweaking the noses of their buffoonish elders and only a few chores to get in the way.

The books are set in the early 60's before Bhopal, Three Mile Island, and Agent Orange rained on the big Science parade. Brinley worked for Lockheed and Martin during one of the the most romantic periods in aviation history, save perhaps the early days of the Wright Brothers. The books are infused with a certainty that rational thought guided by the scientific method and salted with a bit of pluck and wit could solve any problem. I think everyone here can agree that the entire club would be open source coders today, although it's not clear if they would embrace the BSD or GPL license. It may not even be stretching things to say that groups who wrote and distributed DeCSS are working through the same themes as the Mad Scientist Club, albeit on a global scale.

The novel is prequel to the collection of short stories that tells the backstory of how the boys found each other and discovered how a firm devotion to scientific principles could be put to work showing up the grownups. As they say on Fark, hilarity ensued many times.

The earlier short stories took up only 20-30 pages apiece, but this novel stretches to more than 200 pages, making it an entirely different animal. The characters are better drawn, the scenes are set with more than a sentence or two, and the plot twists back upon itself a few times. It's a leisurely read that makes the earlier stories seem a bit cartoonish or slapstick. This sophistication is a pleasure for me to read at my technically grownup age, but it may be why the novel didn't gain the same traction as the short stories. The laughs are driven more by character and dialog than by the setting and action. The short stories are basically set pieces, but the novel is more of a study in character. That's good for anyone who grew up loving the books, but it may mean that the current crop of 8-12 year old boys should wait a year or two before diving in.

The length of the novel also gives Brinley more room to flesh out the adults and let them play more than rubes to the Mad Scientists' schemes. The town's politicians are still a bit overstuffed, but Colonel March, the commander of the local Air Force base, is hardly a foil or a nemisis. Constable Billy Dahr, though, is still around to be the goat.

I suppose I should say something about the story. The Club, or at least the early core of what would become the Club, is out fishing on Strawberry Lake when a fleet of B52s flies over. Something makes a big kerplop in the lake and the Club spends the rest of the book saving the day, defying their elders and deploying some cool gadgets and the scientific method. This is a deeper, richer and very satisfying return for the characters.

Some of these tricks could get you some scars I guess but that's not the worst future awaiting a young reader. First, chicks dig scars -- although that theorem lies well outside of the scope of this book. Second, this may be the adult in me, but kids today seem fatter, lazier, and more hogtied than ever before. Yes, these words will haunt me when my children get bigger, but I think that Brinley hits the sweet spot between obedience and irreverence. Forethought and care save the day in these books, not caprice and whim. The characters are neither insolent nor cowed by authority. The important thing to remember is that the scientific method celebrated by the books does not suggest replacing a few candles with a burning pie plate filled with gasoline. At least not without first doing a bit of research on the safest way to ensure all of the energy turns into hot air.

You can purchase The Big Kerplop from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page. Peter Wayner is the author of several dangerous and incendiary books like Disappearing Cryptography and Translucent Databases . Don't burn them without standing at a safe distance.

Peter Wayner writes: "When I mentioned the Mad Scientist Club short stories to a co-worker, he rolled up his sleeve and showed me the burn scars on his arm. The books, he said, did this to him. Not literally, but by misguided inspiration. In one of the tales, the boys in the Club launch a fleet of fake flying saucers to frighten their hometown of Mamouth Falls. The scars came when the colleague tried to imitate the book, but used real gasoline to add a bit of zip to plastic cleaner bags turned UFOs. Now, that the rediscovered full-length novel about the Club, The Big Kerplop is being republished with a bit of a splash, some adults may look at stories like this and decided that there's a danger that kids might start imitating the novels. The bigger danger, though, may come if they don't." Read on for the rest of Peter's review. The Big Kerplop author Bertrand R. Brinley pages 217 publisher Purple House Press rating 9 reviewer Peter Wayner ISBN 1930900228 summary The Mad Scientists rediscovered, in greater depth -- fun reading for kids and adults.

This novel isn't really new, although it is for all practical purposes. The author, Bertrand Brinley, had much success with the collections of short stories about the seven boys who dreamed of being scientists one day. The short stories continued to stay in print and even seemed to inspire a hack Disney adaptation, but only rumors about The Big Kerplop circulated on the Internet. When the copies of The Big Kerplop would trade on Ebay, they often closed at prices in the hundreds of dollars. Free markets can't ignore messages like that and the Purple House Press purchased the rights and relaunched the books.

It's easy for a Slashdot reader to understand how the stories could command such affection. The boys in the stories live in the netherworld between capability and responsibility. (Enjoy it if you're still there.) They have ham radio sets, fishing boats, weather balloons, and plenty of other gadgets to put to use in tweaking the noses of their buffoonish elders and only a few chores to get in the way.

The books are set in the early 60's before Bhopal, Three Mile Island, and Agent Orange rained on the big Science parade. Brinley worked for Lockheed and Martin during one of the the most romantic periods in aviation history, save perhaps the early days of the Wright Brothers. The books are infused with a certainty that rational thought guided by the scientific method and salted with a bit of pluck and wit could solve any problem. I think everyone here can agree that the entire club would be open source coders today, although it's not clear if they would embrace the BSD or GPL license. It may not even be stretching things to say that groups who wrote and distributed DeCSS are working through the same themes as the Mad Scientist Club, albeit on a global scale.

The novel is prequel to the collection of short stories that tells the backstory of how the boys found each other and discovered how a firm devotion to scientific principles could be put to work showing up the grownups. As they say on Fark, hilarity ensued many times.

The earlier short stories took up only 20-30 pages apiece, but this novel stretches to more than 200 pages, making it an entirely different animal. The characters are better drawn, the scenes are set with more than a sentence or two, and the plot twists back upon itself a few times. It's a leisurely read that makes the earlier stories seem a bit cartoonish or slapstick. This sophistication is a pleasure for me to read at my technically grownup age, but it may be why the novel didn't gain the same traction as the short stories. The laughs are driven more by character and dialog than by the setting and action. The short stories are basically set pieces, but the novel is more of a study in character. That's good for anyone who grew up loving the books, but it may mean that the current crop of 8-12 year old boys should wait a year or two before diving in.

The length of the novel also gives Brinley more room to flesh out the adults and let them play more than rubes to the Mad Scientists' schemes. The town's politicians are still a bit overstuffed, but Colonel March, the commander of the local Air Force base, is hardly a foil or a nemisis. Constable Billy Dahr, though, is still around to be the goat.

I suppose I should say something about the story. The Club, or at least the early core of what would become the Club, is out fishing on Strawberry Lake when a fleet of B52s flies over. Something makes a big kerplop in the lake and the Club spends the rest of the book saving the day, defying their elders and deploying some cool gadgets and the scientific method. This is a deeper, richer and very satisfying return for the characters.

Some of these tricks could get you some scars I guess but that's not the worst future awaiting a young reader. First, chicks dig scars -- although that theorem lies well outside of the scope of this book. Second, this may be the adult in me, but kids today seem fatter, lazier, and more hogtied than ever before. Yes, these words will haunt me when my children get bigger, but I think that Brinley hits the sweet spot between obedience and irreverence. Forethought and care save the day in these books, not caprice and whim. The characters are neither insolent nor cowed by authority. The important thing to remember is that the scientific method celebrated by the books does not suggest replacing a few candles with a burning pie plate filled with gasoline. At least not without first doing a bit of research on the safest way to ensure all of the energy turns into hot air.

You can purchase The Big Kerplop from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page. Peter Wayner is the author of several dangerous and incendiary books like Disappearing Cryptography and Translucent Databases . Don't burn them without standing at a safe distance.

Peter Wayner writes: "If you're a handicapped Windows user, Microsoft offers suggestions and assistance -- but XBox users were out of luck until Andrew 'Bunnie' Huang finished his book Hacking the XBox. Don't be fooled by the title. Officially, Huang's excellent book is not about helping the differently-abled. That would be against the law. Huang was forced by the DMCA to hide his humanitarianism under the cloak of 'reverse engineering' because this is one of the few legitimate uses given a small amount of protection by the law. But if you've got an urge to help the handicapped or any other reason to tinker with your XBox, buy this book before the Man sees through this ruse." Read on for the rest of Peter's review. Hacking the XBox author Andrew "Bunnie" Huang pages 288 publisher No Starch Press rating 9 reviewer Peter Wayner ISBN 1593270291 summary How and why to crack the seal on your Xbox.

There are many reasons why you might want to take apart your XBox, but one of the best ones I can imagine is making it easier for people who can't see, hear or move too well to play the same video games as the rest of us. Searching Microsoft's web site for documents containing both "handicapped" and "xbox" reveals only a suggestion for how to change the degree of difficulty of your Zoo Tycoon Game.

Someone who might want to retrofit a new pointing device or some other enabling gadget onto the XBox might start with the chapter describing how to fix a real USB cable onto the XBox. The chapter, like most in the book, is heavily illustrated with step-by-step pictures and instructions for clipping the cables in the right place and soldering them back together. Some of this might seem a bit rudimentary, but the detail can't hurt. In many cases, the real challenge is finding a way to take apart the case or the pack of wires in the right way. Smashing it isn't always an option. This is a book about mathematics, electronics, and taking apart plastic boxes.

Alas, just doing a bit of soldering isn't going to be enough unless you can make the right drivers. To help those who might want to reprogram their XBox, Huang devotes much of the book to stripping away the layers of the XBox security system, a story that is part mystery and part journey through the security layers in the system. The book is arranged in a very roughly chronological order. While it is mainly a book that teaches you how to reverse engineer the XBox, it is also a story of how he overcame the obstacles presented by the encryption. He talks as much about the unsuccessful paths as the ones that paid off. (This is, I think, an ideal model for the scientific community. It's much more educational than the terse papers that present the results as fait accompli.)

This part of the book quickly gets quite complicated, because Microsoft obviously tried hard to produce a secure machine that could provide a fair platform for people to play games. Getting the XBox to run any old software is not an easy task, but Huang describes several major techniques for drilling through the various layers of security. Again, he offers detailed pictures and instructions for construction special tools that snarf signals from a bus. Then he explains how he managed to grab the right keys for decrypting some of the most important data. Although it's a technical book, it unfolds like a spy novel.

The book is also very politically thoughtful. While the clueless will equate the word "hacking" in the title with piracy, money laundering, terrorism, and not phoning home on mother's day, Huang frames every step with a discussion of whether it is motivated by good or evil. He's not interested in building a tool to pirate XBox games and points out that many of the modifications aimed at running Linux on the Xbox do not help the pirates in any way. If anything, they make the games entirely unplayable.

Huang does want to defend the right to tinker, citing Ed Felten and others in a defense of something we're rapidly losing. I've heard horror stories from Army Majors about Windows PCs that refused to boot after failing to find a C drive. Do we really want to build machines that can't be retrofitted or fixed in the field? Many war movies are saved by the young private who (like Huang) is willing and able to tinker.

If you don't respond to pulls on the heartstrings, you might want to read one of the concluding chapters from the EFF's Lee Tien about the current legal climate. There are few exemptions for tinkering and many of them are limited. Reverse engineering is okay if you're a big corporation making a competing product, but that didn't help 2600 magazine when they were accused of trying to help people view DVDs on their Linux machine. I can only imagine what they would do to someone with very bad vision who wanted to enable a special zoom feature on their Xbox.

The book was originally going to be published by Wiley, but the company balked when it realized there were stiff legal penalties for helping handicapped people use computers. Even the Massachusetts Institute of Technology felt that it would be better for Huang to disassociate itself from Huang and his humanitarian efforts. The university only relented after pressure from a few good professors who helped the university understand the value in Huang's mission. Huang decided to publish the book himself with the help of his girlfriend, Nikki Justis. The two of them should be commended for turning out such a beautiful, professional book. If you're intrigued by the xbox, interested in helping the handicapped, or just trying to learn how to reverse engineer things before things get worse, check out this book. It's a wonderful contribution to the literature.

To close, I'm offering a pair of cool projects with the hope that Huang's book will inspire people to tinker:

• Sonic Information -- The sound in games like Quake is pretty good, but what if it was rendered with enough precision to let blind people grok the scene? The echoes from the tapping of a white cane already carry plenty of information to the blind. What if they could compete on an equal footing with the sighted? Who would win?
• Eye Movement Measuring tools -- Tools exist for sensing the position of our eyes. A quadriplegic game could just look in the right direction and shoot. Clearly some work would need to be done to encode all of the shift-left-left-down-right maneuvers from the games. This could help all of us. The thumb you save from repetitive motion injuries could be your own.

Note: Since this review was written, Hacking the Xbox has found a publisher in the form of No Starch Press. The original self-published version will probably be a sought-after collectable ;)

Peter Wayner is the author of Translucent Databases and ten other books. None rely on the DMCA. Hacking the Xbox is due in July at bn.com; you can also go directly to the book's page at No Starch Press. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Peter Wayner writes: "If you're a handicapped Windows user, Microsoft offers suggestions and assistance -- but XBox users were out of luck until Andrew 'Bunnie' Huang finished his book Hacking the XBox. Don't be fooled by the title. Officially, Huang's excellent book is not about helping the differently-abled. That would be against the law. Huang was forced by the DMCA to hide his humanitarianism under the cloak of 'reverse engineering' because this is one of the few legitimate uses given a small amount of protection by the law. But if you've got an urge to help the handicapped or any other reason to tinker with your XBox, buy this book before the Man sees through this ruse." Read on for the rest of Peter's review. Hacking the XBox author Andrew "Bunnie" Huang pages 288 publisher No Starch Press rating 9 reviewer Peter Wayner ISBN 1593270291 summary How and why to crack the seal on your Xbox.

There are many reasons why you might want to take apart your XBox, but one of the best ones I can imagine is making it easier for people who can't see, hear or move too well to play the same video games as the rest of us. Searching Microsoft's web site for documents containing both "handicapped" and "xbox" reveals only a suggestion for how to change the degree of difficulty of your Zoo Tycoon Game.

Someone who might want to retrofit a new pointing device or some other enabling gadget onto the XBox might start with the chapter describing how to fix a real USB cable onto the XBox. The chapter, like most in the book, is heavily illustrated with step-by-step pictures and instructions for clipping the cables in the right place and soldering them back together. Some of this might seem a bit rudimentary, but the detail can't hurt. In many cases, the real challenge is finding a way to take apart the case or the pack of wires in the right way. Smashing it isn't always an option. This is a book about mathematics, electronics, and taking apart plastic boxes.

Alas, just doing a bit of soldering isn't going to be enough unless you can make the right drivers. To help those who might want to reprogram their XBox, Huang devotes much of the book to stripping away the layers of the XBox security system, a story that is part mystery and part journey through the security layers in the system. The book is arranged in a very roughly chronological order. While it is mainly a book that teaches you how to reverse engineer the XBox, it is also a story of how he overcame the obstacles presented by the encryption. He talks as much about the unsuccessful paths as the ones that paid off. (This is, I think, an ideal model for the scientific community. It's much more educational than the terse papers that present the results as fait accompli.)

This part of the book quickly gets quite complicated, because Microsoft obviously tried hard to produce a secure machine that could provide a fair platform for people to play games. Getting the XBox to run any old software is not an easy task, but Huang describes several major techniques for drilling through the various layers of security. Again, he offers detailed pictures and instructions for construction special tools that snarf signals from a bus. Then he explains how he managed to grab the right keys for decrypting some of the most important data. Although it's a technical book, it unfolds like a spy novel.

The book is also very politically thoughtful. While the clueless will equate the word "hacking" in the title with piracy, money laundering, terrorism, and not phoning home on mother's day, Huang frames every step with a discussion of whether it is motivated by good or evil. He's not interested in building a tool to pirate XBox games and points out that many of the modifications aimed at running Linux on the Xbox do not help the pirates in any way. If anything, they make the games entirely unplayable.

Huang does want to defend the right to tinker, citing Ed Felten and others in a defense of something we're rapidly losing. I've heard horror stories from Army Majors about Windows PCs that refused to boot after failing to find a C drive. Do we really want to build machines that can't be retrofitted or fixed in the field? Many war movies are saved by the young private who (like Huang) is willing and able to tinker.

If you don't respond to pulls on the heartstrings, you might want to read one of the concluding chapters from the EFF's Lee Tien about the current legal climate. There are few exemptions for tinkering and many of them are limited. Reverse engineering is okay if you're a big corporation making a competing product, but that didn't help 2600 magazine when they were accused of trying to help people view DVDs on their Linux machine. I can only imagine what they would do to someone with very bad vision who wanted to enable a special zoom feature on their Xbox.

The book was originally going to be published by Wiley, but the company balked when it realized there were stiff legal penalties for helping handicapped people use computers. Even the Massachusetts Institute of Technology felt that it would be better for Huang to disassociate itself from Huang and his humanitarian efforts. The university only relented after pressure from a few good professors who helped the university understand the value in Huang's mission. Huang decided to publish the book himself with the help of his girlfriend, Nikki Justis. The two of them should be commended for turning out such a beautiful, professional book. If you're intrigued by the xbox, interested in helping the handicapped, or just trying to learn how to reverse engineer things before things get worse, check out this book. It's a wonderful contribution to the literature.

To close, I'm offering a pair of cool projects with the hope that Huang's book will inspire people to tinker:

• Sonic Information -- The sound in games like Quake is pretty good, but what if it was rendered with enough precision to let blind people grok the scene? The echoes from the tapping of a white cane already carry plenty of information to the blind. What if they could compete on an equal footing with the sighted? Who would win?
• Eye Movement Measuring tools -- Tools exist for sensing the position of our eyes. A quadriplegic game could just look in the right direction and shoot. Clearly some work would need to be done to encode all of the shift-left-left-down-right maneuvers from the games. This could help all of us. The thumb you save from repetitive motion injuries could be your own.

Note: Since this review was written, Hacking the Xbox has found a publisher in the form of No Starch Press. The original self-published version will probably be a sought-after collectable ;)

Peter Wayner is the author of Translucent Databases and ten other books. None rely on the DMCA. Hacking the Xbox is due in July at bn.com; you can also go directly to the book's page at No Starch Press. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

peterwayner writes "If you're looking for more proof that good stories happen to those who can tell them, pick up a copy of James McManus's Positively Fifth Street, an adrenaline-charged, first person account of a reporter sent to cover the World Series of Poker in Las Vegas. But why sit on the sidelines? He decides the only way to capture the true flavor is to risk his advance and enter. Along the way, he uses his journalistic license to justify trips to strip clubs, interviews with all of the female players, examinations of the ex-stripper wife of the tournament host, investigations of a murder, and winning bigger and bigger bets at the poker table." Sounds like fun. Read on for the rest of the review. Positively Fifth Street: Murderers, Cheetahs, and Binion's World Series of Poker author James McManus pages 416 publisher Farrar, Straus and Giroux rating 8 reviewer Peter Wayner ISBN 0374236488 summary Journalist enters poker tournament.

This book is a bit of an oddity in the literature of poker, a subject that McManus teaches along with creative writing at the School of the Art Institute of Chicago. Most of the books in the field are manuals designed to teach a beginning player how to calculate the odds, bluff at the right time, and size up the rivals. The books may be informative and helpful, but the largely clinical approach does little for the casual reader.

McManus doesn't bother much with the rules of the game because he's out to explore the nexus of lust, competition and desire that gives Las Vegas such a hold on the human undersoul. To ensure that no one mistakes this for a traditional poker book, he opens with a sex-and-drug-saturated rendition of the murder of Ted Binion, one of the owners of the casino that sponsors the poker tournament each year. None of the wealth begat by poker helped Binion after he had the misfortune to marry the one ex-stripper who would later face murder charges for his death.

Despite witnessing the pain and agony visited by the money upon Binion, McManus still can't resist chasing after his share in the tournament. He has four kids to take care of and his wife is home clipping coupons. Sure, he could just write about the tournament and play it safe, but wouldn't it make sense to enter just to get a feel of it? And gosh, if he wins, he could really pay down that mortgage. Bad Jim, as he calls himself, thinks it makes perfect sense and grabs some poker software for practice.

Bad Jim has plenty of other journalistic rationalizations up his sleeve. Some of the book is devoted to his interviews with female poker players, a relatively rarity with the politically correct power to trump any complaint that this is just a thinly veiled excuse to leave the kids at home and play poker. This angle reaches a humorous climax when he finds himself in a showdown against one female and confesses, "no one wants this woman to win the event more than I do, just not this pot."

A queen on the board means that the woman wins, "paying Bad Jim back personally for two hundred years of poker domination by men, plus millions of years of the other kind." Any other card lets Good Jim take home the cash to support his wife and daughters. Who will win, Politically Correct Jim or Old School Jim?

The book is a seemingly endless stream of these confrontations where the action on the tables reflects a tension between our high-toned aspirations and baser human longings. There are plenty of learned allusions to remind us that he does teach writing at a fancy college, but they are mixed into a narrative driven by sex and greed. Has evolution given us a need for competition and battles to the death? Is poker a good substitute now that we're more civilized? Has the poker prep software given nerds and geeks an edge over the "leather-assed Texas road gamblers?"

His seemingly endless good fortune and his ability to string the conflicts into a story with various remain the strength of the book. He just can't seem to lose. And this is a good thing because the jury in the Binion murder trial is taking forever to make up its mind. Something needs to keep the tension building and Bad Jim's good luck delivers.

So he manages to string us along for almost 400 pages until we find out who wins the tournament and whether Binion's wife goes to jail. It's a terrific exploration of power, sex and death boiled into one short visit to Las Vegas. It's even better if you love poker because the endless descriptions of the hands must be a bit hard on those who don't see the fun in sitting around a smoky hall dealing cards. If you do, though, this is a wonderful read.

Peter Wayner is the author of Translucent Databases and Disappearing Cryptography. You can purchase Positively Fifth Street from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

peterwayner writes "If you're looking for more proof that good stories happen to those who can tell them, pick up a copy of James McManus's Positively Fifth Street, an adrenaline-charged, first person account of a reporter sent to cover the World Series of Poker in Las Vegas. But why sit on the sidelines? He decides the only way to capture the true flavor is to risk his advance and enter. Along the way, he uses his journalistic license to justify trips to strip clubs, interviews with all of the female players, examinations of the ex-stripper wife of the tournament host, investigations of a murder, and winning bigger and bigger bets at the poker table." Sounds like fun. Read on for the rest of the review. Positively Fifth Street: Murderers, Cheetahs, and Binion's World Series of Poker author James McManus pages 416 publisher Farrar, Straus and Giroux rating 8 reviewer Peter Wayner ISBN 0374236488 summary Journalist enters poker tournament.

This book is a bit of an oddity in the literature of poker, a subject that McManus teaches along with creative writing at the School of the Art Institute of Chicago. Most of the books in the field are manuals designed to teach a beginning player how to calculate the odds, bluff at the right time, and size up the rivals. The books may be informative and helpful, but the largely clinical approach does little for the casual reader.

McManus doesn't bother much with the rules of the game because he's out to explore the nexus of lust, competition and desire that gives Las Vegas such a hold on the human undersoul. To ensure that no one mistakes this for a traditional poker book, he opens with a sex-and-drug-saturated rendition of the murder of Ted Binion, one of the owners of the casino that sponsors the poker tournament each year. None of the wealth begat by poker helped Binion after he had the misfortune to marry the one ex-stripper who would later face murder charges for his death.

Despite witnessing the pain and agony visited by the money upon Binion, McManus still can't resist chasing after his share in the tournament. He has four kids to take care of and his wife is home clipping coupons. Sure, he could just write about the tournament and play it safe, but wouldn't it make sense to enter just to get a feel of it? And gosh, if he wins, he could really pay down that mortgage. Bad Jim, as he calls himself, thinks it makes perfect sense and grabs some poker software for practice.

Bad Jim has plenty of other journalistic rationalizations up his sleeve. Some of the book is devoted to his interviews with female poker players, a relatively rarity with the politically correct power to trump any complaint that this is just a thinly veiled excuse to leave the kids at home and play poker. This angle reaches a humorous climax when he finds himself in a showdown against one female and confesses, "no one wants this woman to win the event more than I do, just not this pot."

A queen on the board means that the woman wins, "paying Bad Jim back personally for two hundred years of poker domination by men, plus millions of years of the other kind." Any other card lets Good Jim take home the cash to support his wife and daughters. Who will win, Politically Correct Jim or Old School Jim?

The book is a seemingly endless stream of these confrontations where the action on the tables reflects a tension between our high-toned aspirations and baser human longings. There are plenty of learned allusions to remind us that he does teach writing at a fancy college, but they are mixed into a narrative driven by sex and greed. Has evolution given us a need for competition and battles to the death? Is poker a good substitute now that we're more civilized? Has the poker prep software given nerds and geeks an edge over the "leather-assed Texas road gamblers?"

His seemingly endless good fortune and his ability to string the conflicts into a story with various remain the strength of the book. He just can't seem to lose. And this is a good thing because the jury in the Binion murder trial is taking forever to make up its mind. Something needs to keep the tension building and Bad Jim's good luck delivers.

So he manages to string us along for almost 400 pages until we find out who wins the tournament and whether Binion's wife goes to jail. It's a terrific exploration of power, sex and death boiled into one short visit to Las Vegas. It's even better if you love poker because the endless descriptions of the hands must be a bit hard on those who don't see the fun in sitting around a smoky hall dealing cards. If you do, though, this is a wonderful read.

Peter Wayner is the author of Translucent Databases and Disappearing Cryptography. You can purchase Positively Fifth Street from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

peterwayner writes "One mathematician I know told me that the most important lesson he learned was how to read a math book. It did no good, he said, to just start plowing through the theorems because that brought confusion. The key was to skim the book five or six times to get an idea of what the writer was trying to do. Then, and only then, was it possible to figure out the equations. This is what Barry Mazur tries to do in his book Imagining Numbers . There are some equations, graphs and diagrams, but first and foremost he offers plenty of poetry, philosophy and history to lay a foundation for understanding imaginary numbers." Peter's review continues below -- despite its complicated, abstract subject matter, he says that it's "simple enough to be accessible to most who will be interested in it." Imagining Numbers author Barry Mazur pages 267 publisher Farrar, Straus and Giroux rating 8 reviewer Peter Wayner ISBN 0374174695 summary How to imagine imaginary numbers like the square root of minus fifteen.

Much of modern mathematical literature is structured with crisp, scripted precision. First there is theorem one, then theorem two, which leads to theorem three, which could only be followed by theorem four, and so on until we reach theorem n. If you want to learn the mathematics of complex numbers (a +bi), then classic texts (this or this) will get you there.

Some may like this logical progression, but it leaves others cold in the same way that crisp, modern architecture by Mies van de Rohe leaves some craving a more layered, fractured, ornate, organic and just plain fun place to live and work. Less isn't more, as Robert Venturi said, less is a bore.

If you happen to feel a chill when churning through an assembly line of theorems, you might enjoy the treatment of Mazur, a professor at Harvard who seems to spend as much time reading poets like Rilke or Stevens as he does examining old mathematical texts. Mazur is not the kind of machine that turns coffee into theorems-- he's too busy stopping to smell the rhetorical flourishes.

The book isn't aimed at mathematicians per se. The publisher, Farrar, Strauss and Giroux specializes in mainstream literature and that's probably the best pigeonhole for this book. Mazur wants the reader to understand how to think about imaginary numbers, not evaluate some integrals -- and that reader could really be anyone with the desire to think about mathematical things. The book is simple enough to be accessible to most who will be interested in it.

In many ways, Mazur attempted a much harder task than just teaching complex analysis. It's one thing to learn how to find the roots of polynomials, but it's another thing to try to help people get a feeling or an intuition for the square root of minus fifteen. Integers are easy to understand and even feel by counting out things, but imaginary numbers don't seem to exist. Mathematicians have spent many years trying to find the best metaphors and structures to understand how to find answers for all polynomials and it's never been an easy struggle.

The best part of the book is, without doubt, the historical treatment of how other mathematicians confronted the question of irrational and complex numbers. These ideas have always been hard to grasp and it took time to evolve the most compact and consistent nomenclature.

If you're interested in mathematics as more than just a mechanism that churns out answers, you'll probably enjoy the book. It's a light, friendly, philosophical expedition looking for a way to make imaginary numbers work in our minds.

Peter Wayner is the author of Translucent Databases , a book on how to imagine databases that hold no information yet still do useful work. You can purchase Imagining Numbers from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

peterwayner writes "One mathematician I know told me that the most important lesson he learned was how to read a math book. It did no good, he said, to just start plowing through the theorems because that brought confusion. The key was to skim the book five or six times to get an idea of what the writer was trying to do. Then, and only then, was it possible to figure out the equations. This is what Barry Mazur tries to do in his book Imagining Numbers . There are some equations, graphs and diagrams, but first and foremost he offers plenty of poetry, philosophy and history to lay a foundation for understanding imaginary numbers." Peter's review continues below -- despite its complicated, abstract subject matter, he says that it's "simple enough to be accessible to most who will be interested in it." Imagining Numbers author Barry Mazur pages 267 publisher Farrar, Straus and Giroux rating 8 reviewer Peter Wayner ISBN 0374174695 summary How to imagine imaginary numbers like the square root of minus fifteen.

Much of modern mathematical literature is structured with crisp, scripted precision. First there is theorem one, then theorem two, which leads to theorem three, which could only be followed by theorem four, and so on until we reach theorem n. If you want to learn the mathematics of complex numbers (a +bi), then classic texts (this or this) will get you there.

Some may like this logical progression, but it leaves others cold in the same way that crisp, modern architecture by Mies van de Rohe leaves some craving a more layered, fractured, ornate, organic and just plain fun place to live and work. Less isn't more, as Robert Venturi said, less is a bore.

If you happen to feel a chill when churning through an assembly line of theorems, you might enjoy the treatment of Mazur, a professor at Harvard who seems to spend as much time reading poets like Rilke or Stevens as he does examining old mathematical texts. Mazur is not the kind of machine that turns coffee into theorems-- he's too busy stopping to smell the rhetorical flourishes.

The book isn't aimed at mathematicians per se. The publisher, Farrar, Strauss and Giroux specializes in mainstream literature and that's probably the best pigeonhole for this book. Mazur wants the reader to understand how to think about imaginary numbers, not evaluate some integrals -- and that reader could really be anyone with the desire to think about mathematical things. The book is simple enough to be accessible to most who will be interested in it.

In many ways, Mazur attempted a much harder task than just teaching complex analysis. It's one thing to learn how to find the roots of polynomials, but it's another thing to try to help people get a feeling or an intuition for the square root of minus fifteen. Integers are easy to understand and even feel by counting out things, but imaginary numbers don't seem to exist. Mathematicians have spent many years trying to find the best metaphors and structures to understand how to find answers for all polynomials and it's never been an easy struggle.

The best part of the book is, without doubt, the historical treatment of how other mathematicians confronted the question of irrational and complex numbers. These ideas have always been hard to grasp and it took time to evolve the most compact and consistent nomenclature.

If you're interested in mathematics as more than just a mechanism that churns out answers, you'll probably enjoy the book. It's a light, friendly, philosophical expedition looking for a way to make imaginary numbers work in our minds.

Peter Wayner is the author of Translucent Databases , a book on how to imagine databases that hold no information yet still do useful work. You can purchase Imagining Numbers from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Luke Francl writes "On December 16, the Creative Commons is unveiling their commons licenses. Well, their website is up a little early Creative Commons provides an easy way for creators to give away some of their rights under copyright law without wading through hundreds of pages debating the merits of the GPL verus the OPL versus the FDL verus the public domain ad infinitum. By answering three simple questions, the Creative Commons web application selects an appropriate license for you. You can give it a try at the Choose a License page. They've also got a list of all the Creative Commons licenses." Peter Wayner has released his book Free For All under the license.

Peter Wayner writes "The book Creating Applications with Mozilla did not set out to capture the essence of modern open source software development in a few hundred pages, but it comes closer to that unreachable goal than almost any other book I can imagine. Everything is there: the proliferation of acronyms, the funky names, the endless layers, the earnest collaboration, the unstoppable yearning for customizability, and, of course, plenty of source code. The book is just supposed to be teaching us how to turn Mozilla into a front end for everything, but it's really a distilled exhibit of all that is hip and now in code creation." Peter's review continues below. Creating Applications with Mozilla author David Boswell, Brian King, Ian Oeschger, Pete Collins & Eric Murphy pages 454 publisher O'Reilly rating 9 reviewer Peter Wayner ISBN 0596000529 summary How to use the Mozilla APIs to do anything.

On the first and most obvious level, the book is just the typical, thorough treatment of the important APIs that we've come to expect from O'Reilly. There are chapters addressing all of the important layers of the Mozilla platform and plenty of examples that show you how to customize the platform. Some may want to change the icons and others may want to add more robust features. The range of possibilities is surprising and coders are creating one-to-one communications enhancements, add-on widgets, and even games. There are certainly some things missing, and some areas that could use more detail or more complicated examples, but the book is already 454 pages long.

On another level, this book is also one of the first finished documents that explains what the Mozilla group has really been up to for the past five years. Some have abandoned the project, and others have attacked it as fundamentally misguided. This book shows why it took so long by demonstrating all of the cool features added during the long march to a new, thoroughly extensible architecture.

Are the results enough to justify the time and the effort? Some note that the features may be a bit overhyped, because building your own browser with the Mozilla API is like making a pizza with $15 and a telephone. While there's a large part of the book devoted to the work you can do to change the look and feel of the buttons on your browser, the book and the project offer much more. The Mozilla project is one of the biggest threats to simple tools like Visual Basic to come down the pike in some time. The various layers offer many ways to provide good, customizable interfaces to databases, the web, and much more. I can see how many corporate development shops may want to start making Mozilla the platform for a license-free front-end, simply because it's a straightforward tool without extra costs or restrictions.

At the most abstract level, the book is a great way to get a taste of modern software development. Computer scientists sometimes fix problems by adding more and more layers of indirection. This may not solve anything, but at least there are hooks for a real solution to use some time in the future if some one ever does figure out how to make the box do it. The Mozilla browser is one of the most extreme examples of this philosophy to ever emerge. Emacs was something special, but this is even more insane. Everything can be changed around by rewriting some XML and Javascript and most people don't need to juggle the pointers in grubby C to do amazing things. I realize it's not as beautiful as Lisp to some, but it's got a clarity and level of abstraction that's stunning to behold. Lisp was just procedural, while XML is more like logic programming.

This relentless customizability embodies one of the deepest reasons for the success of open source. Technology is inherently complicated and the only way we can use it is if we can look under the hood. You can say all you want about CVS trees and bazaars filled with competing code, but opening up the interface is one of the most powerful themes of open source. It's not about teaching people to build their own VCR or PVR from scratch, getting the VCRs for free or even debugging the VCR's source code -- it's just about making them easy enough to program.

The book illustrates how Mozilla opens up the API to create a relatively easy language for people to use. The real open source is not the C in the tar ball, but the XML interface spelled out in the book. Many people feel that the most important thing that the first browser designers did was make it easy for people to see the HTML tags marking up the document in front of them. The new Mozilla takes this transparency to a new high.

If you look at the book at all of these levels, you can see that this is one of the most important documents to emerge from the open source community in some time. At first glance, it's just another set of APIs for us to wiggle. I realize it's not fair to credit the Mozilla team or the book authors with creating the browser or XML ex nihilio -- they just jumped on some of the most popular bitwagons propagating across the Net. But the result is a stunning completion of a very important and cohesive vision. The book doesn't crackle with bleeding-edge novelty, but shines with the certainty of a job well-done.

Peter Wayner is the author of Translucent Databases , Disappearing Cryptography , and a number of other books. You can purchase Creating Applications with Mozilla from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Peter Wayner writes "The book Creating Applications with Mozilla did not set out to capture the essence of modern open source software development in a few hundred pages, but it comes closer to that unreachable goal than almost any other book I can imagine. Everything is there: the proliferation of acronyms, the funky names, the endless layers, the earnest collaboration, the unstoppable yearning for customizability, and, of course, plenty of source code. The book is just supposed to be teaching us how to turn Mozilla into a front end for everything, but it's really a distilled exhibit of all that is hip and now in code creation." Peter's review continues below. Creating Applications with Mozilla author David Boswell, Brian King, Ian Oeschger, Pete Collins & Eric Murphy pages 454 publisher O'Reilly rating 9 reviewer Peter Wayner ISBN 0596000529 summary How to use the Mozilla APIs to do anything.

On the first and most obvious level, the book is just the typical, thorough treatment of the important APIs that we've come to expect from O'Reilly. There are chapters addressing all of the important layers of the Mozilla platform and plenty of examples that show you how to customize the platform. Some may want to change the icons and others may want to add more robust features. The range of possibilities is surprising and coders are creating one-to-one communications enhancements, add-on widgets, and even games. There are certainly some things missing, and some areas that could use more detail or more complicated examples, but the book is already 454 pages long.

On another level, this book is also one of the first finished documents that explains what the Mozilla group has really been up to for the past five years. Some have abandoned the project, and others have attacked it as fundamentally misguided. This book shows why it took so long by demonstrating all of the cool features added during the long march to a new, thoroughly extensible architecture.

Are the results enough to justify the time and the effort? Some note that the features may be a bit overhyped, because building your own browser with the Mozilla API is like making a pizza with $15 and a telephone. While there's a large part of the book devoted to the work you can do to change the look and feel of the buttons on your browser, the book and the project offer much more. The Mozilla project is one of the biggest threats to simple tools like Visual Basic to come down the pike in some time. The various layers offer many ways to provide good, customizable interfaces to databases, the web, and much more. I can see how many corporate development shops may want to start making Mozilla the platform for a license-free front-end, simply because it's a straightforward tool without extra costs or restrictions.

At the most abstract level, the book is a great way to get a taste of modern software development. Computer scientists sometimes fix problems by adding more and more layers of indirection. This may not solve anything, but at least there are hooks for a real solution to use some time in the future if some one ever does figure out how to make the box do it. The Mozilla browser is one of the most extreme examples of this philosophy to ever emerge. Emacs was something special, but this is even more insane. Everything can be changed around by rewriting some XML and Javascript and most people don't need to juggle the pointers in grubby C to do amazing things. I realize it's not as beautiful as Lisp to some, but it's got a clarity and level of abstraction that's stunning to behold. Lisp was just procedural, while XML is more like logic programming.

This relentless customizability embodies one of the deepest reasons for the success of open source. Technology is inherently complicated and the only way we can use it is if we can look under the hood. You can say all you want about CVS trees and bazaars filled with competing code, but opening up the interface is one of the most powerful themes of open source. It's not about teaching people to build their own VCR or PVR from scratch, getting the VCRs for free or even debugging the VCR's source code -- it's just about making them easy enough to program.

The book illustrates how Mozilla opens up the API to create a relatively easy language for people to use. The real open source is not the C in the tar ball, but the XML interface spelled out in the book. Many people feel that the most important thing that the first browser designers did was make it easy for people to see the HTML tags marking up the document in front of them. The new Mozilla takes this transparency to a new high.

If you look at the book at all of these levels, you can see that this is one of the most important documents to emerge from the open source community in some time. At first glance, it's just another set of APIs for us to wiggle. I realize it's not fair to credit the Mozilla team or the book authors with creating the browser or XML ex nihilio -- they just jumped on some of the most popular bitwagons propagating across the Net. But the result is a stunning completion of a very important and cohesive vision. The book doesn't crackle with bleeding-edge novelty, but shines with the certainty of a job well-done.

Peter Wayner is the author of Translucent Databases , Disappearing Cryptography , and a number of other books. You can purchase Creating Applications with Mozilla from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Peter Wayner writes "The book Creating Applications with Mozilla did not set out to capture the essence of modern open source software development in a few hundred pages, but it comes closer to that unreachable goal than almost any other book I can imagine. Everything is there: the proliferation of acronyms, the funky names, the endless layers, the earnest collaboration, the unstoppable yearning for customizability, and, of course, plenty of source code. The book is just supposed to be teaching us how to turn Mozilla into a front end for everything, but it's really a distilled exhibit of all that is hip and now in code creation." Peter's review continues below. Creating Applications with Mozilla author David Boswell, Brian King, Ian Oeschger, Pete Collins & Eric Murphy pages 454 publisher O'Reilly rating 9 reviewer Peter Wayner ISBN 0596000529 summary How to use the Mozilla APIs to do anything.

On the first and most obvious level, the book is just the typical, thorough treatment of the important APIs that we've come to expect from O'Reilly. There are chapters addressing all of the important layers of the Mozilla platform and plenty of examples that show you how to customize the platform. Some may want to change the icons and others may want to add more robust features. The range of possibilities is surprising and coders are creating one-to-one communications enhancements, add-on widgets, and even games. There are certainly some things missing, and some areas that could use more detail or more complicated examples, but the book is already 454 pages long.

On another level, this book is also one of the first finished documents that explains what the Mozilla group has really been up to for the past five years. Some have abandoned the project, and others have attacked it as fundamentally misguided. This book shows why it took so long by demonstrating all of the cool features added during the long march to a new, thoroughly extensible architecture.

Are the results enough to justify the time and the effort? Some note that the features may be a bit overhyped, because building your own browser with the Mozilla API is like making a pizza with $15 and a telephone. While there's a large part of the book devoted to the work you can do to change the look and feel of the buttons on your browser, the book and the project offer much more. The Mozilla project is one of the biggest threats to simple tools like Visual Basic to come down the pike in some time. The various layers offer many ways to provide good, customizable interfaces to databases, the web, and much more. I can see how many corporate development shops may want to start making Mozilla the platform for a license-free front-end, simply because it's a straightforward tool without extra costs or restrictions.

At the most abstract level, the book is a great way to get a taste of modern software development. Computer scientists sometimes fix problems by adding more and more layers of indirection. This may not solve anything, but at least there are hooks for a real solution to use some time in the future if some one ever does figure out how to make the box do it. The Mozilla browser is one of the most extreme examples of this philosophy to ever emerge. Emacs was something special, but this is even more insane. Everything can be changed around by rewriting some XML and Javascript and most people don't need to juggle the pointers in grubby C to do amazing things. I realize it's not as beautiful as Lisp to some, but it's got a clarity and level of abstraction that's stunning to behold. Lisp was just procedural, while XML is more like logic programming.

This relentless customizability embodies one of the deepest reasons for the success of open source. Technology is inherently complicated and the only way we can use it is if we can look under the hood. You can say all you want about CVS trees and bazaars filled with competing code, but opening up the interface is one of the most powerful themes of open source. It's not about teaching people to build their own VCR or PVR from scratch, getting the VCRs for free or even debugging the VCR's source code -- it's just about making them easy enough to program.

The book illustrates how Mozilla opens up the API to create a relatively easy language for people to use. The real open source is not the C in the tar ball, but the XML interface spelled out in the book. Many people feel that the most important thing that the first browser designers did was make it easy for people to see the HTML tags marking up the document in front of them. The new Mozilla takes this transparency to a new high.

If you look at the book at all of these levels, you can see that this is one of the most important documents to emerge from the open source community in some time. At first glance, it's just another set of APIs for us to wiggle. I realize it's not fair to credit the Mozilla team or the book authors with creating the browser or XML ex nihilio -- they just jumped on some of the most popular bitwagons propagating across the Net. But the result is a stunning completion of a very important and cohesive vision. The book doesn't crackle with bleeding-edge novelty, but shines with the certainty of a job well-done.

Peter Wayner is the author of Translucent Databases , Disappearing Cryptography , and a number of other books. You can purchase Creating Applications with Mozilla from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Peter Wayner writes: "If you're one of the last few who believe that the numbers on your portfolio statement are any more permanent than a spring day, a sun tan, or a wink in a bar, you may want to tune into John Motavalli's new book, Bamboozled At the Revolution: How Big Media Lost Billions in the Battle for the Internet. The book follows the stumbling attempt by the old school in the media to turn their so-called power into dominance over the new domain. Numbers fly back and forth. Executives fret over turf. Dreams of glory float skywards. Yet in the end, it's just as Ecclesiastes warned: 'All are of the dust, and all turn to dust again.'" Read on below. Bamboozled at the Revolution: How Big Media Lost Billions in the Battle for the Internet author John Motavalli pages 334 publisher Viking rating 7.0 reviewer Peter Wayner ISBN 0670899801 summary Stories from the big media boardrooms and their quest to extend their dominance.

The book is an inside tale told by an insider who chronicles the frantic days when the insiders were certain that the Internet was going to change everything. In this case, the insiders were the golden boys at media conglomerates who managed through some mixture of luck, devotion, and talent to control the worlds of cable television, newspapers, magazines, and movies. In the mid 1990's, the Internet threatened to overturn their world when they realized that anyone could set up a website, turn a bedroom into a corner office, and join the media. One minute some Mom in NJ is burning spaghetti sauce, the next minute Madonna is coming over for a chat on her weblog.

Reading the book is an ideal way for Slashdot readers to stick their nose into the exclusive tent filled with media moguls. The book does an ideal job of conveying the NY mindset that the world is made up of billions of sheep just waiting for the media to tell them how to bleat. When the Internet threatens to lure some of the flock, the big guys with the big corner offices start writing checks hoping to find a way to own a piece of it.

The book is played out chronologically and begins with Time-Warner's desire to build a full-service, interactive cable system in 1993. The final epilog was probably written in April and it's already a bit dated because it went to press before the accounting upheaval at AOL. In between, the executives of the big media companies struggle to find an Internet strategy-- something that never really gels for anyone.

Motavalli documents the progression with details that matter to media executives. We learn where people went to college (Haverford, Harvard), where they ate dinner (City Grill, "a gross strip mall" in Vienna, VA that serves great pizza,), the names of their yachts (Highlander), if their offices were big (yes), and if they got along (no). All of the executives in this book are always getting irked, losing confidence, chafing at some new org chart, or jettisoning some division.

Nothing seems to work for these guys. They try merging with each other; they try pop-up ads; and they try building portals. Yet through it all, the value of advertising just keeps dropping. The more time people spend on-line, the more page views they create. That means, more viewers mean lower ad prices. Uh-oh. The law of supply and demand seems to insist that success only begets failure. How are people going to make money on-line? We may never know, because nothing except the severance packages ever work out for the guys in the corner offices. The Internet won't be tamed.

To some extent, the title of the book is a misnomer. There aren't many stories of fast talking Internet guys pulling the wool over the eyes of the old media guys, at least in the way that Lyle Lanley talked the town of Springfield into building a monorail. The media moguls knew that the Internet was going to be big and they knew they only way they could be part of it was to invest. As Bob Pittman says at the beginning of the book, the networks ignored cable channels and then woke up one day to see that the upstarts controlled the new landscape. The old school media magnates knew they had no choice and they spent freely.

The title is also a bit wrong because the bamboozled are usually outright losers, conned completely -- and that certainly hasn't happened to all of the media titans. The list of the top news sites from Jupiter Media Metrix includes plenty of old corporate names . Despite the loss of cash, some of the old media companies were able to dominate the Internet. That doesn't mean they'll stay in the business and it doesn't mean that they're making money, but no one is worrying about the Mom in NJ.

This world view is a bit myopic. It should come as no surprise that web sites like the Drudge Report or Slashdot don't make it into the conversation. This is really a book about the few guys at the top of the New York media empires and their desire to somehow, some way, get a handle on this Internet thing. Truly interactive sites like Slashdot seem to be beyond the understanding of these guys because Motavalli notes that despite the "Letters to the Editors" section, most magazine and newspapers editors don't understand how to interact with readers.

The most telling details may be what didn't make the book. Motavalli spends little time talking about the words and images on the web pages. His subjects liked to use the word "content" as an abstraction for what the little guys serve to the little sheep. No one seemed to wonder whether it was good or bad, noir or funny, juvenile or sophisticated, or anything more than pure content. Aside from an occasional note about some truly lame web site, there's little discussion about what makes a web site good.

This is too bad because a few parts of the book hint that the guys below the big guys were really struggling to find the right voice for the on-line medium. They were asking questions like whether audience liked the ability to pick and choose the video snippets in the evening news. Was an on-line soap opera compelling enough to watch every day? Was there anyone who was willing to camp out by their keyboard to be the first to access some web site? Was buying an MP3 like buying a single or a full album? Did people want one portal or many?

As anyone who's posted to Slashdot in search of karma knows, finding a way to please the crowds is not an easy task. Every artist knows that after all of the hype, all of the press, and all of the marketing, a song, a book, an article, or a Slashdot comment needs to stand alone on the stage, if only for a brief second, and live or die on its merits. Motavalli's book best contribution may be showing us how little the media big wigs cared about these moments. It wasn't about the story or the presentation or even what the sheep seemed to like. It was all about the org chart.

Peter Wayner is a writer, consultant and media mogul himself. If you're one of the sheep reading this far, you might consider consuming his latest content on secure information handling ( Translucent Databases ) or his content on steganography ( Disappearing Cryptography). You can purchase Bamboozled from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Peter Wayner writes: "If you're one of the last few who believe that the numbers on your portfolio statement are any more permanent than a spring day, a sun tan, or a wink in a bar, you may want to tune into John Motavalli's new book, Bamboozled At the Revolution: How Big Media Lost Billions in the Battle for the Internet. The book follows the stumbling attempt by the old school in the media to turn their so-called power into dominance over the new domain. Numbers fly back and forth. Executives fret over turf. Dreams of glory float skywards. Yet in the end, it's just as Ecclesiastes warned: 'All are of the dust, and all turn to dust again.'" Read on below. Bamboozled at the Revolution: How Big Media Lost Billions in the Battle for the Internet author John Motavalli pages 334 publisher Viking rating 7.0 reviewer Peter Wayner ISBN 0670899801 summary Stories from the big media boardrooms and their quest to extend their dominance.

The book is an inside tale told by an insider who chronicles the frantic days when the insiders were certain that the Internet was going to change everything. In this case, the insiders were the golden boys at media conglomerates who managed through some mixture of luck, devotion, and talent to control the worlds of cable television, newspapers, magazines, and movies. In the mid 1990's, the Internet threatened to overturn their world when they realized that anyone could set up a website, turn a bedroom into a corner office, and join the media. One minute some Mom in NJ is burning spaghetti sauce, the next minute Madonna is coming over for a chat on her weblog.

Reading the book is an ideal way for Slashdot readers to stick their nose into the exclusive tent filled with media moguls. The book does an ideal job of conveying the NY mindset that the world is made up of billions of sheep just waiting for the media to tell them how to bleat. When the Internet threatens to lure some of the flock, the big guys with the big corner offices start writing checks hoping to find a way to own a piece of it.

The book is played out chronologically and begins with Time-Warner's desire to build a full-service, interactive cable system in 1993. The final epilog was probably written in April and it's already a bit dated because it went to press before the accounting upheaval at AOL. In between, the executives of the big media companies struggle to find an Internet strategy-- something that never really gels for anyone.

Motavalli documents the progression with details that matter to media executives. We learn where people went to college (Haverford, Harvard), where they ate dinner (City Grill, "a gross strip mall" in Vienna, VA that serves great pizza,), the names of their yachts (Highlander), if their offices were big (yes), and if they got along (no). All of the executives in this book are always getting irked, losing confidence, chafing at some new org chart, or jettisoning some division.

Nothing seems to work for these guys. They try merging with each other; they try pop-up ads; and they try building portals. Yet through it all, the value of advertising just keeps dropping. The more time people spend on-line, the more page views they create. That means, more viewers mean lower ad prices. Uh-oh. The law of supply and demand seems to insist that success only begets failure. How are people going to make money on-line? We may never know, because nothing except the severance packages ever work out for the guys in the corner offices. The Internet won't be tamed.

To some extent, the title of the book is a misnomer. There aren't many stories of fast talking Internet guys pulling the wool over the eyes of the old media guys, at least in the way that Lyle Lanley talked the town of Springfield into building a monorail. The media moguls knew that the Internet was going to be big and they knew they only way they could be part of it was to invest. As Bob Pittman says at the beginning of the book, the networks ignored cable channels and then woke up one day to see that the upstarts controlled the new landscape. The old school media magnates knew they had no choice and they spent freely.

The title is also a bit wrong because the bamboozled are usually outright losers, conned completely -- and that certainly hasn't happened to all of the media titans. The list of the top news sites from Jupiter Media Metrix includes plenty of old corporate names . Despite the loss of cash, some of the old media companies were able to dominate the Internet. That doesn't mean they'll stay in the business and it doesn't mean that they're making money, but no one is worrying about the Mom in NJ.

This world view is a bit myopic. It should come as no surprise that web sites like the Drudge Report or Slashdot don't make it into the conversation. This is really a book about the few guys at the top of the New York media empires and their desire to somehow, some way, get a handle on this Internet thing. Truly interactive sites like Slashdot seem to be beyond the understanding of these guys because Motavalli notes that despite the "Letters to the Editors" section, most magazine and newspapers editors don't understand how to interact with readers.

The most telling details may be what didn't make the book. Motavalli spends little time talking about the words and images on the web pages. His subjects liked to use the word "content" as an abstraction for what the little guys serve to the little sheep. No one seemed to wonder whether it was good or bad, noir or funny, juvenile or sophisticated, or anything more than pure content. Aside from an occasional note about some truly lame web site, there's little discussion about what makes a web site good.

This is too bad because a few parts of the book hint that the guys below the big guys were really struggling to find the right voice for the on-line medium. They were asking questions like whether audience liked the ability to pick and choose the video snippets in the evening news. Was an on-line soap opera compelling enough to watch every day? Was there anyone who was willing to camp out by their keyboard to be the first to access some web site? Was buying an MP3 like buying a single or a full album? Did people want one portal or many?

As anyone who's posted to Slashdot in search of karma knows, finding a way to please the crowds is not an easy task. Every artist knows that after all of the hype, all of the press, and all of the marketing, a song, a book, an article, or a Slashdot comment needs to stand alone on the stage, if only for a brief second, and live or die on its merits. Motavalli's book best contribution may be showing us how little the media big wigs cared about these moments. It wasn't about the story or the presentation or even what the sheep seemed to like. It was all about the org chart.

Peter Wayner is a writer, consultant and media mogul himself. If you're one of the sheep reading this far, you might consider consuming his latest content on secure information handling ( Translucent Databases ) or his content on steganography ( Disappearing Cryptography). You can purchase Bamboozled from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Hettinga writes: "Through many popular books and articles in the New York Times, Peter Wayner has done more to promote the field of applied financial cryptography, and in particular open source financial cryptography, than any other author writing today. His new book, Translucent Databases, from Flyzone Press, is no exception." Read on for the rest of the review. Translucent Databases author Peter Wayner pages 185 publisher Flyzone Press rating Outstanding. 5 Stars. Buy this Book. reviewer Robert Hettinga ISBN 0-9675844-1-8 summary Translucent Databases cure "Database Nation" and the "Transparent Society"?

Translucent Databases has all the hallmarks of Wayner's books: clear, easy to read exposition of the main issues, why they're important, and, in his technical books, excellently documented code written for the most popular platforms for the technology in question.

This book in particular should be an instant classic because like all great books, it takes what should be a very simple idea, encrypted databases, and expands it to some amazing conclusions.

For a long time now, I've been interested in what I call the geodesic economy, where all information, including information controlling financial assets, is fractally "surfacted", like so much grease in soapy dishwater, as far out into the edges of a ubiquitous internetwork as Moore's Law will allow, using financial cryptography protocols to secure transactions and markets on a nominally insecure, but ubiquitous, public internetwork.

People who are familiar with my thinking about such things over the past 8 years will see quite quickly why I think Peter's new book is so important. Transparent databases represent a way not only to link the batch-settled, book-entry debit-for-credit world of modern financial operations with a more simply founded, but much more sophisticated world which uses cryptographic tokens representing control of various financial and real assets. They also show us how to actually account for those tokens in such a fashion that every financial actor in that market, man or machine, can trust that their bearer certificates are authentic ones, and done in such a fashion that a given token retains its cryptographic integrity, including the functionally anonymous characteristics that made it so cheap to use in the first place.

The singular feature of Wayner's translucent databases is that, like internet bearer transactions themselves, the cryptography securing data in them can happen in the client, and not a centrally vulnerable server. More to the point, by using data stored in this fashion, the data can be dispersed as far out in the network as... well, Moore's Law allows, in extremely fast and lightweight files, and, instead of creating summaries of data for reports, the data can be polled for as close to its source as possible, instantaneously, in realtime, instead of being rolled up into increasingly larger batch-processed summaries taking weeks, sometimes months, to produce and audit.

There are obvious implications for my own particular hobby-horses, like anonymous but accurate double spend databases for bearer transactions, where only a simple blinded m-of-n cryptographic hash of a given promise to pay is necessary to prevent the duplication of that promise to more than one person at a time. However, for the rest of us :-), Wayner also points to a whole host of much less esoteric applications in the lots of the usual places where absolute privacy and extremely authentic information, is at a premium. Examples for military, medical, and anti-rape databases, for accounting systems and securities transactions, and even for internet poker -- the paradigm of completely untrusted parties cooperating for what each player hopes will be his own, preferrably cash, benefit -- are all presented in clear writing and running code.

There has been a lot of lip-service in the privacy community about "owning" your own data. Unfortunately, by involving the state at all, these "advocates" almost always favor inadvertantly draconian political solutions to the problem presented by the ubiquity of database technology and its otherwise beneficial presense in our lives. They ususally present this nonsense as a "sacrifice" for the "greater good" that would make Hayek's Road to Serfdom look like Lilac Sunday at the local arboretum.

In Translucent Databases, Wayner shows, in precise detail, with code, how to solve that problem, without trusting lawyers, much less guys with guns.

Though quite a short read, the scope of the book itself is quite considerable. Wayner starts from simple hashes of data to merely obscure it, through various kinds of encryption, quantization of data, and even accounting with encrypted data using what amounts to virtual cumulative crossfoots like the kind you would see on all good accounting reports. In so doing, Wayner explains, quite simply, something that people like Eric Hughes made great, complicated hay out of years ago with gangling theories of encrypted "open" books.

Ultimately, Wayner really does end up where a lot of us think databases will be someday, particularly in finance: repositories of data accessible only by digital bearer tokens using various blind signature protocols, neatly, and quite literally, "dis-integrating" the ability of databases to be used against us as a tool of totalitarianism, exemplified most recently by Simpson Garfinkel in his book Database Nation , and, oddly enough, not because someone or other wants to strike a blow against the empire, but simply because it's safer -- and cheaper -- to do that way.

Every database programmer should have a copy of this simple and elegant book on his reference bookshelf. Particularly if he cares about the integrity of his data, the liability to the database's owner should information be misappropriated, and, not least, about freedom itself in a world of ubiquitous, and, frankly, necessary, stored detail: details about practically every person on earth, their property and finances, and, ultimately, everything they do.

Translucent Databases presents a simple, frankly beautiful, solution to David Brin's world of ubiquitous surveillance, one not requiring, as Brin seems to want, "trust" of state force-monopolists, much less their lawyers and apparatchiks.

In fact, it's such an elegant solution that, as Schopenhauer liked to say about the public acceptance of important new ideas, soon enough, people will say it was obvious all along.

Robert Hettinga is founder of IBUC, the Internet Bearer Underwriting Corporation, which will, hopefully, someday, :-), use translucent databases full of internet bearer certificates to reduce transaction costs by three orders of magnitude. You can purchase Translucent Databases through the publisher. Slashdot welcomes readers' book reviews -- to submit yours, read the book review guidelines, then visit the submission page.

Hettinga writes: "Through many popular books and articles in the New York Times, Peter Wayner has done more to promote the field of applied financial cryptography, and in particular open source financial cryptography, than any other author writing today. His new book, Translucent Databases, from Flyzone Press, is no exception." Read on for the rest of the review. Translucent Databases author Peter Wayner pages 185 publisher Flyzone Press rating Outstanding. 5 Stars. Buy this Book. reviewer Robert Hettinga ISBN 0-9675844-1-8 summary Translucent Databases cure "Database Nation" and the "Transparent Society"?

Translucent Databases has all the hallmarks of Wayner's books: clear, easy to read exposition of the main issues, why they're important, and, in his technical books, excellently documented code written for the most popular platforms for the technology in question.

This book in particular should be an instant classic because like all great books, it takes what should be a very simple idea, encrypted databases, and expands it to some amazing conclusions.

For a long time now, I've been interested in what I call the geodesic economy, where all information, including information controlling financial assets, is fractally "surfacted", like so much grease in soapy dishwater, as far out into the edges of a ubiquitous internetwork as Moore's Law will allow, using financial cryptography protocols to secure transactions and markets on a nominally insecure, but ubiquitous, public internetwork.

People who are familiar with my thinking about such things over the past 8 years will see quite quickly why I think Peter's new book is so important. Transparent databases represent a way not only to link the batch-settled, book-entry debit-for-credit world of modern financial operations with a more simply founded, but much more sophisticated world which uses cryptographic tokens representing control of various financial and real assets. They also show us how to actually account for those tokens in such a fashion that every financial actor in that market, man or machine, can trust that their bearer certificates are authentic ones, and done in such a fashion that a given token retains its cryptographic integrity, including the functionally anonymous characteristics that made it so cheap to use in the first place.

The singular feature of Wayner's translucent databases is that, like internet bearer transactions themselves, the cryptography securing data in them can happen in the client, and not a centrally vulnerable server. More to the point, by using data stored in this fashion, the data can be dispersed as far out in the network as... well, Moore's Law allows, in extremely fast and lightweight files, and, instead of creating summaries of data for reports, the data can be polled for as close to its source as possible, instantaneously, in realtime, instead of being rolled up into increasingly larger batch-processed summaries taking weeks, sometimes months, to produce and audit.

There are obvious implications for my own particular hobby-horses, like anonymous but accurate double spend databases for bearer transactions, where only a simple blinded m-of-n cryptographic hash of a given promise to pay is necessary to prevent the duplication of that promise to more than one person at a time. However, for the rest of us :-), Wayner also points to a whole host of much less esoteric applications in the lots of the usual places where absolute privacy and extremely authentic information, is at a premium. Examples for military, medical, and anti-rape databases, for accounting systems and securities transactions, and even for internet poker -- the paradigm of completely untrusted parties cooperating for what each player hopes will be his own, preferrably cash, benefit -- are all presented in clear writing and running code.

There has been a lot of lip-service in the privacy community about "owning" your own data. Unfortunately, by involving the state at all, these "advocates" almost always favor inadvertantly draconian political solutions to the problem presented by the ubiquity of database technology and its otherwise beneficial presense in our lives. They ususally present this nonsense as a "sacrifice" for the "greater good" that would make Hayek's Road to Serfdom look like Lilac Sunday at the local arboretum.

In Translucent Databases, Wayner shows, in precise detail, with code, how to solve that problem, without trusting lawyers, much less guys with guns.

Though quite a short read, the scope of the book itself is quite considerable. Wayner starts from simple hashes of data to merely obscure it, through various kinds of encryption, quantization of data, and even accounting with encrypted data using what amounts to virtual cumulative crossfoots like the kind you would see on all good accounting reports. In so doing, Wayner explains, quite simply, something that people like Eric Hughes made great, complicated hay out of years ago with gangling theories of encrypted "open" books.

Ultimately, Wayner really does end up where a lot of us think databases will be someday, particularly in finance: repositories of data accessible only by digital bearer tokens using various blind signature protocols, neatly, and quite literally, "dis-integrating" the ability of databases to be used against us as a tool of totalitarianism, exemplified most recently by Simpson Garfinkel in his book Database Nation , and, oddly enough, not because someone or other wants to strike a blow against the empire, but simply because it's safer -- and cheaper -- to do that way.

Every database programmer should have a copy of this simple and elegant book on his reference bookshelf. Particularly if he cares about the integrity of his data, the liability to the database's owner should information be misappropriated, and, not least, about freedom itself in a world of ubiquitous, and, frankly, necessary, stored detail: details about practically every person on earth, their property and finances, and, ultimately, everything they do.

Translucent Databases presents a simple, frankly beautiful, solution to David Brin's world of ubiquitous surveillance, one not requiring, as Brin seems to want, "trust" of state force-monopolists, much less their lawyers and apparatchiks.

In fact, it's such an elegant solution that, as Schopenhauer liked to say about the public acceptance of important new ideas, soon enough, people will say it was obvious all along.

Robert Hettinga is founder of IBUC, the Internet Bearer Underwriting Corporation, which will, hopefully, someday, :-), use translucent databases full of internet bearer certificates to reduce transaction costs by three orders of magnitude. You can purchase Translucent Databases through the publisher. Slashdot welcomes readers' book reviews -- to submit yours, read the book review guidelines, then visit the submission page.

peterwayner writes: "Everyone has heard stories of odd coincidences from cousins who call each other simultaneously or professors making the same discovery, but there may be no better proof of synchronicity than Steven Spielberg's charcoal grey rendering of Philip Kindred Dick's short story, "Minority Report." This tale of police who solve crimes before they are committed reached the theaters just a few weeks after the United States learned that even citizens are being locked up without a trial or a lawyer because they might turn out to be terrorists." Read the rest of his review below.

The resonance between this story and the current war is so strong that it's almost impossible to watch it for what it is, a good murder mystery conceived well before September 11th retelling a short story that was published long ago in 1956. The movie is half a work of philosophy and half a head-scratching what-if narrative exploring the merger of computers, extra-sensory perception, and genetic research. All of this is painted on the screen in the sad muted browns, sepias, blues and greys of an amateur watercolorist who can't keep the colors from turning to mud.

The conceit is the kind of classic conundrum that made science fiction great: the police in 2054 can tap the minds of three "pre-cogs" who see visions of murders a few hours before they will happen. Tom Cruise plays a cop who flies off in a jet pack to nab the soon-to-be-bad guys and lock them away before they kill. Can we really be sure the crime will be committed just as the pre-cognitives predict? Cruise is an earnest believer in the system's perfection until, it should be obvious, the system implicates him in the pre-murder of someone he's never met.

The yarn unfolds as a long string of chase scenes mixed with some flashbacks and some pre-cognitive dodges. Cruise's character, we're told, is a fast runner and he spends plenty of time running fast. The plot is crisp and layered enough to unfold several times. The hinge points are as good as the philosophical question they serve.

The biggest failure of the movie may be the set design and the look. At one moment, we see computers to inspire the next generation from Apple, in another moment we're in a mall that isn't as fancy or as new as the mall around the corner from my house. The logos for the Gap and Pepsi haven't changed since they were faxed over from the product-placement department. Many of the scenes look contemporary, with minimal set dressing, but then along comes a great car chase tricked out like the wet dream from some 19-year-old in an art school in Southern California. The unity of vision that delivered the oily dystopia of Bladerunner is missing this time. I wouldn't be surprised if someone tightened the budget screws in the middle of the film and sent them scrambling to save money on some scenes.

The tone coming from the actors is also a bit uneven. Spielberg managed to toss in funny moments in the Indiana Jones trilogy and whole schtick came together with the amazing certainty of comic-book escapism. The bits of humor in this movie's chase scenes, though, ruin the nervous paranoia and amped-up tension crackling through the narrative's ganglia. Is this supposed to be summer joy ride or a serious exploration of the meaning of justice?

These errors in execution don't matter too much because the storyline is so strong and central to our current struggle with terrorism. No one probably wants to hear that Dick wrote this story just a few years after the Supreme Court finally decided that it wasn't really legal to lock up Japanese-Americans on the off chance that they might take their orders from Tokyo. The movie theater where I saw the film is only a few miles from the prison that held much of Baltimore's City Council during the Civil War.

Despite the uncomfortable fact that moments like these happen again and again in history, there's no way to escape wondering whether Spielberg is some kind of pre-cog being who gets his version of the zeitgeist delivered early. The timing is just eerie.

Peter Wayner thinks his new book, Translucent Databases is about ten years ahead of its time. His book about steganography, Disappearing Cryptography , may be a few months late."

peterwayner writes: "Everyone has heard stories of odd coincidences from cousins who call each other simultaneously or professors making the same discovery, but there may be no better proof of synchronicity than Steven Spielberg's charcoal grey rendering of Philip Kindred Dick's short story, "Minority Report." This tale of police who solve crimes before they are committed reached the theaters just a few weeks after the United States learned that even citizens are being locked up without a trial or a lawyer because they might turn out to be terrorists." Read the rest of his review below.

The resonance between this story and the current war is so strong that it's almost impossible to watch it for what it is, a good murder mystery conceived well before September 11th retelling a short story that was published long ago in 1956. The movie is half a work of philosophy and half a head-scratching what-if narrative exploring the merger of computers, extra-sensory perception, and genetic research. All of this is painted on the screen in the sad muted browns, sepias, blues and greys of an amateur watercolorist who can't keep the colors from turning to mud.

The conceit is the kind of classic conundrum that made science fiction great: the police in 2054 can tap the minds of three "pre-cogs" who see visions of murders a few hours before they will happen. Tom Cruise plays a cop who flies off in a jet pack to nab the soon-to-be-bad guys and lock them away before they kill. Can we really be sure the crime will be committed just as the pre-cognitives predict? Cruise is an earnest believer in the system's perfection until, it should be obvious, the system implicates him in the pre-murder of someone he's never met.

The yarn unfolds as a long string of chase scenes mixed with some flashbacks and some pre-cognitive dodges. Cruise's character, we're told, is a fast runner and he spends plenty of time running fast. The plot is crisp and layered enough to unfold several times. The hinge points are as good as the philosophical question they serve.

The biggest failure of the movie may be the set design and the look. At one moment, we see computers to inspire the next generation from Apple, in another moment we're in a mall that isn't as fancy or as new as the mall around the corner from my house. The logos for the Gap and Pepsi haven't changed since they were faxed over from the product-placement department. Many of the scenes look contemporary, with minimal set dressing, but then along comes a great car chase tricked out like the wet dream from some 19-year-old in an art school in Southern California. The unity of vision that delivered the oily dystopia of Bladerunner is missing this time. I wouldn't be surprised if someone tightened the budget screws in the middle of the film and sent them scrambling to save money on some scenes.

The tone coming from the actors is also a bit uneven. Spielberg managed to toss in funny moments in the Indiana Jones trilogy and whole schtick came together with the amazing certainty of comic-book escapism. The bits of humor in this movie's chase scenes, though, ruin the nervous paranoia and amped-up tension crackling through the narrative's ganglia. Is this supposed to be summer joy ride or a serious exploration of the meaning of justice?

These errors in execution don't matter too much because the storyline is so strong and central to our current struggle with terrorism. No one probably wants to hear that Dick wrote this story just a few years after the Supreme Court finally decided that it wasn't really legal to lock up Japanese-Americans on the off chance that they might take their orders from Tokyo. The movie theater where I saw the film is only a few miles from the prison that held much of Baltimore's City Council during the Civil War.

Despite the uncomfortable fact that moments like these happen again and again in history, there's no way to escape wondering whether Spielberg is some kind of pre-cog being who gets his version of the zeitgeist delivered early. The timing is just eerie.

Peter Wayner thinks his new book, Translucent Databases is about ten years ahead of its time. His book about steganography, Disappearing Cryptography , may be a few months late."

Peter Wayner writes: "In a world where Ali had to meet Frazier and Luke had to meet his father, it was only a matter of time before buzzwords like Java and eXtreme Programming found themselves together on the same marquee. A pair of new books examines some open source Java development tools and outlines how they can be put to use by those trying to master their workload by adopting the techniques of eXtreme programming." Read on for his latest review, which is really two reviews in one. (see each) author (see each) pages (see each) publisher (see each) rating (see each) reviewer Peter Wayner ISBN (see each) summary Two books which explore the use of Ant in Java software development

The two books are excellent examples of how the book industry organizes and disciplines the often crazy explosion of new tools, approaches, structures and metaphors developed by the software industry. Ant: The Definitive Guide by Jesse Tilly and Eric Burke comes from O'Reilly, the masters of producing missing manuals for open source projects. The other, Java Tools for eXtreme Programming: Mastering Open Source Tools including Ant, JUnit, and Cactus by Richard Hightower and Nicholas Lesiecki was published by John Wiley and Sons. Both provide a clear, example-driven exploration of the tools at hand.

The books are probably driven by the success of Kent Beck's Extreme Programming Explained: Embrace Change , a manifesto that outlined Beck's belief that the best way to develop code was with small teams of programmers and users who constantly reworked the software. His most controversial and attention grabbing notion demanded that the programmers work in pairs sharing one computer, one mouse and one keyboard. The constant interaction forced everyone to actually communicate with each other without sending emails and that, more than anything else, may be responsible for the success of his vision. His book spawned a few others on how programmers can plan to apply his vision.

Meanwhile, on the other side of the buzzword galaxy, the Apache group was quietly creating some of the coolest Java development and deployment tools around. Ant was and still is one of the most revolutionary, even though it was just a simple reworking of the classic UNIX make command. Its creator, James Davidson, grew so frustrated with the shell interface of the make command that he wrote a Java-centric version that moved all of the compilation, compression, and distribution inside one Java process. Now, no one has to wait for another Java Virtual Machine to start up to compile each class file independently.

While Davidson's Ant isn't much different than make at first glance, it's hard to overestimate the power of giving programmers a clever tool with plenty of hooks into the development process. Anyone can write new tasks for Ant, and some clever folks have built great new widgets that do things like enforce style guidelines or grab new code from a CVS tree. The structure of Ant lets the programmer dig deeply into the build process. The organic growth and dynamic flexibility shows how close Java can be to Lisp.

Tilly and Burke do a good job capturing the spirit of the tool. Their book follows O'Reilly's time-tested and market-proven simple-examples technique to illustrate how to use Ant for your projects. The chapters in the first half of the book outline how to use and extend Ant for your project. The strength of the book may be the way the authors casually include practical advice about the bugs and idiosyncracies of the tool. While Ant is quite capable, there are a number of little limitations to the XML parser that can drive new users a bit nuts. The second half of the book is a detailed description of the API, the data types and the other practical documentation.

In one sense, it's not really fair to lump this book in with all of this gloss about Extreme Programming. because it's just another methodical O'Reilly book with Dover artwork on the cover. It's important to realize that these tools aren't directly tied to the extreme programming movement. Ant was just created by a Java programmer who hated to wait. Everything else came afterwards when he opened the API.

Ant: The Definitive Guide author Jesse Tilly & Eric M. Burke pages 260 publisher O'Reilly rating 7 ISBN 0-597-00184-3 summary A methodical, in-depth look at the Java tool.

The other book, however, explicitly illustrates how some popular open source tools can help the process of extreme programming. Hightower and Lesiecki's book is much broader than Tilly and Burke's because they want to tackle so much more. They don't want to just provide a missing manual for the tool-- they want to give the world a road map on how they use Ant and its cousins JUnit, HTTPUnit, and Cactus to build better applications. It should be noted that Hightower and Lesiecki work for a consulting group called eBlox and a number of other eBlox programmers are listed as contributors to the book. I think it's fair to say that anyone who hires eBlox will get eXtreme Programming results built with this methodology.

The best part about this book is the wide scope. Ant remains the central taskmaster responsible for building the software, but the book explains how to incorporate other tools for testing the software. The authors embrace one of the extreme programming central beliefs that programmers should define how to test their code before it is actually written. The book explains how to use JUnit, Cactus, and HTTPUnit to set up rules to test every class file. After ANT fires up the compiler, it turns around and runs the tests on the code.

Java Tools for eXtreme Programming author Richard Hightower and Nicholas Lesiecki pages 513 publisher John Wiley and Sons rating 7 ISBN 0-471-20708-X summary How to use some Java tools to transform extreme programming theory into reality.

I don't think that eXtreme Programming or any of these tools is the last word on the subject. The biggest problem is that testing a piece of code is guaranteed to be fairly rudimentary. No programmer can come up with test cases to push all of buttons in all possible combinations. The structure and discipline provided by this approach can help, but the book makes it clear that no amount of pairs programming or extremism will remove the need for the guidance of good programmers.

If anything these tools and the books about them should serve as inspiration for the next round of tools even more focused on extreme programming. The tools are impressive, but there is plenty of room for more innovation. None of them is aimed at explicitly coordinating the work of multiple developers and none of them is designed to provide much structure to the refactoring process. These areas are still very much arts, but there's no reason why tool suites like Ant can't evolve some rational approach to solving them. Perhaps the Slashdot audience can provide some informative postings with pointers to the next generation of cool tools.

Hightower and Lesiecki's book feels a bit more rudimentary and basic than Tilly and Burke's, in part because they cover so much more ground. Although their book is broader, it doesn't go into as much depth about Ant as Tilly and Burke's. The examples are simpler, too, and Hightower and Liesiecki seem mainly interested in getting you excited about building and testing software with the tools. There just isn't as much room for details. If you're interested in learning as much as you can about Ant, choose the book devoted to it. If you want to learn how to use a diverse set of tools to build and test your program in an extreme way, go for that book.

Peter Wayner blends the buzzwords of security, privacy, and data warehousing together in his latest book, Translucent Databases. It shows how to ensure that only the right people see the right information and the wrong people get nothing. His other new book, Disappearing Cryptography, mixes the buzzwords of being, nothingness, steganography, and cryptography. You can purchase both Ant: The Definitive Guide and Java Tools for eXtreme Programming from bn.com. Slashdot welcomes readers' book reviews -- to submit yours, read the book review guidelines, then hit the submission page.

Peter Wayner writes: "In a world where Ali had to meet Frazier and Luke had to meet his father, it was only a matter of time before buzzwords like Java and eXtreme Programming found themselves together on the same marquee. A pair of new books examines some open source Java development tools and outlines how they can be put to use by those trying to master their workload by adopting the techniques of eXtreme programming." Read on for his latest review, which is really two reviews in one. (see each) author (see each) pages (see each) publisher (see each) rating (see each) reviewer Peter Wayner ISBN (see each) summary Two books which explore the use of Ant in Java software development

The two books are excellent examples of how the book industry organizes and disciplines the often crazy explosion of new tools, approaches, structures and metaphors developed by the software industry. Ant: The Definitive Guide by Jesse Tilly and Eric Burke comes from O'Reilly, the masters of producing missing manuals for open source projects. The other, Java Tools for eXtreme Programming: Mastering Open Source Tools including Ant, JUnit, and Cactus by Richard Hightower and Nicholas Lesiecki was published by John Wiley and Sons. Both provide a clear, example-driven exploration of the tools at hand.

The books are probably driven by the success of Kent Beck's Extreme Programming Explained: Embrace Change , a manifesto that outlined Beck's belief that the best way to develop code was with small teams of programmers and users who constantly reworked the software. His most controversial and attention grabbing notion demanded that the programmers work in pairs sharing one computer, one mouse and one keyboard. The constant interaction forced everyone to actually communicate with each other without sending emails and that, more than anything else, may be responsible for the success of his vision. His book spawned a few others on how programmers can plan to apply his vision.

Meanwhile, on the other side of the buzzword galaxy, the Apache group was quietly creating some of the coolest Java development and deployment tools around. Ant was and still is one of the most revolutionary, even though it was just a simple reworking of the classic UNIX make command. Its creator, James Davidson, grew so frustrated with the shell interface of the make command that he wrote a Java-centric version that moved all of the compilation, compression, and distribution inside one Java process. Now, no one has to wait for another Java Virtual Machine to start up to compile each class file independently.

While Davidson's Ant isn't much different than make at first glance, it's hard to overestimate the power of giving programmers a clever tool with plenty of hooks into the development process. Anyone can write new tasks for Ant, and some clever folks have built great new widgets that do things like enforce style guidelines or grab new code from a CVS tree. The structure of Ant lets the programmer dig deeply into the build process. The organic growth and dynamic flexibility shows how close Java can be to Lisp.

Tilly and Burke do a good job capturing the spirit of the tool. Their book follows O'Reilly's time-tested and market-proven simple-examples technique to illustrate how to use Ant for your projects. The chapters in the first half of the book outline how to use and extend Ant for your project. The strength of the book may be the way the authors casually include practical advice about the bugs and idiosyncracies of the tool. While Ant is quite capable, there are a number of little limitations to the XML parser that can drive new users a bit nuts. The second half of the book is a detailed description of the API, the data types and the other practical documentation.

In one sense, it's not really fair to lump this book in with all of this gloss about Extreme Programming. because it's just another methodical O'Reilly book with Dover artwork on the cover. It's important to realize that these tools aren't directly tied to the extreme programming movement. Ant was just created by a Java programmer who hated to wait. Everything else came afterwards when he opened the API.

Ant: The Definitive Guide author Jesse Tilly & Eric M. Burke pages 260 publisher O'Reilly rating 7 ISBN 0-597-00184-3 summary A methodical, in-depth look at the Java tool.

The other book, however, explicitly illustrates how some popular open source tools can help the process of extreme programming. Hightower and Lesiecki's book is much broader than Tilly and Burke's because they want to tackle so much more. They don't want to just provide a missing manual for the tool-- they want to give the world a road map on how they use Ant and its cousins JUnit, HTTPUnit, and Cactus to build better applications. It should be noted that Hightower and Lesiecki work for a consulting group called eBlox and a number of other eBlox programmers are listed as contributors to the book. I think it's fair to say that anyone who hires eBlox will get eXtreme Programming results built with this methodology.

The best part about this book is the wide scope. Ant remains the central taskmaster responsible for building the software, but the book explains how to incorporate other tools for testing the software. The authors embrace one of the extreme programming central beliefs that programmers should define how to test their code before it is actually written. The book explains how to use JUnit, Cactus, and HTTPUnit to set up rules to test every class file. After ANT fires up the compiler, it turns around and runs the tests on the code.

Java Tools for eXtreme Programming author Richard Hightower and Nicholas Lesiecki pages 513 publisher John Wiley and Sons rating 7 ISBN 0-471-20708-X summary How to use some Java tools to transform extreme programming theory into reality.

I don't think that eXtreme Programming or any of these tools is the last word on the subject. The biggest problem is that testing a piece of code is guaranteed to be fairly rudimentary. No programmer can come up with test cases to push all of buttons in all possible combinations. The structure and discipline provided by this approach can help, but the book makes it clear that no amount of pairs programming or extremism will remove the need for the guidance of good programmers.

If anything these tools and the books about them should serve as inspiration for the next round of tools even more focused on extreme programming. The tools are impressive, but there is plenty of room for more innovation. None of them is aimed at explicitly coordinating the work of multiple developers and none of them is designed to provide much structure to the refactoring process. These areas are still very much arts, but there's no reason why tool suites like Ant can't evolve some rational approach to solving them. Perhaps the Slashdot audience can provide some informative postings with pointers to the next generation of cool tools.

Hightower and Lesiecki's book feels a bit more rudimentary and basic than Tilly and Burke's, in part because they cover so much more ground. Although their book is broader, it doesn't go into as much depth about Ant as Tilly and Burke's. The examples are simpler, too, and Hightower and Liesiecki seem mainly interested in getting you excited about building and testing software with the tools. There just isn't as much room for details. If you're interested in learning as much as you can about Ant, choose the book devoted to it. If you want to learn how to use a diverse set of tools to build and test your program in an extreme way, go for that book.

Peter Wayner blends the buzzwords of security, privacy, and data warehousing together in his latest book, Translucent Databases. It shows how to ensure that only the right people see the right information and the wrong people get nothing. His other new book, Disappearing Cryptography, mixes the buzzwords of being, nothingness, steganography, and cryptography. You can purchase both Ant: The Definitive Guide and Java Tools for eXtreme Programming from bn.com. Slashdot welcomes readers' book reviews -- to submit yours, read the book review guidelines, then hit the submission page.

Peter Wayner passed us this review of Adam Cohen's The Perfect Store, a chronicle of the rise of Ebay. Read on to learn more about the people and ideas behind the dominant online auction site. The Perfect Store: Inside Ebay author Adam Cohen pages 336 publisher Little,Brown rating 8 reviewer Peter Wayner ISBN 0-316-15048-7 summary The story of the world's largest online swapmeet, and why it's really not a swapmeet.

According to the tale, an atheist traveled to Rome to check out the Catholic Church, and saw, through some odd gift of divine grace, that the Devil himself was sitting at on the throne of St. Peter and ruling the Church disguised as a Pope. The atheist reflected upon the paradox and then became a devout Roman Catholic. Why? He reasoned that only the one true faith could succeed with the Devil himself in charge.

Leaps of faith take many forms, and none were stranger to the world of the 1990's than the possibility that people might buy objects they've never touched from people they've never met and send money to addresses they've never seen on the basis of a bunch of colored stars summarizing a community's collective opinion. Yet that's eBay -- and now anyone curious about the communion of online buyers and sellers can turn to The Perfect Store by Adam Cohen. The new history chronicles the purity of the founder's vision, the tumultuousness of exponential growth, the tremors of bliss rippling down the spines of the auction winners, the purgatory of crashing servers, the saintly trust of the masses, and the deviltry of the few. Through all of these trials and tests, the company prospered with a steadfast devotion to a libertarian's dream of a frictionless marketplace where buyers and sellers could engage in a conversation to discover the one true price.

The book is sort of a hagiography, although focused more on the marketplace community than the corporate leadership. Almost every twist and turn of the company's history seems to depend upon how well the people adhere to the vision of a hierarchy-free community of buyers and sellers. The company thrives when they make it easy for goods to find the people who want them.

The book begins where eBay itself began: in the vision of the founder, Pierre Omidyar. The book follows him and then the people who join the company by laying out a largely chronological collection of important milestones, interrupted every now and then with a tale of some quirky eBay member. The author, Adam Cohen, may not speak with the earnest voice of a true believer, but he is largely happy to describe the decisions with devotion and reverence. This shouldn't be surprising because he worked closely with everyone at eBay and even had his own company ID badge and work space in the office building. He obviously spoke often to the core team and the history is filled with their words.

But the book isn't a dump truck filled with happy stories. The book manages to include almost all of the major controversies that I, a casual eBay user and fan, remember. There's a long discussion about the decision to ban guns and plenty of talk about the right way to handle pornography and used underwear. Cohen also interviewed a number of the disenchanted members who developed a love/hate relationship with the marketplace run by one corporation. They keep talking about quitting or protesting or going somewhere else when eBay keeps jacking up the rates, but every time the market dominance of the company keeps pulling them back in.

The later half of the book is largely filled with these controversies, in part because there are only so many ways you can keep repeating details about the company's phenomenal growth. The viral explosion of new listings was the story at the beginning, but after the IPO cemented the success, the management had to wrestle with the bits of evil that would drift into the network.

Most of the coverage of these battles is straight-forward and carried by a flat tone typical of journalistic distance. The analysis and criticism are largely left for the reader to assemble, although the parts aren't hard to find. For instance, we learn early that Omidyar's experience in the 1980's with the fat cat-friendly IPO market inspired him to create a neutral marketplace where all buyers and sellers were equals. He apparently tried to buy into an IPO only to discover that skinny cats didn't get to buy at the issuing price. Back then, Omidyar was a skinny cat.

But when it comes time for eBay's IPO, the people on the company's throne skipped the chance for an eBay-like OpenIPO. Goldman Sachs got the opportunity to pick an opening price for the stock, and the investment bankers managed to find a number that left a lion's share for the usual fat cats.

At the time, Omidyar, the other members of the management team (Jeff Skoll and Meg Whitman) and Benchmark Capital controlled a stunning 98.1% of the stock. They quickly became billionaires. Many of the workers made a few million of that 1.9% divided among the rest, but everyone else was left out. The thousands of people who worked the bulletin boards, and help create a cohesive community ruled by colored stars got nothing. This continues to be a bitter point for many involved with eBay from the beginning. Money weaves a strange path in and out of the narrative. On one hand, marketplaces are all about price discovery. The only reason to list an item on eBay is to get money. On the other, the book gives the impression that it's kind of crass to be into eBay for the money. The eBay folks are supposed to be passionate believers in this community ruled by colored stars. It's all about community, we're told. But I guess if you can't get IPO shares, that's what you have to live with.

The book may be best as a sly bit of exploratory surgery aimed at the strange desires in our body that drive commerce and trade. Some of the vignettes of eBay members are priceless and the stories about the effect of eBay on the market for collectables are not to be missed. Before eBay, the members of the Midwest Sad Irons Collectors spent hours at garage sales and antique stores looking for what many of us might call a rusting hunk of metal. There were even conventions populated by dealers helping people find what they wanted. All of the socializing and chatting intertwined in the weekend swapmeets became history when eBay made it possible for anyone to get what they want by plopping down big bids. There's no need to go to wade through church yards filled with schlock to find the grail of sad iron collectors, the swan-on-swan. Someone else is doing it right now... and all you need to do is grep the database. If you're lucky, there's no reserve!

At moments like these, the essential paradox of eBay becomes clear. On one hand, we're really after the stuff. We want the Pez dispenser, the Hair Bear bunch poster or the Elvis jacket. Do you realize how hard it is to find one just like that?

On the other hand, anyone with a bank account can buy any collectable now. There are dozens of every collectable waiting for buyers on eBay. Purity of heart, steadfast devotion to the goal, or indefatigable energy won't help you find the Grail when it's just a matter of typing the right number into a web form. There's no real scarcity anymore if you've got the right credit card. Which brings the question: if the items aren't really scarce, why would we want them?

The real problem is that eBay strips away the narrative from the objects. Flea markets, classified ads, and garage sales toss in stories for free and this is what the dinner guests, the friends, and the collecting buddies really want. They want to hear about the clueless, the loopy, the obnoxious, the greedy, the windbags, the ditzes, and all of the other characters buying and selling sad irons.

Adam Cohen's history, The Perfect Store, is a crisp, clean, and thorough retelling of what made eBay what it is today. It's a good story and you can't just buy those. Wait, I guess you can -- and the publisher is willing to print as many as the market will bear. Well, there's another paradox: Maybe, if eBay can survive with this many strange, wonderful and bitter stories, it may be the one true thing after all.

Peter Wayner is the author of Translucent Databases , a book commodifying the protection paradox. It describes how to build databases that reveal nothing to the wrong people, but everything to the right people. You can purchase The Perfect Store from bn.com. Slashdot welcomes readers' book reviews -- to submit yours, read the book review guidelines, then hit the submission page.

Peter Wayner writes: "There are 1693 books for sale at Amazon.com with the word "java" in the title and almost all of them are earnest, chipper books that promise real programmers, dummies , and nuts that learning Java is easy. Bruce Tate's, Bitter Java , is not one these books." Read on to see if you'd like to experience Bruce Tate's bitterness first hand. Bitter Java: The lessons taught by server-side Java Antipatterns author Bruce A. Tate (with help from Braden R. Flowers) pages publisher Manning rating 8 reviewer Peter Wayner ISBN 1-930110-43-X summary A collection of bad habits to avoid for server developers using Java.

Writing and reading technical books is both a pleasure and a chore. Programming computers can be great fun, but doing the job well requires almost impossible amounts of discipline, attention to detail, and pure drive. The machines churn through billions of operations per second and a mistake in just one can send everything tumbling out of control. Most authors tend to gloss over the difficulty by tossing in a spoonful of Mary Poppins because it does little good to grouse. It's just so simple and straight-forward to toss in optimistic words like "simple" and "straight-forward."

Tate's approach is looks a bit different. He wants to follow in the tradition of Frederick Brook's Mythical Man Month and talk about software development with an honest voice. Microsoft executives, Objective C devotees, and assembler lovers will be disappointed because the title is a bit misleading. He's not really bitter about Java in the way that Princess Diana was bitter about the British Royalty, he's just had a few bad experiences and he wants to help us learn from them.

In fact, he's not even writing about Java in the general sense. The book concentrates on the problems that often arise with most popular and complicated applications for the technology like servlets and enterprise Java beans. If you're building a web site based on Java, then you might want to read through this book.

The structure itself is devoted to uncovering antipatterns , a term Tate uses because it plays off the way that Sun offered Java patterns to help programmers use the new tools efficiently. Most of the chapters show the wrong way to build something and then show how to correct it.

Chapter 8, for instance, demonstrates a bulletin board that seems to be well-designed on the surface. The parts of the data structure are broken up into suitable objects and every object comes with a collection of methods that act as gatekeepers for the data inside the object. It all looks elegant, but it performs badly especially on large installations when the objects live on different servers. Suddenly, all of the extra well-meaning object-oriented engineering starts jamming the flow. Wrapping every object with so much glue code is like hiring more workers to speed up a bureaucracy. Tate shows how to aggregate the calls and speed things up dramatically by cutting through the misapplied object-oriented concepts.

If you step back a bit and think about the book from a distance, the right title starts to look like "Bitter Object-Oriented Programming". Most of the problems in the book emerge when seemingly good uses of OOP turn out to be terribly slow when implemented. While all of the problems are practical hurdles awaiting Java programmers, they must have cousins in the world of C++ and the other OOP languages. Splitting things up into many objects is plenty of fun at the beginning, but when the messages start flowing, the code becomes a swamp.

After a few chapters it becomes clear that object-oriented programming is starting to reach practical limits. The theory may be elegant, but programmers can only make it work if they use guidebooks like Tate's. The object-oriented toolkits are too easy to use dangerously. So what is the solution?

This kind of guidebook filled with antipatterns may be the best we can do for now. Tate himself says that the book is filled with "merc talk", the kind of chatter about hair raising experiences he says that mercenaries trade when they're sitting around the fire. This is an apt description. If you're a hired codeslinger creating J2EE applications or servlets, then this is a good book for your shelf.

Peter Wayner's latest two books are Translucent Databases , an exploration of how to create ultra-secure databases, and Disappearing Cryptography: Information Hiding, Steganography and Watermarking , a book about mathematical parlour tricks, sleights-of-hand, and subversive things you can do with bits. You can purchase Bitter Java at bn.com, and you can join Peter in reviewing books by submitting reviews after reading the book review guidelines.

Peter Wayner writes: "There are 1693 books for sale at Amazon.com with the word "java" in the title and almost all of them are earnest, chipper books that promise real programmers, dummies , and nuts that learning Java is easy. Bruce Tate's, Bitter Java , is not one these books." Read on to see if you'd like to experience Bruce Tate's bitterness first hand. Bitter Java: The lessons taught by server-side Java Antipatterns author Bruce A. Tate (with help from Braden R. Flowers) pages publisher Manning rating 8 reviewer Peter Wayner ISBN 1-930110-43-X summary A collection of bad habits to avoid for server developers using Java.

Writing and reading technical books is both a pleasure and a chore. Programming computers can be great fun, but doing the job well requires almost impossible amounts of discipline, attention to detail, and pure drive. The machines churn through billions of operations per second and a mistake in just one can send everything tumbling out of control. Most authors tend to gloss over the difficulty by tossing in a spoonful of Mary Poppins because it does little good to grouse. It's just so simple and straight-forward to toss in optimistic words like "simple" and "straight-forward."

Tate's approach is looks a bit different. He wants to follow in the tradition of Frederick Brook's Mythical Man Month and talk about software development with an honest voice. Microsoft executives, Objective C devotees, and assembler lovers will be disappointed because the title is a bit misleading. He's not really bitter about Java in the way that Princess Diana was bitter about the British Royalty, he's just had a few bad experiences and he wants to help us learn from them.

In fact, he's not even writing about Java in the general sense. The book concentrates on the problems that often arise with most popular and complicated applications for the technology like servlets and enterprise Java beans. If you're building a web site based on Java, then you might want to read through this book.

The structure itself is devoted to uncovering antipatterns , a term Tate uses because it plays off the way that Sun offered Java patterns to help programmers use the new tools efficiently. Most of the chapters show the wrong way to build something and then show how to correct it.

Chapter 8, for instance, demonstrates a bulletin board that seems to be well-designed on the surface. The parts of the data structure are broken up into suitable objects and every object comes with a collection of methods that act as gatekeepers for the data inside the object. It all looks elegant, but it performs badly especially on large installations when the objects live on different servers. Suddenly, all of the extra well-meaning object-oriented engineering starts jamming the flow. Wrapping every object with so much glue code is like hiring more workers to speed up a bureaucracy. Tate shows how to aggregate the calls and speed things up dramatically by cutting through the misapplied object-oriented concepts.

If you step back a bit and think about the book from a distance, the right title starts to look like "Bitter Object-Oriented Programming". Most of the problems in the book emerge when seemingly good uses of OOP turn out to be terribly slow when implemented. While all of the problems are practical hurdles awaiting Java programmers, they must have cousins in the world of C++ and the other OOP languages. Splitting things up into many objects is plenty of fun at the beginning, but when the messages start flowing, the code becomes a swamp.

After a few chapters it becomes clear that object-oriented programming is starting to reach practical limits. The theory may be elegant, but programmers can only make it work if they use guidebooks like Tate's. The object-oriented toolkits are too easy to use dangerously. So what is the solution?

This kind of guidebook filled with antipatterns may be the best we can do for now. Tate himself says that the book is filled with "merc talk", the kind of chatter about hair raising experiences he says that mercenaries trade when they're sitting around the fire. This is an apt description. If you're a hired codeslinger creating J2EE applications or servlets, then this is a good book for your shelf.

Peter Wayner's latest two books are Translucent Databases , an exploration of how to create ultra-secure databases, and Disappearing Cryptography: Information Hiding, Steganography and Watermarking , a book about mathematical parlour tricks, sleights-of-hand, and subversive things you can do with bits. You can purchase Bitter Java at bn.com, and you can join Peter in reviewing books by submitting reviews after reading the book review guidelines.

Peter Wayner writes: "In all of the scary stories Hollywood circulates about copyright piracy, nothing could be scarier that the gang of file swapping, copyright circumventing hackers in the new movie 'Enigma'. They laugh and love a bit, but mainly they spend their time building a big whirring and clicking machine to smash a copyright protection mechanism. When the machine delivers, they put the results into a Gnutella-like file sharing system called Ultra so their friends can track down the original artists and kill them." (Read on for the rest of Peter's review.)

Ooops. Wrong generation and wrong spin. "Enigma" is about good codebreakers -- the mathematicians and clerks of Great Britain's Bletchley Park who helped the Allied cause during World War II by breaking the German coding machine known as "Enigma." It's a wonderful story that's been told as non-fiction several times before by serious historians. This time around, the former newspaper columnist Robert Harris created a thinly fictionalized novel filled with composite characters based on reality. While the result is not factually perfect, it is close enough to capture the dangerous era. Abandoning the literal truth also allowed him to build a richly plotted yarn that evolves cleanly and smoothly.

The film closely follows the novel, although it does eliminate a few of the more subtle complexities. It was wildly popular in Britain when it was released there last year, probably because the story is told with gorgeously detailed sets dressed with nostalgia for a time of British patriotism and success. The film's costumes are lavish, the extras are everywhere, and the look is close enough to reality that the best complaint one ex-translator stationed at Bletchley Park could offer was that the canteen in the film was much nicer. Even Mick Jagger, one of the film's producer, couldn't resist the spirit and gave himself a cameo appearance as an officer relaxing in a club.

This film could represent the cultural high point for codeslinging nerds and other Slashdot types. Jagger produced this film with another cultural icon, Saturday Night Live's Lorne Michaels. If you secretly spend your days dreaming of strutting around the stage like Mick Jagger, you can now take some pride in the fact that Mick Jagger spent at least a few days dreaming of playing a code geek. And why not? According to one of the characters, the women go weak in the knees when they get to talk to codebreakers like the protagonist, Tom Jericho (Dougray Scott).

This movie is about sex and mathematics and the crucial satisfaction that comes from understanding the depth of their power. The two main threads of the film track Tom Jericho's search for 1) a missing lover (Saffron Burroughs) and 2) a new way to break the Germans' four rotor, Naval Enigma system known as Shark. His lover may have been mixed up in Germany's sudden decision to abandon the old codes and all of this must be untangled or else the war could be lost. Tom Stoppard, the screenwriter also responsible for Shakespeare In Love, weaves these two threads together with car chases, kissing, train whistles, moonlit nights, illicit file swapping and a few other romantic chords.

It seems like a lot of things happen in four days, but we must remember that this plays out in an era when people weren't couch potatoes taught that ignoring advertising is forbidden. The pacing is the biggest problem with the film because there's too much action packed into 117 minutes, leaving some transitions a bit confusing. The jumps are often too quick and in some places it's hard to know when the flashbacks begin and end.

Despite that, there's much for a geek to love in this movie. Both the Enigma machine and the cryptanalytic attack developed by the British are described in fairly good detail. We learn, perhaps too quickly, that much of the game is finding a crib, a term the codebreakers used to refer to a word or phrase that must be somewhere in the scrambled message. A weather broadcast, for instance, would include the word "rainy" on a wet day and the codebreakers would examine the possible combinations that might produce that word. That was one weakness the folks at Bletchley Park were able to exploit before Jericho's girlfriend disappeared.

Some of the other mathematical details are accurate but not explained in enough detail to be easily understood. Once the crib was identified, the codebreakers relied heavily on the fact that the Enigma machine could not encode one letter into itself. This weakness allowed them to eliminate many of the potential cribs quickly. Then they spent their time looking for potential "loops" in the coding. In a simple case, a loop is formed when the letter A is encoded as an R and a few letters later, an R is encoded as an A. Most of the loops are a chain of several letters strung out in an odd combination. This pencil-and-paper work by the codebreaker is turned over to a big machine that uses the loops to eliminate many of the potential positions of the rotors. The rest are tested quickly with plenty of whirring and clicking. On a good day, and there were many of them, the right settings for the rotors popped out and let the Allies read the encrypted traffic.

You get to see all of this in action, although the film does not describe much of it in the hopes of sparing those unanointed with the knee-weakening, code smashing gene. It's not really fair for me to concentrate on the machines and ignore the actors because most of the movie revolves around the emotional battles for the characters and their conflicting desires. These passions are well-constructed and intelligently arranged. Dougray Scott plays the mathematician with enough dash and sophistication while Kate Winslet fills out the role of the mousey clerk and co-conspirator. The real star is Jeremy Northam, who plays a sophisticated Foreign Office spy with the right amount of oily charm. He, like everyone else in this movie, is fighting a private little war which may or may not fit in with the larger battle between the Allied and Axis forces.

Some of these battles are so crucial to the plot that it's impossible to comment on them without spoiling the ending. For this reason, I'm including several links for you to click after seeing the movie ( first, second, and third.) as well as a sentence encrypted with an Enigma simulator:

FBZ DDE NZA DJN PNI POH YBF NJR QFP DDZ TVP IHN YSJ IXX UAH YXF BZT ZXW BXS GES GYD IFO VXQ KHU LMA SYX YEG MGK

Using Enigma as a digital rights management device is not new-- Harris includes an encrypted dedication in the novel-- but it raises an interesting question: Is the movie and its detailed description of breaking the Enigma in violation of the DMCA? Is the extra detail in the movie just a cookbook for those who want to pirate the sentence I encrypted above? If so, should I be able to shut it down? While some reviewers may dream of writing something so powerful that it closes a movie immediately, I would hate to do it to this one. It's a pretty, nostalgic thriller that makes a good date movie--especially if you happen to be a knee-weakening, codebreaking type.

Peter Wayner's latest books are Disappearing Cryptography, an exploration about how to disguise information and Translucent Databases, a practical description of how to use encryption algorithms to protect sensitive information like credit cards and medical records. If they ever get made into a movie, he wants to be played by Keanu Reeves -- the one who played Ted "Theodore" Logan, not the one who played Neo.