Slashdot Mirror

eldavojohn writes "For quite some time humans have struggled to answer the question why there is anything rather than nothing. Jim Holt's Why Does the World Exist? tackles such questions in the form of a journey. After laying a brief groundwork, Holt travels from leading prominent philosopher to curmudgeonly physicist to reserved theologian, visiting each and relaying the juiciest parts of his transcripts to the reader. In doing so, this book takes on an interesting form with a meaty dense center to each chapter (the actual dialogues) surrounded by the light and fluffy bread of Holt's expert writing about the settings, weather and food of his travels. While this consequently lacks the characteristics of a heady hard hitting original philosophical work, these sandwiches should prove quite palatable for most readers. Why Does the World Exist? criss-crosses the etymological, epistemological, theological and philosophical aspects of its title while remaining a fairly easy read." Keep reading for the rest of eldavojohn's review. Why Does the World Exist?: An Existential Detective Story author Jim Holt pages 320 publisher Liveright rating 9/10 reviewer eldavojohn ISBN 978-0871404091 summary An existential detective story. The book's first page is titled "A Quick Proof That There Must Be Something Rather Than Nothing, for Modern People Who Lead Busy Lives" (made for those of you who don't have time to read) and presents a very simple proof about the self-forbiddingness of nothing. The book starts off with a brief prerogative to drive the reader's thirst for why this question is important. Typical of the rest of the book Holt drops a lot of names so I'm not going to mention the names that are brought up in passing. The author tries to cover all his bases by bring up anyone from Roger Penrose to René Descartes to Woody Allen. The veritable name dropping proves Holt has done his homework but at times can be a little overbearing and, in my opinion, reaches borderline ADD-philosophy at a few points in the book. Be warned, you will find Tennessee Williams, John Archibald Wheeler, Marcel Proust, Albert Einstein, Baruch Spinoza and Georg Cantor all mentioned on the same page! The opening few pages select an interesting cast from history as the question arises: Why Does the World Exist?

Holt proceeds from baiting the reader to what he calls a "Philosophical Tour D'Horizon" and, as its name suggests, this chapter blazes through many names — big and small — throughout history that might have contributed to answering this question. I can say this effort is quite readable whereas a more serious effort to be completely comprehensive would be much more lengthy and tedious. I should disclose at this point that Holt played his cards well by mentioning and paying favor to perhaps my most favorite of polymaths: Gottfried Wilhelm Leibniz (and he continues to do so throughout this book).

Following that, the next obvious step is to tackle a definition of "nothing" — our 'null hypothesis' of existence. We exist as something so we know that and so Holt begins by sampling what we have at our disposal to define nothing. Holt briefly recalls the advent of zero in mathematics and moves on to the more refined points of what nothing can be defined as in English, French and a number of other ways. This chapter struck me as needlessly tiresome as the author tackles the inane intricacies of natural languages applied to concepts like nothing. Heidegger's "nothing that noths" question struck me as merely a failure of natural language — not a deep and profound question. Holt correctly switches to logical methods like predicate calculus to better tackle this concept of nothing but this chapter left a bad taste in my mouth as the author never attacks the root problem. You can talk about how the word "nothing" operates in English or how "le néant" operates in French but these human invented definitions and grammars are buggy systems for the task at hand. Why do scientists prefer math to describe systems? Why do computers use true and false versus "maybe" and "probably not"? Logic, predicate calculus and math (although far from perfect themselves) are our tools to arm ourselves to better describe our surroundings and I feel like Holt wasted words on the shortcomings of "Does it make sense to say X about nothing?" Regardless this chapter does present mental exercises to the reader about what nothing truly is and examines the paradox of the null hypothesis in existence. Also, in so many ways nothing is nice and simple so why doesn't the law of parsimony dictate that there should have been nothing instead of what is?

The first person Holt visits in this book is Russian Physicist Andrei Linde (the same Linde that was awarded one of Milner's nin awards) and very little time is spent on Linde since the theory visited here is that we exist because our everything was created in a lab by a "physicist" hacker. The second person Holt interviews is a little more interesting and given many more pages. He also happened to be my favorite character in the quest and one with which I found myself most in agreement: Adolf Grünbaum. Holt calls this man "The Great Rejectionist" and I found that to be an adequate and fair title because their discussions make it clear that it is hard to start with base assumptions when debating this borderline hostile mind. Grünbaum, an atheist, had attacked Freudian psychoanalysis and served as an intelligence officer after escaping Nazi Germany. The one complaint I have of Grünbaum (that would be more prevalent with other philosophers) is that they took no sides on the debate of why there is something rather than nothing and instead required Holt to make statements that could then be either met with concurrence (ha!) or picked apart by someone armed with years of studying. There's a part in this chapter where Holt alludes to Grünbaum disagreeing to the statement that the Null World is the simplest possible outcome (I'm assuming in order to invoke the Law of Parsimony) and even allowing that to go forward Grünbaum says "Why should we think that the simple is ontologically more likely to be true?"

The way Grünbaum immediately rejected Holt's premises and the opening exercises discussing nothing led me to a problematic question about what exists outside our universe and what existed before the Big Bang. If it is indeed Nothing (with a capital N) then we mean there are no laws of nature, no Law of Parsimony, not even some semblance of cause and effect. So what particularly bothers me about all this discussion is that we're talking about Nothing using logic that has been developed and rooted entirely here in our world of something. Of course, this would circumvent any discussion or this book to be written so I assume that most philosophers in this realm largely set this aside for the sake of discussion and speculation.

Before jumping to the next stop, Holt arms us with the concepts of finite versus infinite and with good reason. Richard Swinburne is a philosopher of religion at Oxford and I found him to be the most disagreeable person encountered along the way in this book. Holt brings up many good points against the possibility of there being a God. The possibility of God explains away all of our aforementioned problems but I felt like he gave Swinburne a free pass on a lot of these points. I was disappointed that the author embodied an intellectual steel trap for everyone else while Swinburne, when cornered, wasn't pressed further. This chapter sets out to answer a lot of questions but I felt like Swinburne was reaching when he tried to explain that God is actually a very simple concept — maybe even simpler than you or I. And I just don't buy that. I also didn't think that Holt fully utilized the newly established definitions of infinity and nothing to pry apart Swinburne's position. As an example, Swinburne speaks of the "infinitely powerful" and "infinitely good" God but draws that as an analogy to parents watching children. He says that God keeps his distance and that's why we're not permeated with infinite goodness ourselves. I feel like Holt should be tearing this apart because this is illogical to me if I consider these two cases: Case 1) the universe is finite and there is Nothing outside of the universe so God does not exist outside the universe so he exists inside the universe. But if God is infinitely good, there would be no room in a finite space for evil — it would be completely packed with good. Case 2) God exists outside the universe (I believe this was Swinburne's suggestion) with the ability to influence inside the universe. However, we now find ourselves back to the issue that Swinburne and Holt addressed in this chapter and that is answering the questions, "What amount of power and good does God allow into the universe? And why that amount?" These two cases have plagued my mind since I was a child, E=mc^2 dictates that it takes a finite (though large to us) amount of power to create sustenance from nothing. The Christian God has an infinite amount of power and is infinitely good yet allows people to die when a finite amount of power would prolong their lives. From good people to bad people to people who have never had the chance to hear God's word, they die daily when a finite amount of power would save them. But I digress — suffice it to say this was a very disappointing chapter and this is why this book loses a point in my mind. I guess it was necessary to visit this possibility but it wasn't fair to let cordiality intervene with a philosophical swordfight.

On the heels of the visit to Swinburne, Holt discusses some of the finer points of proving God's existence through pure logic. I enjoyed his references to Bertrand Russell and Russell's fall to Anselm's ontological argument. Holt also relays Richard Dawkin's knee jerk dismissal of it and Gödel's more complete analysis of the logic. The next stop on the way is physicist David Deutsch of Oxford. The visit with Deutsch is relatively brief but he seems to maintain safe positions without venturing anywhere problematic. His interest is studying the mutliverse theory but he balks at any attempts to even suggest there might be a principle that explains the foundation of our existence. So there's not much to discuss but the opening of this principle of multiple universes is important to the rest of the possibilities presented throughout the book. Holt also looks at the possibility that our universe exists because of a "quantum fluctuation" as first proposed by Ed Tryon and later given more concrete possibilities by Alex Vilenkin. This leads nicely into Holt's next person to visit: Steven Weinberg.

Weinberg sheds a lot of light on the physical aspects with the question of existence. Weinberg provides a little discussion on string theory and how the scientific aspects might work. I was surprised to learn that Weinberg is disappointed at the slow rate of string theory development and he calls it "the best effort we've made to step beyond what we already know." There is, of course, a careful context to that statement with Weinberg explaining that it hasn't worked out how we initially thought it would. I found one of Weinberg's statements to be surprising when he calls Quantum mechanics an "empty stage" and he further says he thinks that "Karl Popper was wrong to say that a scientific theory must be open to falsification. You can't falsify quantum mechanics, since it doesn't make predictions." We don't have a final theory yet but Weinberg does a great job of explaining what finding one would mean and what it will never be able to answer. Holt follows this up with a lot of information and caveats about the multiverse/megaverse as he transitions to another popular scientist and writer.

I've read a number of Roger Penrose's books and was pleased to read his interaction with Holt. I was a little disappointed with Holt's treatment of Platonism in regards to mathematics — mostly because he treats it as borderline mysticism and I personally enjoy reading that kind of mathematical philosophy. While I feel like it has roots in mysticism, I have enjoyed Penrose's works that reference "Platonic contact." Penrose imagines that there are three worlds: the physical world, the world consisting of consciousness and the aforementioned Platonic world. A very brief explanation is that there is a mysterious connection between this physical world via our minds to the conscious world and in our minds there is now a small part of our conscious (the part dealing with mathematics) that connects us to the Platonic world. So I suppose that triples the question of this book and Holt isn't afraid to call these worlds "miraculously self-creating and self-sustaining." Penrose, calls the Platonic world "eternally existing", "profound" and "timeless" but what of the possibility of the Null World? What about outside our universe? How does it stand up to the Nothing? These questions are never really pressed for some reason. Holt briefly references an extreme Platonist by the name of Max Tegmark and I felt like Penrose didn't leave much progress in our quest to answer the question of why there is something rather than nothing. Instead, he offers that this Platonic world is prime and the other two exist in its shadows but I was never satisfied or understood why those shadows exist.

Holt transitions to the next pieces with a reference to John Archibald Wheeler's "it from bit." As a developer, this is an incredibly tantalizing possibility but I found it to be a bit misplaced in this book. I found the explanation of this to be less than satisfactory (similarly as in my review of Gleick's "The Information") and I wish someone would include more substance to this view of everything arising from information. Holt muddies up the water even a little further by examining the idea that our brains have this "mind-stuff" or property to them that is perhaps built on top of a quantum phenomena. While there are interesting thought experiments about this "mind-stuff" and consciousness, it seems a little out of scope from the grand purpose of this book. Nonetheless it's fun to think about.

One of the final realms to explore is John A. Leslie's own position of an almost "ethical requiredness" or a need for goodness. I found Leslie to be a sound and logical philosopher but I did not enjoy that the bulk of his explanations seemed to hinge on analogies. Perhaps this is far more prevalent in modern philosophy but something inside me objects to using paintings to explain how universes are enumerated. The example I'm talking about is the question of why, if goodness is a prerogative, would there be infinitely many universes conceptually available but only ours in existence (which is of some arbitrary goodness). And Leslie explains this by saying that the diversity of goodness in the universes is analogous to why the Louvre has paintings of various quality instead of having its walls packed with perfect replicas of the Mona Lisa. I understand his premises and his analogy but I don't see the value of arbitrary selection of a universe — this "axiarchic theory." Both Leslie and Holt reference Dawkin's response of calling goodness a piffling concept and noting that cosmologically it's as arbitrary as "Channel Number Fiveness." And this is the premise of Leslie's assertions: that "Goodness is required existence, in a nontrivial sense." Holt notes that Leslie is a sort of modern-day Spinoza.

The last philosopher on Holt's journey is Derek Parfit who, among other things, discusses the idea of a "selector" with Holt. Parfit breaks down our existence into how and why which is an interesting way to look at it when you consider the selector to be a mechanism that selects (or doesn't select) our universe out of all the possibilities. If the selector is something, then you have to explain the selector of the selector or the meta-selector. For example: The null hypothesis (the world of Nothing) has the selector of simplicity and no meta-selector. Also, by some sound logic and reasoning the two come to the conclusion that a selector can't select itself thus looping backwards and explaining its selection. Armed with this, the author tries his hand at proving which of these explanations and meta-explanations are valid and comes to a conclusion. Similar to my earlier complaints, the biggest problem I have with this is that his method is to rule out the combinations of meta-selectors and selectors until he is down to one or two. How does he know that the explanations for his options in this book amount to the entirety of the possibilities of selectors and meta-selectors? To rule out all possibilities but one in order to understand this seems futile since we may not be able to imagine all selectors and meta-selectors possible.

The very last person interviewed for the book is John Updike. Although he had some interesting things to say, this felt more like an intellectual artist's view of why there is something rather than nothing. Updike says he is part of the group that find this existence to be "a kind of miracle" and he calls this a "last resort, really of naturalistic theology." There's a bit of cute wordplay in this last chapter but it felt appropriate to read it near the end of this journey. Updike gets to weave characters into plots and embed the aforementioned logic and views into those stories. And given that background and his interest in this topic, he playfully left me with an "it's not so bad that we don't know" sort of lightheartedness.

The penultimate chapter of this book deals with the question of whether we seriously exist at all. I think it would have been better for Holt to approach this from a nurture versus nature standpoint that's already been heavily discussed before. He does pose some interesting thought exercises like a procedure that replaces diseased brain matter with healthy brain matter that has no recollection or memories but it only does it 1% of my brain matter at a time. At what point would I cease to be me? So there's some interesting ideas in here but the chapter is largely disagreeable with me. I know that every person I meet knows at least one thing I don't and I like to use such a basic pairwise comparison to justify unique existence. I don't find much value in considerations of the self on a transcendental level and that's probably why this chapter didn't have a lot of value to me.

Throughout the book, Holt has been relaying to us his day to day experiences including the death of his dog. He also noted that Updike died fairly suddenly months after he spoke with him. In the final chapter "Return to Nothingness," Holt does a little work of tying what this all means into the context of death. During the writing of this book, his mother passed away and the final pages are devoted to that account and his emotions. If Updike was a jocular relief about existence, this final chapter is a sobering reminder that ultimately we are all mortal. While well written and heavily symbolic, it is a depressing note on which to end this journey.

I thoroughly enjoyed this book. It's composition is a good mix of art and science making it a light read compared to others about the same topic. If you're looking for thought experiments or wish to further ply yourself with a good survey of the current armaments in this debate, you can buy Why Does the World Exist? from Amazon. Slashdot welcomes readers' book reviews — to see your own review here, read the book review guidelines, then visit the submission page.

MassDosage writes "After nearly 15 years or of writing code professionally it was refreshing to take a figurative step back and read a book aimed at people getting started with computer programming. As the title suggests, Think Like A Programmer tries to get to the core of the special way that good programmers think and how, when faced with large and complex problems, they successfully churn out software to solve these challenges in elegant and creative ways. The author has taught computer science for about as long as I've been programming and this shows in his writing. He has clearly seen a lot of different people progress from newbie programmers to craftsmen (and craftswomen) and has managed to distill a lot of what makes this possible in what is a clear, well-written and insightful book." Read below for the rest of Mass Dosage's review. Think Like A Programmer author V. Anton Spraul pages 256 publisher No Starch Press rating 8/10 reviewer Mass Dosage ISBN 978-1-59327-424-5 summary An Introduction to Creative Problem Solving Think Like A Programmer is probably best read by those with at least a year's experience with programming, such as first or second year computer science students or those picking up programming on their own. The code examples in the book are all written in C++ so a basic knowledge of C++ syntax is required but this should be easy to pick up by anyone with familiarity with related or similar languages. Experienced programmers looking to brush up on their fundamentals will most likely find something useful here too. They probably do a lot of what is suggested here already without being aware of it but it can be encouraging to see this formalized in a book. I found it gratifying to see that some of the techniques I use daily were covered here — it's good to know that I'm not the only one who scrawls down funny diagrams and sketches out a rough plan before actually typing any code.

Different types of problem solving are discussed in separate chapters which cover the use of data structures, pointers, recursion and code libraries before wrapping up with a final chapter that brings all the previous approaches together. The book is intended to be read in its entirety with later chapters making frequent references to topics covered earlier. Think Like A Programmer is not a cheat sheet or cook book with quick fixes but a more substantive book that rewards those who read it as thoroughly as it has been written. Each chapter contains a few examples which are used to explain the topic under discussion and these have been well chosen to illustrate the key concepts. A series of exercises are also included which build on and extend each chapter. The author stresses that if the reader really wants to learn something and improve their problem solving skills then these exercises should be considered even more important than the text. The best way to learn how to program is by doing and the exercises force one to put what one has just learned into practise. The first few exercises at the end of a chapter are relatively simple and are basically variations on the examples that help the reader build confidence before moving into more challenging and tricky exercises that push one to apply one's recently acquired knowledge to new limits.

Throughout the book everything is explained in a good level of detail and enough background information is provided so that the reader should never feel out of their depth. The pros and cons of the various presented solutions are clearly weighed up with logical backing. The author is obviously very knowledgeable and experienced with teaching hard concepts to new learners and this shows in his no-nonsense, down-to-earth but enjoyable writing style. The code samples are clear and well thought out as are the diagrams that accompany the various examples. The chapter on classes was the only one where I felt like focus was being lost due to too many C++ implementation details but perhaps that's just the nature of the language. I would have liked the example here to show more clearly how classes can turn a morass of functional code into something more logically grouped and easier to understand. To be fair, the exercises at the end of this chapter do ask one to do this by asking one to convert a collection of string utility functions into a more logically organized string class. This again shows the importance of actually doing the exercises and not just simply reading them.

The core idea of how programmers take a complex problem and then break this down into smaller, more manageable and solvable parts is well described. The importance of having a plan before jumping in and writing code without thinking is stressed and there are great suggestions for how to take stock of your own personal strengths and weaknesses and come up with a personal plan that works for you. The example is given of someone who likes jumping right into coding — for someone like this it probably makes sense for them to do early prototyping as a way to start solving a particular problem, as long as the longer term plan involves taking a step away from this and incorporating the lessons learned into a more thoroughly thought out solution later. In this, as in the rest of the book, the author shows his years of experience teaching a wide range of people with different skill sets and approaches to problem solving. There is no single way to think like a programmer, but rather a number of tried and tested strategies that can be employed in various ways. Think Like A Programmer captures this core idea in an satisfying, down to earth manner and I can highly recommend it to anyone wanting to improve their problem solving capabilities. I wish I had had this book when I started studying computer science — the fundamentals contained here would have been a valued addition to the text books teaching syntax and specific technologies.

You can purchase Think Like A Programmer from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Michael Ross writes "Of all the open source content management systems used for building websites, Drupal has a reputation for being one of the most flexible and powerful available, but not the easiest for web designers to use. Drupal version 7 has made some strides in alleviating those flaws, but there is still much progress to be made. During the past few years, a number of books have been published that explain how Drupal designers can do custom theming, but they tend to focus on the technical details of the theme layer, and not the practice of web design when using Drupal as a foundation. That rich yet neglected subject area is the focus of a new book, Drupal for Designers: The Context You Need Without the Jargon You Don't." Keep reading to see what Michael has to say about the book. Drupal for Designers author Dani Nordin pages 328 pages publisher O'Reilly Media rating 8/10 reviewer Michael J. Ross ISBN 978-1449325046 summary How to design and manage Drupal projects. The book's author, Dani Nordin, is a Massachusetts-based web designer and the founder of The Zen Kitchen, a UX design business. The book was published by O'Reilly Media, on 1 August 2012, under the ISBN 978-1449325046. The publisher's page offers a description of the book, the table of contents, an author bio, and some free sample content (the first chapter). This publication is a compilation of three previously-released short guides — Planning and Managing Drupal Projects, Design and Prototyping for Drupal, and Drupal Development Tricks for Designers — with additional material. All of these books were written by Dani Nordin, and comprise the "Drupal for Designers" series by O'Reilly Media. (My thanks to the publisher for a review copy of this particular title.)

The book's material spans 328 pages, and is organized into seven parts, which do not include the introduction or the first chapter. The seven parts — each comprising at least two chapters — are largely presented in the same order that a typical reader would want to learn and implement the recommendations: Discovery and User Experience; Sketching, Visual Design, and Layout; Setting Up a Local Development Environment; Prototyping in Drupal; Making It Easier to Start Projects; Working with Clients; and Sample Documents.

Unlike most introductory Drupal books, this one wisely begins with a helpful dictionary of Drupal terminology. The first chapter also discusses the phases that compose a typical Drupal project lifecycle. Sandwiched in between is some guidance on where to place custom code in a Drupal directory system. The author advises that "Any module, theme, or other customization that you create for your site should always reside in sites/all" (page 2, and also reflected on pages 1 and 5). That may be true of contrib modules and themes, but certainly not custom ones, which are better located in sites/default or sites/[domain name]. She states that a child theme should be "stored separately in sites/all/<client_name>" (page 4). Actually, they should be placed in "sites/default/themes" or the themes subdirectory of a domain name directory. Finally, she recommends that for a multisite installation, one should keep "everything in sites/all" (page 5). Lumping everything into the "all" subdirectory would defeat the fundamental mechanism of multisite, which allows one to host multiple sites on a single Drupal installation, with their custom files and settings separated by domain name.

The first part of the book is loaded with valuable counsel on how to conduct the discovery phase of a website project, including coverage of project goals, user experience (UX), mockup tools, user personas, wireframes, prototypes, and the key components of a short-form project brief. It is evident from the narrative that the author is drawing upon a great deal of real-world experience, as well as lessons learned from other veteran web designers. The only blemish is where the author refers to "the project brief in Section 8" (page 45, repeated on page 254), and yet there appears to be no such section in the book. Perhaps she means Appendix A, which has an example project brief.

Once a design team has completed and received sign-off on a project brief — as well as any wireframes and other helpful preliminaries — a logical next step is to build the initial visual design. In the second part of the book, the author demonstrates how she uses sketches, style tiles, layout elements, greyboxing, grid systems, and Fireworks templates for crafting a visual design for a website. Throughout these chapters, she uses a redesign of her own personal website to illustrate the material. Both this part and the previous part of the book contain little information that is specific only to Drupal; thus, it could be useful to designers building websites using other CMSs.

Some readers of the book may already have up-to-date Drupal environments installed and configured on their development web servers. For those who do not, Part III will likely be appreciated, especially if the reader is using a Mac machine, because that is the environment to which the text and screenshots are geared. The author contends that "Windows seems to add an annoying layer of complexity to most of the command-line stuff" (page 102). Yet from my own experience, installing and using Git and Drush on a Windows PC is largely the same as in a Linux environment. Most developers complain that the main hurdle is Git's unintuitive workflow, which is independent of the operating system. The author touches upon some other tools, such as LESS and phpMyAdmin. Chapters 9 and 10 focus on Drush and Git, respectively. The last chapter in this section steps the reader through installing MAMP and Drupal. The discussion is generally comprehensible, except for the first paragraph on page 132, which is arguably the most confusing in the entire book. For instance, echoing a misstep seen earlier, it advises that all changes to your Drupal site should be stored in the sites/localhost directory, which contradicts the advice on the previous page, that all customizations to the site should be located in the sites/all directory.

The fourth part of the book covers prototyping in Drupal: gleaning from the client the information needed to define the content types for the website; choosing the appropriate modules for implementing the desired functionality; using views for displaying data; improving the HTML generated by views; creating custom Drupal themes; and using LESS to better manage the CSS within a theme. The advice is on target, except for the recommendation to use the Submit Again module, which does not have a Drupal 7 release, and has been replaced by the Add another module. Readers who are having difficulty locating the User Reference module mentioned by the author (page 187), can find it as a submodule in the References project. Lastly, the author instructs the reader to enable any base theme used (page 217), but actually it does not need to be enabled; installation alone is sufficient.

Part V, the briefest of them all, explains how to utilize the Features module, as well as Drush Make and installation profiles. Part VI comprises three chapters which offer guidance on how to propose an estimate for new projects, how to push back on unreasonable client requests, and how to learn from and document a finished project. This material is so closely related to that presented in the first part of the book — project discovery, planning, project briefs, etc. — that these final three chapters should have been incorporated into that earlier part. In fact, the first paragraph of this part states that it describes a phase of the discovery process that should be conducted prior to the phase described in Part I. Nonetheless, the author provides smart tips on some of the more difficult aspects of project management. The last part of the book comprises three appendices with sample documents — specifically, a project brief, a work agreement, and a project proposal.

On the publisher's page for the book, no errata have been reported, at this time. That is likely because the book appears to contain remarkably few errata: "What if there was" (pages 81 and 245; "was" should be "were"); "get familiar [with] the command line" (page 108); "a couple of" (page 172; should be "a few," as it is referencing three bullet points); ".less" (page 208, twice; should be "LESS"); "carpal tunnel[s]" (page 231); "original code [for] a feature" (page 242); and ".tpl" (page 266; should be ".tpl.php"). This is certainly a low number of errata for a technical book of this size. Kudos to the author and the O'Reilly editing team.

Overall, the book's style is clear and conversational, with only a few rough patches. Incidentally, the terms "directory" and "folder" are synonymous, but newbie readers who do not understand this could be confused when the two terms are used interchangeably, especially within the same sentence (e.g., page 109). Interspersed at various points in the text are interviews with people involved in web design, entitled "From the Trenches," which add perspective from designers other than the author. The reader will also find some natural humor and humility, which is always welcome in a technical work.

The author and publisher have made good use of the many screenshots, showing sample designs, Drupal user interface pages, etc. Unfortunately, for the Drupal pages, the admin theme used is the default, Seven, which results in black text on a gray background — a poor choice for such wide screenshots being compressed into small images on the page. Consequently, much of the text is barely legible, especially for anyone with imperfect eyesight.

From a technical point of view, the information provided is accurate and worthwhile. The only serious problem is the misleading advice, noted above, concerning the placement of custom modules and themes within the directory structure of a Drupal project — which was undoubtedly unintentional. The reader will encounter some HTML markup, a lot more CSS, and a minimal amount of PHP code. All of it is neatly formatted, and the only apparent problem is where a snippet of example code includes invalid nested "<?php" tags (page 188).

Despite these minor blemishes, this is one of the better-written Drupal books on the market. Web designers who will be working on Drupal projects, should be well rewarded in choosing this book as a solid starting point for their studies.

Michael J. Ross is a freelance web developer and writer.

You can purchase Drupal for Designers from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

benrothke writes "In the documentary Scared Straight! a group of inmates terrify young offenders in an attempt to 'scare them straight'" (hence the show's title) so that those teenagers will avoid prison life. A 2002 meta-analysis of the results of a number of scared straight and similar intervention programs found that they actively increased crime rates, leading to higher re-offense rates than in control groups that did not receive the intervention. For those considering the use of social media in their business, it is quite easy to read Navigating Social Media Legal Risks: Safeguarding Your Business as a scared straight type of reference. Author Robert McHale provides so many legal horror stories, that most people would simply be too afraid of the legal and regulatory risks to every consider using social media." Keep reading for the rest of Ben's review. Navigating Social Media Legal Risks: Safeguarding Your Business author Robert McHale and Eric Garulay pages 320 publisher Que rating 10/10 reviewer Ben Rothke ISBN 978-0789749536 summary Definitive guide to social media law for the layman But the reality is that social media is becoming required for nearly every business. With that, Navigating Social Media Legal Risks, author and attorney Robert McHale, with Eric Garulay, provide a fascinating and invaluable reference to any organization that wants to use social media, and not violate any of the myriad state, federal and international laws and regulations.

Social media makes it relatively easy for organizations to find and retain customers and increase sales, amongst many other benefits. At the same time, it can expose an organization to significant and highly-expensive legal risks and issues, and find themselves at the receiving end of a subpoena.

The books 12 chapters take a look at various aspects of social media and details how to use them in a legal and judicious manner.

In chapter 1, the book details social media promotions law around contests and sweepstakes. People often use the terms contest and sweepstake interchangeably, but the words have very different meanings. There are various contests and sweepstakes laws that must be dealt with before these promotions can commence. Often web sites will combines elements of contests and sweepstakes, include prizes, chances and considerations, which in turn make it a lottery. The issue is that it is illegal for most entities to create a lottery. So if not done correctly, a simple contest can turn into a costly legal mess.

Chapter 2 deals with online endorsements and testimonials. Any company that will use online endorsements and testimonials in their advertising must ensure that they are following all truth in advertising laws. The book details numerous areas where regulators have launched investigations and taken enforcement actions against violators. The book notes that one rogue blogger will not likely trigger a law enforcement action if your company has a reasonable training and monitoring program in place.

Chapter 5 shows how to manage the legal risks of UGC (user-generated content). UGC can drive significant amounts of traffic to a web site, but also creates legal risks.

Organizations can find protection from UGC via the Digital Millennium Copyright Act (DMCA) and the Communications Decency Act of 1996 (CDA). But those firms that want to enjoy the protections of the DMCA and CDA are required to fully comply with a very detailed set of legal requirements, leaving them very little room for error. The chapter details how to avoid those errors.

The book has scores of examples of things many readers may not have thought about. For example, chapter 8 writes of the Anticybersquatting Consumer Protection Act (ACPA). The purpose of the ACPA is to protect consumers and American businesses and provide clarity in the law for trademark owners by prohibiting the bad-faith and abusive registration of distinctive marks as Internet domain names with the intent to profit from the goodwill associated with such marks-a practice commonly referred to as cybersquatting.

Yet what about the post-domain path of a URL, which is everything after the domain name. Of which question is, are post-domain path names protected under the ACPA? For example, is the post-domain path of twitter.com/Boeing owned by Boeing or simply the person who registered it first? The courts are grappling with that and similar questions.

In chapter 9, the authors detail the need for designing a geolocation data security plan. This is particularly important for firms that handle consumer's geolocation data. Such a plan is particularly important given that the tracking, storage and sharing of precise geolocation information is becoming increasingly subject to legal and regulatory requirements..

The book concludes with 10 social media lessons that details some noteworthy social media business entanglements and the lessons that businesses must learn from them. A few of these include: your Twitter hashtag can be used against your, do not pay for or use false endorsements and other invaluable lessons. The advice in these 10 tips alone are worth the price of the book.

Each chapter ends with detailed tactical lists of dos and donts around the specific topic.

The book should be required reading for every organization. Even those firms that have completely rejected any form of corporate social media interaction can still be held liable for actions of their employees. So such firms can't simply bury their head in the sand.

At $30, Navigating Social Media Legal Risks: Safeguarding Your Business is the cheapest legal advice you can get, and is worth every penny. If you are looking for crystal clear and detailed advice on social media law, you won't find a better book.

The world of social media is fraught with legal danger which can be quite expensive and embarrassing to recover from. It lives up to its title, and provides an outstanding path to navigate the dangerous waters of social media.

Ben Rothke is the author of Computer Security: 20 Things Every Employee Should Know.

You can purchase Navigating Social Media Legal Risks: Safeguarding Your Business from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

benrothke writes "In the documentary Scared Straight! a group of inmates terrify young offenders in an attempt to 'scare them straight'" (hence the show's title) so that those teenagers will avoid prison life. A 2002 meta-analysis of the results of a number of scared straight and similar intervention programs found that they actively increased crime rates, leading to higher re-offense rates than in control groups that did not receive the intervention. For those considering the use of social media in their business, it is quite easy to read Navigating Social Media Legal Risks: Safeguarding Your Business as a scared straight type of reference. Author Robert McHale provides so many legal horror stories, that most people would simply be too afraid of the legal and regulatory risks to every consider using social media." Keep reading for the rest of Ben's review. Navigating Social Media Legal Risks: Safeguarding Your Business author Robert McHale and Eric Garulay pages 320 publisher Que rating 10/10 reviewer Ben Rothke ISBN 978-0789749536 summary Definitive guide to social media law for the layman But the reality is that social media is becoming required for nearly every business. With that, Navigating Social Media Legal Risks, author and attorney Robert McHale, with Eric Garulay, provide a fascinating and invaluable reference to any organization that wants to use social media, and not violate any of the myriad state, federal and international laws and regulations.

Social media makes it relatively easy for organizations to find and retain customers and increase sales, amongst many other benefits. At the same time, it can expose an organization to significant and highly-expensive legal risks and issues, and find themselves at the receiving end of a subpoena.

The books 12 chapters take a look at various aspects of social media and details how to use them in a legal and judicious manner.

In chapter 1, the book details social media promotions law around contests and sweepstakes. People often use the terms contest and sweepstake interchangeably, but the words have very different meanings. There are various contests and sweepstakes laws that must be dealt with before these promotions can commence. Often web sites will combines elements of contests and sweepstakes, include prizes, chances and considerations, which in turn make it a lottery. The issue is that it is illegal for most entities to create a lottery. So if not done correctly, a simple contest can turn into a costly legal mess.

Chapter 2 deals with online endorsements and testimonials. Any company that will use online endorsements and testimonials in their advertising must ensure that they are following all truth in advertising laws. The book details numerous areas where regulators have launched investigations and taken enforcement actions against violators. The book notes that one rogue blogger will not likely trigger a law enforcement action if your company has a reasonable training and monitoring program in place.

Chapter 5 shows how to manage the legal risks of UGC (user-generated content). UGC can drive significant amounts of traffic to a web site, but also creates legal risks.

Organizations can find protection from UGC via the Digital Millennium Copyright Act (DMCA) and the Communications Decency Act of 1996 (CDA). But those firms that want to enjoy the protections of the DMCA and CDA are required to fully comply with a very detailed set of legal requirements, leaving them very little room for error. The chapter details how to avoid those errors.

The book has scores of examples of things many readers may not have thought about. For example, chapter 8 writes of the Anticybersquatting Consumer Protection Act (ACPA). The purpose of the ACPA is to protect consumers and American businesses and provide clarity in the law for trademark owners by prohibiting the bad-faith and abusive registration of distinctive marks as Internet domain names with the intent to profit from the goodwill associated with such marks-a practice commonly referred to as cybersquatting.

Yet what about the post-domain path of a URL, which is everything after the domain name. Of which question is, are post-domain path names protected under the ACPA? For example, is the post-domain path of twitter.com/Boeing owned by Boeing or simply the person who registered it first? The courts are grappling with that and similar questions.

In chapter 9, the authors detail the need for designing a geolocation data security plan. This is particularly important for firms that handle consumer's geolocation data. Such a plan is particularly important given that the tracking, storage and sharing of precise geolocation information is becoming increasingly subject to legal and regulatory requirements..

The book concludes with 10 social media lessons that details some noteworthy social media business entanglements and the lessons that businesses must learn from them. A few of these include: your Twitter hashtag can be used against your, do not pay for or use false endorsements and other invaluable lessons. The advice in these 10 tips alone are worth the price of the book.

Each chapter ends with detailed tactical lists of dos and donts around the specific topic.

The book should be required reading for every organization. Even those firms that have completely rejected any form of corporate social media interaction can still be held liable for actions of their employees. So such firms can't simply bury their head in the sand.

At $30, Navigating Social Media Legal Risks: Safeguarding Your Business is the cheapest legal advice you can get, and is worth every penny. If you are looking for crystal clear and detailed advice on social media law, you won't find a better book.

The world of social media is fraught with legal danger which can be quite expensive and embarrassing to recover from. It lives up to its title, and provides an outstanding path to navigate the dangerous waters of social media.

Ben Rothke is the author of Computer Security: 20 Things Every Employee Should Know.

You can purchase Navigating Social Media Legal Risks: Safeguarding Your Business from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

theodp writes "The NYT's Steve Lohr reports that his has been the crossover year for Big Data — as a concept, term and marketing tool. Big Data has sprung from the confines of technology circles into the mainstream, even becoming grist for Dilbert satire ('Big Data lives in The Cloud. It knows what we do.'). At first, Jim Davis, CMO at analytics software vendor SAS, viewed Big Data as part of another cycle of industry phrasemaking. 'I scoffed at it initially,' Davis recalls, noting that SAS's big corporate customers had been mining huge amounts of data for decades. But as the vague-but-catchy term for applying tools to vast troves of data beyond that captured in standard databases gained world-wide buzz and competitors like IBM pitched solutions for Taming The Big Data Tidal Wave, 'we had to hop on the bandwagon,' Davis said (SAS now has a VP of Big Data). Hey, never underestimate the power of a meme!"

Ian Lamont writes "LendInk, a community for people interesting in using the lending features of the Kindle and Nook, has been shut down after some authors mistakenly thought the site was hosting pirated ebooks. The site brought together people who wanted to loan or borrow specific titles that are eligible for lending, and then sent them to Amazon or BarnesAndNoble.com to make the loans. Authors and publishers who were unaware of this feature of the Kindle and Nook, and/or mistakenly assumed the site was handing out pirated copies, were infuriated. LendInk's hosting company received hundreds of complaints and shut the site down. LendInk's owner says: 'The hosting company has offered to reinstate Lendink.com on the condition that I personally respond to all of the complaints individually. I have to say, I really do not know if it is worth the effort at this point. I have read the comments many of these people have posted and I don't think any form of communication will resolve the issues in their eyes. Most are only interested in getting money from me and others are only in it for the kill. They have no intentions of talking to me or working this out. So much for trying to start a business and live the American Dream.'"

Quince alPillan writes "Netflix revealed today that they've released Chaos Monkey, an open source Amazon Web Service testing tool that will randomly turn off instances in Auto Scaling Groups. 'We have found that the best defense against major unexpected failures is to fail often. By frequently causing failures, we force our services to be built in a way that is more resilient. We are excited to make a long-awaited announcement today that will help others who embrace this approach. ...source code for the founding member of the Simian Army, Chaos Monkey, is available to the community.'"

thatpythonguy writes "Core Python Application Programming is the latest addition to a growing corpus of literature serving a growing number of Python programmers and engineers. This Prentice Hall book of 800+ pages covers some traditional areas and touches upon some new ones. I typically do not spend much time speaking about the author of the books that I review; however, this occasion warrants an exception. And it is not because Wesley Chun used Python over a decade ago to build the address book and spell-checker for Yahoo! Mail nor is it because he holds a minor degree in music from UC Berkeley in classical piano. Rather, it is because he is both an engineer and an instructor. In other words, he was not pulled from his geek duties and asked to become a pseudo-writer; he already does that for his consulting practice, authoring (or co-authoring) several books and articles on Python (including "Python Web Development with Django") as well as starring in his own training video (entitled "Python Fundamentals"). The result of that experience is a writing style that is technically sound, yet accessible." Keep reading for the rest of Ahmed's review. Core Python Applications Programming author Wesley J. Chun pages 888 publisher Prentice Hall rating 8/10 reviewer Ahmed Al-Saadi ISBN 978-0132678209 summary Python application programming for intermediate python engineers The book followed the normal evolutionary path of other books in its class. It started out as the second part of "Core Python Programming" and ended up being split into its own volume in its third edition. The first part became "Core Python Language Fundamentals" which covers the core language. This volume covers the natural successor topics of "now what?" that the first raises: the use of Python in various applications. It is for this reason that the book recommends that the reader be an intermediate Python programmer. I think "intermediate" here refers to anyone who has read an introductory book or followed a tutorial on the core language.

The book covers the two main lines of python development: 2.x and 3.x. Despite the slow adoption of the 3.x line due to its backward incompatibility, there are already popular third-party libraries that have been ported to that line and that occurrence will only increase moving forward. Chun does a very good job balancing the two by providing concurrent examples (i.e., code snippets) in both flavours. He also has numerous references and side notes indicating that certain features/libraries are only available for certain versions of the language.

There are three parts to the book: General Application Topics, Web Development, Supplemental/Experimental. The first includes the usual dosage of general chapters including regular expressions (regex), network programming (including an intro to the Twisted framework), Internet client programming, threading and multi-processing, GUI, and databases (including a taste of NoSQL). It is peculiar that it also includes chapters on Microsoft Office programming and writing Python extensions which are not general in my opinion. It is probably because these two chapters do not fit anywhere else! The second part is probably the core of Chun's own experience as he is a self-described "web guy". He certainly goes into details in that domain covering web clients/servers (yes, he writes a small web server!), general web programming (i.e., CGI and WSGI), the Django framework, cloud computing (mostly Google App Engine; GAE), and web services. Finally, the last part has two chapters on text processing and miscellaneous topics (basically, Jython and Google+). I find the naming of the text processing chapter rather poor given that it is about processing comma-separated values (CSV), JavaScript Object Notation (JSON), and Extensible Markup Language (XML). Arguably, "text processing" is more descriptive of regex, transcoding, and Unicode! Two appendices at the end of the book provide some background and a guide to Python 3.x migration.

Chun spends some time delving into a problem domain in addition to providing the Python solution. For example, he describes the regular expression syntax in detail and spends time explaining the client-server architecture using real-life analogies to drive his points home. His code examples are well-structured, object-oriented solutions that range from the demonstrative to the practical. For example, in the Django chapter, he builds a practical Twitter application that uses third-party libraries and some advanced features. However, do not expect a cookbook-style coverage nor production-ready code from a book of this nature. Do expect many exercises with partial solutions at the end of the book.

I find Chun's approach to be pedagogically sound. His ideas flow logically from one to the next, incrementally building a story-like chain of problems and Python solutions. He highlights architectural patterns that are shared by disparate problem domains (e.g., the event-driven nature of SocketServer and Tkinter), leading to a better understanding of both. However, he does leave out many topics from his coverage for applications in compression, cryptography, and date handling (among others). Maybe he considers these to be ancillary or simple enough to be looked up in Python's own standard library documentation. Also, as a Developer Advocate for Google, it is not surprising to see him cover the GAE in depth. Specifically, I think for anyone who is interested in running Django on the GAE, he can be an excellent (and accessible, by his own admission) resource. Google him (no pun intended!) to see his presentation on "porting" Django applications to the GAE.

Finally, the book is aesthetically type-set and is well-structured. I think that it has a wealth of well-written information that cover key areas of Python application development that will be useful to a broad spectrum of readers.

Ahmed Al-Saadi is a software consultant based in Montreal, Canada. He mainly speaks Python, Erlang, and Objective-C these days.

You can purchase Core Python Applications Programming, 3rd ed from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

itwbennett writes "Amazon, which has come under attack for harsh warehouse working conditions, on Monday announced a new training benefit program for fulfillment center employees. The program will cover 95% of the cost of vocational training for jobs that Amazon determined to be in high demand and that pay relatively well, including aircraft mechanics, computer-aided design, machine tool technology, medical laboratory science and nursing." Two limitations of note: the maximum Amazon will contribute is $2,000/year for four years, and the employees need to have worked full-time for three consecutive years before they can take advantage of the program.

TwobyTwo writes "Yesterday, Slashdot posted a piece titled Who Really Invented the Internet?. It quoted a Wall Street Journal article with the same title by Gordon Crovitz. Crovitz makes the claim that government research did not play a key role in driving the invention of the Internet, giving credit instead to Xerox PARC. Unfortunately, Crovitz' article is wrong on many specific points, and he's also wrong in his key conclusion about the government's role. In a wonderful piece in the LA Times Michael Hiltzik corrects the record. Hiltzik, who is the author of an excellent book about PARC called Dealers of Lightning, makes clear that government funded research was indeed the foundation for the Internet's success."

benrothke writes "Anyone who has worked in information technology knows of Gartner. They are one of the leading information technology research and advisory firms. Most of their clients are CIOs and senior IT leaders in corporations and government agencies, high-tech and telecom enterprises. Gartner is huge with over 5,000 associates, over 1, 200 research analysts and consultants and clients in 85 countries. Their revenue in 2011 was nearly $1.5 billion. While Gartner is the world's largest, there are over 650 independent analyst firms worldwide. Barbara French's Directory of Analysts provides a comprehensive list. With all that, very few people understand how Gartner works and what makes them tick. In UP and to the RIGHT: Strategy and Tactics of Analyst Influence: A complete guide to analyst influence, ex-Gartner analyst Richard Stiennon takes the mystery out of Gartner. In particular, a good part of the book deals with Gartner's vaunted Magic Quadrant." Read below for the rest of Ben's review. UP and to the RIGHT: Strategy and Tactics of Analyst Influence: A complete guide to analyst influence author Richard Stiennon pages 186 publisher IT-Harvest Press rating 9/10 reviewer Ben Rothke ISBN 0985460709 summary Definitive guide on Gartner and their Magic Quadrant The Magic Quadrant (MQ) is Gartner's proprietary research tool that according to them provide a qualitative analysis into a market and its direction, maturity and participants, thus possibly enabling a company to be a stronger competitor for that market. Every, and I mean every tech vendor strives to be recognized by Gartner be on a prominent post on the MQ.

Today there are hundreds of different MQ's for sectors from firewalls, cloud services to web hosting and everything in between.

For those not Gartner clients, buying a specific MQ can be expensive. But vendors often use the MQ to tout their product and pay to make them publicly available. Some examples of the freely-available are the MQ for:Secure Web Gateways, Security Information and Event Management and Web Fraud Detection. A Google search of the term with the PDF format will also reveal numerous free versions.

The book derives its name based on the best place for a company to be on the MQ. Up and to the right is where Gartner places market leaders which is nirvana for a tech firm. The other locations on the quadrant are: niche player, visionary and challenger. But for a tech firm, there is only one location, and that is up and to the right.

The MQ itself has two markers; completeness of vision, which defines features and innovative enhancements. The other is ability to execute, which is determined by revenue, number and quality of resellers and distributors, number of employees and their distribution between engineering, sales, and support and other business issues.

If up and to the right is the desired location, how does one get there? For many tech firms, they often are clueless. In the book, Stiennon provides clear direction on how to get there. For those looking to make the expedition to the land of Gartner; this book is a veritable Berlitz Guide on how to safely make the journey.

A Gartner myth that will never go away and that Stiennon deals with on page 2 is the notion that getting on the MQ is simply a matter of paying for the privilege. He calls the notion of MQ pay to play completely false.

Chapter 2 is The Magic of Magic Quadrants and Stiennon details what it is and why vendors aspire for placement. Irrespective of its value, he notes that every time a new MQ comes out, the vendor has an opportunity to issue a self-congratulatory press release about it.

In chapter 6, Stiennon makes the somewhat depressing observation that the senior analysts at Gartner have not had hands-on experience with products for many years. Yet these same analysts often have huge influence on the very products they often don't understand in minutia.

In some ways, the book is akin to How to Win Friends and Influence People by Dale Carnegie. The only difference is that one is attempting to influence a Gartner analyst in the vendor's favor. In chapter 7, the book details how to find the influencers. Stiennon is a big fan of social media and gives a number of valuable methods to find the Gartner analysts in your sector.

One approach I think Stiennon is mistaken is with the use of Klout. He writes that Klout is a great tool for measuring relative influence, at least on social media of an analyst. That may be somewhat true, but for a large part is irrelevant. As I wrote in Some Observations on Klout Scores, Klout can and should be applauded for trying to measure this monstrosity called social influence; but their results of influence should in truth, carry very little influence.

I based this on the fact that Klout scores Funny One Liners and the legendary Tim O'Reilly as being equal; which is utterly absurd. You can do your own Klout analysis for similar irrelevant and meaningless Klout scores.

The MQ is not the only service Gartner offers. In chapter 8, Stiennon writes of SAS Day. SAS is the Gartner Strategic Advisory Service, where a vendor buys the services of an analyst for a day. He notes that the pay to play myth may arise from SAS; but observes that you are not buying the analyst's opinion, rather their time. Vendors can get a lot out of a SAS day, as it is a day-long bottoms-up analysis of their products, markets, sales strategies and more with an analyst who has a deep awareness of that sector.

Stiennon also provides a lot of pragmatic direction on SAS on how to prepare for the SAS day. Given the expense of the analyst and the need to have all of the key staffers there, he notes that getting an agenda planned, good conference rooms, nutritious meals and much more are key to getting the most out of the day.

Back to the MQ; Stiennon writes that every organization of size needs a dedicated analyst relations (AR) staff member. The AR person will be the conduit between the vendor and the analyst firm. While the AR person is critical, he writes that a firm should never pin the responsibility for missing a target of MQ placement on the AR person. Executing on the MQ strategy is the responsibility of the entire organization.

The book provides more pragmatic advice in chapter 12 where it details the use of Gartner conferences. Stiennon writes that firms invest huge sums to attend and sponsor Gartner conferences in the hope to get in front of and sell to leading CIO's. In many cases a single sale to a CIO that arises from a Gartner event will justify the huge expenses.

But even with that, many firms make the mistake of manning their booths at the conference with junior staffers and marketing people that can't speak to the CIO, while the CEO of the vendor firm is in the back of the booth on their cell phone. That is just one of a few major faux pas the chapter details and how then can be obviated.

The chapter also details a common sales mistake in staffing the booths with booth babes. He notes that the concept is gross and misogynistic.

Towards the end, the book closes with what not to do when dealing with Gartner. He gives two examples of firms that were on their negative side. After Oracle Under Fire was written, Oracle CEO Larry Ellison went on a tirade against Gartner.

In another case, ZL Technologies, an email archiving firm sued Gartner for over $1 billion in damages (even though it was worth a fraction of that) when an analyst said their products was not up to par.

The book closes with the observation that buyers need industry analysts, as the analysts see that changes that are coming in the industry and are able to forewarn their clients.

The book is an easy read, yet highly informative and insightful. Every chapter has Stiennon's real-world experience at Gartner and post-Gartner.

While Stiennon is ex-Gartner, never in the book does his disparage his former employer or denigrate their MQ methodology. Rather he shows ways in which the vendor can maximize the potential Gartner relationship and exposure.

Any technology executive, investor and everyone in their PR and marketing departments who are looking to be on the MQ, deal with Gartner or any advisory service, should make certain that UP and to the RIGHT: Strategy and Tactics of Analyst Influence: A complete guide to analyst influence is on their absolutely required reading list. The book provides myriad superb advice on everything you need to know about dealing with and being successful with Gartner.

Given the extraordinary costs involved with analysts and the preparation for analyst meetings, the books $22 price tag is an absolutely bargain combined with its indispensable content. Whether you are a niche player or leader, it is a book well worth reading.

Ben Rothke is the author of Computer Security: 20 Things Every Employee Should Know.

You can purchase UP and to the RIGHT: Strategy and Tactics of Analyst Influence: A complete guide to analyst influence from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

benrothke writes "Anyone who has worked in information technology knows of Gartner. They are one of the leading information technology research and advisory firms. Most of their clients are CIOs and senior IT leaders in corporations and government agencies, high-tech and telecom enterprises. Gartner is huge with over 5,000 associates, over 1, 200 research analysts and consultants and clients in 85 countries. Their revenue in 2011 was nearly $1.5 billion. While Gartner is the world's largest, there are over 650 independent analyst firms worldwide. Barbara French's Directory of Analysts provides a comprehensive list. With all that, very few people understand how Gartner works and what makes them tick. In UP and to the RIGHT: Strategy and Tactics of Analyst Influence: A complete guide to analyst influence, ex-Gartner analyst Richard Stiennon takes the mystery out of Gartner. In particular, a good part of the book deals with Gartner's vaunted Magic Quadrant." Read below for the rest of Ben's review. UP and to the RIGHT: Strategy and Tactics of Analyst Influence: A complete guide to analyst influence author Richard Stiennon pages 186 publisher IT-Harvest Press rating 9/10 reviewer Ben Rothke ISBN 0985460709 summary Definitive guide on Gartner and their Magic Quadrant The Magic Quadrant (MQ) is Gartner's proprietary research tool that according to them provide a qualitative analysis into a market and its direction, maturity and participants, thus possibly enabling a company to be a stronger competitor for that market. Every, and I mean every tech vendor strives to be recognized by Gartner be on a prominent post on the MQ.

Today there are hundreds of different MQ's for sectors from firewalls, cloud services to web hosting and everything in between.

For those not Gartner clients, buying a specific MQ can be expensive. But vendors often use the MQ to tout their product and pay to make them publicly available. Some examples of the freely-available are the MQ for:Secure Web Gateways, Security Information and Event Management and Web Fraud Detection. A Google search of the term with the PDF format will also reveal numerous free versions.

The book derives its name based on the best place for a company to be on the MQ. Up and to the right is where Gartner places market leaders which is nirvana for a tech firm. The other locations on the quadrant are: niche player, visionary and challenger. But for a tech firm, there is only one location, and that is up and to the right.

The MQ itself has two markers; completeness of vision, which defines features and innovative enhancements. The other is ability to execute, which is determined by revenue, number and quality of resellers and distributors, number of employees and their distribution between engineering, sales, and support and other business issues.

If up and to the right is the desired location, how does one get there? For many tech firms, they often are clueless. In the book, Stiennon provides clear direction on how to get there. For those looking to make the expedition to the land of Gartner; this book is a veritable Berlitz Guide on how to safely make the journey.

A Gartner myth that will never go away and that Stiennon deals with on page 2 is the notion that getting on the MQ is simply a matter of paying for the privilege. He calls the notion of MQ pay to play completely false.

Chapter 2 is The Magic of Magic Quadrants and Stiennon details what it is and why vendors aspire for placement. Irrespective of its value, he notes that every time a new MQ comes out, the vendor has an opportunity to issue a self-congratulatory press release about it.

In chapter 6, Stiennon makes the somewhat depressing observation that the senior analysts at Gartner have not had hands-on experience with products for many years. Yet these same analysts often have huge influence on the very products they often don't understand in minutia.

In some ways, the book is akin to How to Win Friends and Influence People by Dale Carnegie. The only difference is that one is attempting to influence a Gartner analyst in the vendor's favor. In chapter 7, the book details how to find the influencers. Stiennon is a big fan of social media and gives a number of valuable methods to find the Gartner analysts in your sector.

One approach I think Stiennon is mistaken is with the use of Klout. He writes that Klout is a great tool for measuring relative influence, at least on social media of an analyst. That may be somewhat true, but for a large part is irrelevant. As I wrote in Some Observations on Klout Scores, Klout can and should be applauded for trying to measure this monstrosity called social influence; but their results of influence should in truth, carry very little influence.

I based this on the fact that Klout scores Funny One Liners and the legendary Tim O'Reilly as being equal; which is utterly absurd. You can do your own Klout analysis for similar irrelevant and meaningless Klout scores.

The MQ is not the only service Gartner offers. In chapter 8, Stiennon writes of SAS Day. SAS is the Gartner Strategic Advisory Service, where a vendor buys the services of an analyst for a day. He notes that the pay to play myth may arise from SAS; but observes that you are not buying the analyst's opinion, rather their time. Vendors can get a lot out of a SAS day, as it is a day-long bottoms-up analysis of their products, markets, sales strategies and more with an analyst who has a deep awareness of that sector.

Stiennon also provides a lot of pragmatic direction on SAS on how to prepare for the SAS day. Given the expense of the analyst and the need to have all of the key staffers there, he notes that getting an agenda planned, good conference rooms, nutritious meals and much more are key to getting the most out of the day.

Back to the MQ; Stiennon writes that every organization of size needs a dedicated analyst relations (AR) staff member. The AR person will be the conduit between the vendor and the analyst firm. While the AR person is critical, he writes that a firm should never pin the responsibility for missing a target of MQ placement on the AR person. Executing on the MQ strategy is the responsibility of the entire organization.

The book provides more pragmatic advice in chapter 12 where it details the use of Gartner conferences. Stiennon writes that firms invest huge sums to attend and sponsor Gartner conferences in the hope to get in front of and sell to leading CIO's. In many cases a single sale to a CIO that arises from a Gartner event will justify the huge expenses.

But even with that, many firms make the mistake of manning their booths at the conference with junior staffers and marketing people that can't speak to the CIO, while the CEO of the vendor firm is in the back of the booth on their cell phone. That is just one of a few major faux pas the chapter details and how then can be obviated.

The chapter also details a common sales mistake in staffing the booths with booth babes. He notes that the concept is gross and misogynistic.

Towards the end, the book closes with what not to do when dealing with Gartner. He gives two examples of firms that were on their negative side. After Oracle Under Fire was written, Oracle CEO Larry Ellison went on a tirade against Gartner.

In another case, ZL Technologies, an email archiving firm sued Gartner for over $1 billion in damages (even though it was worth a fraction of that) when an analyst said their products was not up to par.

The book closes with the observation that buyers need industry analysts, as the analysts see that changes that are coming in the industry and are able to forewarn their clients.

The book is an easy read, yet highly informative and insightful. Every chapter has Stiennon's real-world experience at Gartner and post-Gartner.

While Stiennon is ex-Gartner, never in the book does his disparage his former employer or denigrate their MQ methodology. Rather he shows ways in which the vendor can maximize the potential Gartner relationship and exposure.

Any technology executive, investor and everyone in their PR and marketing departments who are looking to be on the MQ, deal with Gartner or any advisory service, should make certain that UP and to the RIGHT: Strategy and Tactics of Analyst Influence: A complete guide to analyst influence is on their absolutely required reading list. The book provides myriad superb advice on everything you need to know about dealing with and being successful with Gartner.

Given the extraordinary costs involved with analysts and the preparation for analyst meetings, the books $22 price tag is an absolutely bargain combined with its indispensable content. Whether you are a niche player or leader, it is a book well worth reading.

Ben Rothke is the author of Computer Security: 20 Things Every Employee Should Know.

You can purchase UP and to the RIGHT: Strategy and Tactics of Analyst Influence: A complete guide to analyst influence from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Michael Ross writes "All the leading content management systems (CMSs), including Drupal, use a combination of source code, in files, and user/configuration data, in a database. There may be some mixing of the two types of components — such as configuration settings stored in small files, or JavaScript code stored in the database — but most CMS-based websites generally employ this separation. One significant benefit is that updates to the non-custom code (the CMS's "core") can be easily made without overwriting user data or custom configuration settings. However, each website has its own copy of the core code, even if the websites reside on the same server — which wastes disk space and wastes developer time when all of those instances of core need to be updated. Thus there is growing interest in running multiple websites on a single core instance, despite the dearth of documentation for how to do so. For those in the Drupal world, one resource is a new book by Matt Butcher, Drupal 7 Multi Sites Configuration." Read below for the rest of Michael's review. Drupal 7 Multi Sites Configuration author Matt Butcher pages 100 pages publisher Packt Publishing rating 8/10 reviewer Michael J. Ross ISBN 978-1849518000 summary A tutorial on how to run multiple Drupal 7 web sites from a single installation. Released on 26 March 2012 by Packt Publishing under the ISBN 978-1849518000, the book spans 100 pages, organized into five chapters. For developers familiar with the subject — particularly those who have read the (few) articles that cover Drupal multisite — it may seem inconceivable that such a subject could fill an entire book. Yet for the countless Drupal developers and administrators who have encountered critical problems in implementing the advice proffered in the aforesaid articles, a definitive book could be invaluable. Even a brief perusal of the book's table of contents will show that there are more topics to be covered than one might have imagined. This review is based upon a print copy of the book kindly provided by the publisher. An electronic edition is available as well. More details can be found on the publisher's page, where visitors will find an overview, a table of contents, a brief author biography, and links for purchasing the print and electronic versions of the book.

In the first chapter, the author presents the fundamental ideas and many benefits of basing multiple Drupal websites on a single code base, known as "multi-site hosting." He discusses the most common configuration options, and then focuses on the one used throughout the book, namely, Drupal's built-in multi-site capability. One thinks of Drupal (and any other PHP applications) as running on top of the web server layer (typically Apache); so readers will likely be confused by the statement that virtual hosting "is a layer higher than Drupal's multi-site feature" (page 8). Aside from that, the discussion is straightforward.

The second half of the chapter provides detailed instructions on two methods for setting up a server for multi-site usage. The first method utilizes virtualization, specifically VirtualBox and Vagrant, which supposedly are ideal for spinning up disposable websites. However, the instructions for "Installing our tailored Vagrant project" quickly become problematic: The MultiSite Drupal Vagrant Profile directs the user to perform a git clone command, and then "cd multisite_drupal_vagrant_profile," which works fine, as that directory exists. But the next step, on page 15 of the book, calls for the reader to cd into "multisite_vagrant," which does not exist. Was the aforesaid directory intended? Apparently so, as otherwise the third command, "vagrant up," fails. Windows users, at the very least, may find these steps and those that follow to be quite perplexing. In my case, both VirtualBox and Vagrant initially appeared to fail installation; yet upon trying them again, they were apparently running. But certain operations discussed in the book, were never executed. I slogged my way through numerous cryptic error messages, and eventually gave up. Any other reader who experiences anything similar may also chuckle at the author's claim that "This made it easy to get an entire server environment configured and running without dealing with the nuances of configuration" (page 17). The second method presented for setting up a multi-site environment is to manually configure Apache and MySQL. Even though this approach is probably what most readers will settle upon, it is sadly given a backseat to Vagrant.

In the second chapter, "Installing Drupal for Multi-site," the author explains how to perform the standard Drupal 7 installation, but for three example instances. For those readers unable to get the Vagrant method working fully, or who for some other reason choose not to use it, the author's frequent references to Vagrant will likely be increasingly annoying. Fortunately, it tapers off about halfway through the chapter, as the author explicates the details of multi-site configuration, concluding with some tips on where the reader can find assistance if she encounters any difficulties during an install. The only flaw is, on page 41, where the author states that "the lines that typically need changing are highlighted," but none of them are.

The complexities of sharing configuration settings among multiple websites, compose the first topic addressed in the third chapter. All of the technical information appears to be sound, except for the advice on page 46 to add the line "global $conf;" in the shared settings PHP file, which is included in the site-specific settings files. A "global" keyword would only be needed if the line setting the array value $conf['site_slogan'] were inside a function, in which case the variable $conf would have only local scope without the keyword. The PHP documentation on variable scope notes that, for a (non-global) variable, its "scope spans included and required files as well." (I confirmed this with a quick test, in which a shared settings file changed the slogans of two different websites.) The author then explains how to share modules and themes among multiple websites, or keep them separate. The chapter concludes with information on how subthemes in separate Drupal 7 instances can use a single base theme.

The fourth chapter, "Updating Multi-site Drupal," focuses on the administration of multiple websites sharing Drupal code. Readers will learn of the numerous pitfalls that can catch the unwary (or at least the inexact). The fifth and final chapter, "Advanced Multi-sites," continues the discussion of other factors that can complicate and undermine working off a single Drupal code base: favicons in themes, robots.txt files, shared authentication, shared content, and other topics that one may never encounter if only working with simple websites — but could be critical otherwise. The only readily apparent flaw is his referring to the project at http://drupal.org/project/virtual_site as "the Virtual Site module" (page 80), when in fact it is the Virtual Sites module — not be confused with the actual Virtual Site module.

Unlike most Packt Publishing books, this one contains relatively few errata: "served [a] few" (on the first "About the Reviewers" page), "start its" (page 17; should read "start it"), "Drupal looks for, for site configuration" (page 30), "trouble shooting" (42), and a missing ")" in the first sentence on page 67. Scattered throughout the book are several instances of title case used inappropriately when referring to generic concepts that are not proper names, e.g., "Version Control System" (page 10). Fortunately, all of these flaws are quite minor, and should have been caught by the publisher's production team.

Some of the narrative is a bit redundant, such as a question being asked at the end of one section, only to be repeated at the beginning of the next section, sometimes more than once. The (unneeded) chapter summaries add to the repetition, as do the introductory paragraphs of each chapter, many of which merely tell the reader what she just read in the previous chapter. Yet the author's narrative style is generally clear and easy to understand.

The main problem with this book is the VirtualBox and Vagrant pair — specifically, the (unjustified) heavy emphasis upon them, and the spotty instructions for configuring them, which could easily confuse and discourage readers. The information is mostly confined to the first two chapters, yet all of it should have been left out, or consolidated and relegated to an appendix — especially as most readers would not use Vagrant for their development environments, and probably no one would use it for a live production environment.

But for anyone interested in setting up multiple Drupal-based websites that share a single code base, these blemishes are of little consequence. Although modest in size, Drupal 7 Multi Sites Configuration provides the most thorough coverage to date of this worthwhile yet oft-neglected subject.

Michael J. Ross is a freelance web developer and writer.

You can purchase Drupal 7 Multi Sites Configuration from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Michael J. Ross writes "Veteran computer programmers — adept with languages such as PHP, Perl, and JavaScript — typically have no trouble learning an additional language, often just by reading online tutorials and stepping through sample code. But for those new to programming, that approach can prove difficult and frustrating. Yet nowadays there appears to be growing interest among such people for learning how to write programs in Python, especially as it is seeing increasing use by Google and other organizations, and is often chosen as the primary teaching language in schools. For such budding programmers, one possible starting point is the book Head First Python." Read on for the rest of Michael's review. Head First Python author Paul Barry pages 494 pages publisher O'Reilly Media rating 6/10 reviewer Michael J. Ross ISBN 978-1449382674 summary A gentle introduction to the Python programming language. The book's author Paul Barry, is an experienced programmer and lecturer in computing science. The book was published by O'Reilly Media, on 7 December 2010, under the ISBN 978-1449382674. On the publisher's page, visitors can learn more about the book and its author, see feedback from readers, peruse the discussion forum, and read the errata identified so far (many of which appear to be fixed in the most recent printing). The book's example code is available from Head First Labs. It is packaged into a large Zip archive file, containing directories for all the chapters. Additional resources — such as test data — can be downloaded from a page on the website of the school where the author teaches, The Institute of Technology, Carlow in Ireland. (But don't bother trying to use the site's search functionality to find more information about him, because no search results are returned, as of this writing. Hmm, what is the Goidelic word for "fail?")

The book's material, spanning 494 pages, is organized into 11 chapters, plus a supplementary section for more advanced topics. In the first chapter, "Everyone loves lists," the author briefly explains how to find and install on one's computer Python and its IDLE development environment, if necessary. Oddly, he assumes that if it is already present on a Windows machine, then it will be found in the directory c:\Python31; this is repeated in the second chapter as well. More importantly, he mentions the (command-line) command to start the Python shell, but then immediately begins describing IDLE, without mentioning how to get it running. Most of the chapter explains how Python supports lists and functions, although the coverage of the latter topic is much too brief, considering how critical functions are in any programming language, including Python.

The second chapter shows how to bundle up functions into modules, and make them available to other developers through distribution utilities. This may be an important topic, yet it is inconceivable to me as to why, so early in the book, the author dives into the rather involved details of registering with PyPI and distributing a Python module to the rest of the world, before even introducing such language basics as input/output, files, and objects. (More on that later.)

If the reader perseveres through all the flaws in the first two chapters, then she will likely find that the quality of the narrative gradually improves throughout the rest of the book. An example of this is the third chapter, which addresses basic file access and exception handling. The following chapter, which focuses on data persistence, extends the discussion of how to save in-memory data in files, including the use of the standard library "pickle" for dumping and later loading any type of data. The next few chapters introduce the reader to increasingly complex ways of representing data, in the form of lists (again), dictionaries, and (object-oriented) classes. The discussion is fairly clear, except readers familiar with other object-oriented languages may be confused on page 194, where class attributes are being defined in the constructor only. In fact, the author does not fully explain where attributes can be defined, and what their resultant scope would be.

The seventh chapter roughly marks the halfway point in the book, and also is where the focus shifts from developing Python programs to releasing them to the public. The author begins by incorporating techniques presented earlier in the book, to build a Python-based web app, using the popular Model-View-Controller (MVC) paradigm. The next chapter shows how to port those web apps to mobile devices. Chapter 9 extends these topics, by demonstrating how to query for and accept user data in HTML forms on web pages, and in similar dialogs on Android phones — as well as how to store that data in an SQLite database. The next logical step is to learn how to make Python apps scalable, as well as cloud-based, in this case using the Google App Engine (GAE). Readers are also introduced to Django, for form validation. The final chapter, and the appendix, cover a number of miscellaneous topics, such as how to spreadsheet-type data storage, development IDEs, variable scope, unit testing, and regular expressions.

Most readers should find that the relaxed writing style makes this book approachable, though fairly lengthy. Like most if not all of the other books in the Head First lineup, this one is made more palatable with a sense of humor that is not silly — a welcome improvement to any programming book. The best parts are in the "fireside chats," which are fictional and sometimes pointed conversations, oftentimes between two similar components of Python.

Yet the narrative is far from perfect. Some of the phrasing is ponderous, e.g., "Perform the edits to your code" (page 113); why not just "Edit your code?" A few concepts are used without explanation, e.g., the Python value of "None" (page 80). Some technical slang terms are used quite early in the book, yet with no definitions or explanations for the neophyte — e.g. "app" and "webapp" (both on page xvi). Admittedly, most readers of this book will be programmers or other techies, who feel comfortable with those terms. But the Head First series is intended for people just getting started, and thus all such terms should be explained up front, if only briefly.

There are numerous errata not found in the aforesaid list (on the O'Reilly Media website): "tools to for accepting" (page xviii), "design user-friendly websites" (xxvii; should be "learn Python"), "try and" (14, 84 twice, and 188; should be "try to"), "As your plan to" (37; "you plan" was likely intended), "utilities" (49), "users that" (50; should be "users who"), "argument" (52), "a iterable" (53 and 54), "the the list on screen" (64), "the your latest version" (65), "a argument" (71), "gives you with a chance" (88), "file's contents" (123; incorrect plural possessive), "the facilities pickle" (134; probably should be "the pickle facilities"), "your were" (170), "it's new mode" (185; no apostrophe in "its"), and at this point I ceased recording errata. These flaws, plus the 119 already reported, suggest that the author and O'Reilly copy editors did not perform enough quality control when working on the manuscript.

One glaring problem with the material is the dramatic unevenness in the depths of coverage, from one topic to the next. For instance, even though the book is aimed at readers who already know another programming language (page xxiv), an entire section is devoted to establishing the (obvious) non-scalability of having to use an individual print() statement for every item in a list, and the superiority of instead iterating through the list (page 15). Yet in the same chapter, only a couple pages (29-30) are provided to explain functions, with no discussion of topics important to any programmer, such as whether one can set parameters to default values, or how to pass arguments by reference, if it's even possible. Some of this unevenness is due to the book's goal of presenting technical information in an easily-digestible form; for instance, in Chapter 7, the reader is told how a web server returns a web page, but later faces the minefield of invoking Python's built-in web server on a CGI server.

A second significant problem is the often-illogical ordering of material — both high level and low. Chapter 2 illustrates both cases: The author recommends that the reader release her code to the public (in the form of modules) after presumably having learned only one chapter's worth of material, when such code would undoubtedly be unready for public consumption. At a much lower level, the first "There Are No Dumb Questions" entry in the chapter briefly discusses various editors that could be used for writing Python code. This information should have been presented at the beginning of the first chapter, or even in the introduction — not after the reader has already chosen whatever editor seemed most convenient at the moment, and probably saved at least one file of code. A third variation of this problem, is when the reader is tested on concepts not previously presented — such as the "Who Does What?" section on page 53, which quizzes the reader on half a dozen functions, none of which the reader has presumably even seen before, and some of which are never mentioned again in the book!

In terms of the typography of the print version of the book, I found the font face and size to be problematic, especially on those pages where the text appears to have been printed a bit too lightly — at least in the review copy of the book kindly provided to me by the publisher. For instance, all of the code on page 227 is practically unreadable. Throughout the book, in the snippets of code, the comments are a light gray making them quite difficult to read — probably because these are screenshots of IDLE sessions, in which comments are by default displayed in green, which apparently does not translate well to grayscale illustrations.

Overall, this book appears to have received less oversight and editing than is typical in the Head First series. If you are a veteran programmer searching for a concise treatment of Python, then this book is not optimal for you. Yet if you seek an engaging and highly visual introduction to an elegant programming language, then Head First Python can be a worthwhile place to start your journey.

Michael J. Ross is a freelance web developer and writer.

You can purchase Head First Python from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

OverTheGeicoE writes "Former TSA Administrator Kip Hawley has been in the news in recent months, talking about how the Transportation Security Administration is broken and how it can be fixed. Some of his TSA criticisms in the popular press seem to make sense. This seemed strange to me. Just last March he was defending TSA in a debate with Bruce Schneier in The Economist. Then, the very next month, he's criticizing his former agency as if he was on the other side of that debate to begin with. Why? I felt like I was missing something, so I decided to read his book to find out more about his position. The title of the book is Permanent Emergency: Inside the TSA and the Fight for the Future of American Security, and it is co-written by Nathan Means." Keep reading for the rest of OverTheGeicoE's review. Permanent Emergency: Inside the TSA and the Fight for the Future of American Security author Kip Hawley and Nathan Means pages 260 publisher Palgrave Macmillan rating 6 reviewer OverTheGeicoE ISBN 978-0-230-12095-2 summary An inside look at TSA from its former leader. The book is partly a memoir of Hawley's involvement with TSA, which predates his appointment as its administrator. Hawley helped architect the TSA shortly after it was first authorized. He left government service once that was finished, but came back again in 2005, appointed by President George W. Bush to become TSA's third administrator in four years. He stuck with the job until the exact moment Barack Obama was sworn in as President in January of 2009. If you're looking for insight into TSA's most controversial policies, the extensive use of body scanning and pat down searches, you won't find that in this book. Those policies were put in place by Hawley's successor almost two years later. The phrase 'body scan' is used exactly once.

The book breaks from the memoir style at times and changes to that of an action-suspense thriller. It is interwoven with segments of prose similar to a Tom Clancy novel. In these segments we learn about the life, and possibly the ultimate death, of an Al Qaeda operative who goes by multiple names throughout the course of the book. Raised in Austria, we follow the terrorist through training with Al Qaeda in Pakistan and his connection with various airline-related terrorist plots against the United States. Under Administrator Hawley, TSA uses all its intelligence resources to track his moves and act to thwart the terrorist's nefarious schemes.

The Clancyesque sections are a severe weakness of the book, bordering on laughable at times. For example, there's a description of a Casio watch that reminded me of a Dave Barry parody of Tom Clancy. The action-suspense writing style also tends to over-dramatize and exaggerate TSA's actual accomplishments. The intelligence sources TSA uses all belong to conventional intelligence agencies, both US and foreign. The event leading to the most dramatic moments of the book, the disruption of a liquid bomb plot, was the work of British intelligence and law enforcement in the UK. The authors describe in great, suspenseful detail that while the British are rounding up actual Al Qaeda cell members, TSA in the US is waging war against an entire phase of matter, one that covers about 70% of Earth's surface. Thanks to their determined efforts, TSA was able to ban liquids from carry on luggage literally overnight. However, in this and all other terrorist plots covered in this book, the authors never offer any evidence that TSA's use of its borrowed intelligence ever allowed TSA to disrupt any specific, credible, and imminent threat. So, if you like the idea of a Tom Clancy book where the Jack Ryan character agonizes over intel a lot but never actually does anything of provable value with it, this may be the book for you.

Although the writing style was problematic at times, it didn't totally undermine the value of the book. It helped me understand why mainstream media is so accepting of TSA. During Hawley's tenure, TSA made strong, successful efforts to woo the press, including interviews with CBS' 60 Minutes and appearances on Oprah. The good relationship established during Hawley's administration apparently continues to this day, despite the dramatic changes in operations imposed by his successor. The book also gives an amusing mini-bio of TSA's 'Blogger Bob' Burns, who has been called 'the Tokyo Rose of the modern age' for his defenses of TSA under John Pistole.

I've often wondered why TSA seems so unresponsive to the American public, and this book offered me a plausible explanation. Hawley seems to view TSA almost exclusively as a weapon in the US war against Al Qaeda. When TSA implements policies that seem crazy or ineffective to the rest of us, it doesn't use outside opinions to judge the effectiveness of its policies. Instead it uses information gathered from the intelligence community unavailable to outsiders. A policy change is considered effective if Al Qaeda reacts in a desirable way. For example, if a TSA operation deploys VIPR teams at public transportation centers and suspected Al Qaeda operatives leave the US afterwards, the operation is considered successful.

This book also helped me better understand Hawley's recent press comments. It sounds as if Hawley is saying that TSA's most controversial policies can be terminated if intelligence shows Al Qaeda to be on the decline. Now that he is outside TSA, Hawley seems to see what the American public does, and sees a reason to change security. If intelligence shows an increase of Al Qaeda activity, security can be raised again as needed.

This understanding of how TSA works is also confusing. What we're actually seeing from TSA is an expansion of their activities in recent years, with no meaningful or significant easing of its invasive passenger screening being proposed. Could that mean Al Qaeda is actually on the rise in some way not obvious to the general public? If not, Hawley's successor is a real bungler, and I would expect Hawley to call him that when given a chance. Instead, Hawley specifically refuses to second guess his successor at the end of his book, leaving me puzzled about how the US war against Al Qaeda is actually going.

Permanent Emergency is an interesting book. It certainly has flaws. The writing style is inconsistent and often unsatisfying. It is not entirely factually correct in many of its stories; TSA classifies a lot of information, and the authors admit to changing or concealing details for that and other reasons. The book does not attempt to tackle the most controversial aspects of today's TSA policies. Still, the book gives insight into how TSA was formed, what problems it was designed to address, and how it operates. TSA is so new, there are few sources of this type to examine right now, so any firsthand account is useful. I recommend this book to anyone concerned by TSA's operations, as it helps us understand how TSA became what it is now.

You can purchase Permanent Emergency: Inside the TSA and the Fight for the Future of American Security from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

benrothke writes "In Digital Vertigo: How Todays Online Social Revolution Is Dividing, Diminishing, and Disorienting Us, author Andrew Keen, who describes himself as the Anti-Christ of Silicon Valley (whatever that means), raises numerous profound questions about social media and its implications on society. In the new world of social media and Web 3.0, which is claiming to revolutionize communication and interactions, Keen writes that history is repeating itself and points to the beginning of the industrial revolution as an example. He writes of Jeremy Bentham who invented the Panopticon; a structure where the inhabitants were watched at all times. Bentham felt the Panopticon could make humanity more virtuous, more hard-working and happier; similar to the promise of Web 3.0. The Panopticon was a failure, and Keen sees the same for Web 3.0. The book is a critique of Web 3.0." Read below for the rest of Ben's review. Digital Vertigo: How Today's Online Social Revolution Is Dividing, Diminishing, and Disorienting Us author Andrew Keen pages 256 publisher St. Martin's Press rating 8/10 reviewer Ben Rothke ISBN 0312624980 summary Critique of Web 3.0 While definitions of Web 3.0 vary greatly; Keen focuses on the personalization aspect. His view is that the current Internet culture and the wave of Web 3.0 social software is debasing society.

In this well-researched book, Keen presents two theses: that Web 3.0 is turning into an Orwellian infrastructure and that the hype of the Web 3.0 prognosticators is all hype. For the first point, it is a false premise, while the later has significant merit.

Keen has a misinterpretation of Big Brother and 1984. The book has scores of references to George Orwell, Big Brother, 1984 and related themes. Orwell describes Big Brother as the dictator of a totalitarian state, where the ruling party wields total power over the inhabitants.

In the society that Orwell describes, everyone is under complete surveillance by the authorities. Since the publication of 1984, the term has been synonymous for abuse of government power, particularly in respect to civil liberties, often specifically related to mass surveillance.

It is hard, if not impossible to see how Facebook and other social media services, which are voluntary and operate on an opt-in model, are anything close to totalitarianism and forced surveillance. The notion that Facebook is absolutism flies in the face of its tens of thousands of groups and topics, often in conflict with each other. Ironically, Keen never mentions the fact that Facebook founder Mark Zuckerberg was born in 1984.

One of the inherent problems with Facebook is that even if a person likes something, it is unclear if they bought the item, truly like it, or simply liked it to enter a raffle or help a friend. That is one of the reasons why General Motors Co. recently announced plans to stop advertising with Facebook. They found that that paid Facebook ads have little impact on consumers car purchases.

And therein is the rub; while all of that information is somewhat nebulous within the databases of Facebook, there is another organization, where substantial amounts of a person's most personal data is stored. That is an organization Keen seems oblivious to. That company is Experian, the largest of the big 3 credit firms.

While someone may like the New York Times on Facebook, Experian knows if the person has a subscription to the Times, what type of subscription they purchased, how long they have been a subscriber and how they paid for it. That is but one small example of the myriad data Experian has. Experian is not a social media company, they are not part of the Web 3.0 social revolution, yet they are significantly more dangerous than Facebook, Twitter and LinkedIn combined; a fact the book never discusses.

While Keen is critical of the social media wonks that the future will be social, he assumes that their prognostications of a social future are completely accurate. But as Facebook's growth has slowed and the fruits of its IPO stalled, there are many people who are simply tiring of social media.

In the introduction, Keen astutely quotes British philosopher John Stuart Mill that privacy is not only essential to life and liberty it's essential to the pursuit of happiness, in the broader and deepest sense. Keen sees social media in direct contradiction to that notion of privacy.

He closes the chapter with the observation estimating that in 2020; about 50 billion intelligent networked devices such as his BlackBerry Bold will be in use, many of which will be gathering personal data. Note though that at the recent 14th Annual AT&T Cyber Security Conference, one of the speakers put that number closer to 500 billion.

In chapter 1, Keen quotes Julian Assange that Facebook is that world's most comprehensive database about people, their relationships, names, address, locations, and more. Keen accepts that observation as gospel, uses it as an underpinning in the book, oblivious to Experian, which is interminably more comprehensive and authoritative than Facebook will ever be.

Case in point, many people put their birthday on Facebook as January 1, as it is a required field. While that Facebook data is utter rubbish, Experian has the person's true DOB.

Chapter 1 closes with numerous social media services being termed Orwellian services. It is hard to understand how an opt-in system is Orwellian. The chapter then closes with the histrionic question of "has Nineteen Eighty-Four finally arrived on all of our screens".

The histrionics continue with Orwell and its derivatives being used nearly 10 times on the first page of chapter 2. With that, Keen does note the importance of privacy and how it is being significantly eroded in social media. He quotes social media research scientist Dr. Julie Albright that privacy is taking a back seat to the notion that our every thought, act or desire should be publicized.

There are interesting insights in chapter 2 where he writes that social media has enabled new kinds of collective stupidity, and that it makes it hard for people to think for themselves; rather they simply cite what has already been cited.

He also notes that social media makes it effortless to destroy a life of integrity and a person's reputation. He notes that in our hypervisible age, all it takes is a camcorder and a Skype account to destroy someone's life; using the Dharun Ravi case as an example.

A point Keen perceptively makes is that there is little evidence that with all the sharing in social media, that it actually makes people more forgiving or tolerant. Rather it fuels a mob culture of intolerance, Schadenfreude and revengefulness. He writes that the tolerance that Jeff Jarvis thought Web 3.0 would bring, are in fact fueling the corrosive belligerence that has infected much of the snarky, gotcha public discourse in contemporary society.

Keen writes in depth about Mark Zuckerberg's notion of frictionless sharing and is concerned about its privacy consequences. Yet Zuckerberg's grand plan will only work if everyone opts in, which is still quite speculative.

In chapter 8, much of Keen's fears are allayed when he writes that the truth is that most of us don't want to share everything we read, watch and listen to online. In June 2012, noted security guru Marcus Ranum announced that he was deleting his Facebook account due to the inanity of the posts and invitations.

Keen himself said that he stopped using Facebook as he was embarrassed by some of the things people put up so he decided to close his account; calling it one of the best things he'd ever done online. With that, frictionless sharing goes nowhere.

Chapter 5 — The Cult of the Social, presents some of the most perceptive thoughts in the book. Keen quotes historian John Tresch that today's social media systems encourages people to manage their fame machine, with the goal to build followers and establish their own cloud of glory;but gaining nothing in the long-term.

The book closes with John Stuart Mill's notion that remaining human requires us to sometimes disconnect from society, to remain private, autonomous and secret. The alternate Mill recognized was the tyranny of the majority and the death of individual liberty; which Keen notes is not an unrealistic fear.

Another observation of Mill's that our uniqueness as a species lies in our ability to stand apart from the crowd, to disentangle ourselves from society, to be let alone and to be able to think and act for ourselves. For the proponents of Web 3.0, they see our uniqueness as a species as being social; for Keen, it is the antithesis.

In the book, Keen advocates that we need to ensure the balance between our public and private lives and is rightfully scared of those that say we are heading into a world that will no longer have privacy. Mills notion of the fundamentals of privacy mean that if we abandon it, we lose some of our essence as human beings.

Keen lets the reader know that he is not a Luddite and doesn't advocate completely abandoning social media. As a Twitter devotee, he has found the time to write over 10,000 tweets and amass nearly 20,000 followers.

Overall, Digital Vertigo: How Today's Online Social Revolution Is Dividing, Diminishing, and Disorienting Us is a book well worth reading. Keen raises countless fundamental questions of the underlying hazards of Web 3.0. He writes of our often blind infatuation with this new thing called Web 3.0 in which people are reveling far too much of their inner self, just for the use of a free service.

Ben Rothke is the author of Computer Security: 20 Things Every Employee Should Know.

You can purchase Digital Vertigo: How Today's Online Social Revolution Is Dividing, Diminishing, and Disorienting Us from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

benrothke writes "In Digital Vertigo: How Todays Online Social Revolution Is Dividing, Diminishing, and Disorienting Us, author Andrew Keen, who describes himself as the Anti-Christ of Silicon Valley (whatever that means), raises numerous profound questions about social media and its implications on society. In the new world of social media and Web 3.0, which is claiming to revolutionize communication and interactions, Keen writes that history is repeating itself and points to the beginning of the industrial revolution as an example. He writes of Jeremy Bentham who invented the Panopticon; a structure where the inhabitants were watched at all times. Bentham felt the Panopticon could make humanity more virtuous, more hard-working and happier; similar to the promise of Web 3.0. The Panopticon was a failure, and Keen sees the same for Web 3.0. The book is a critique of Web 3.0." Read below for the rest of Ben's review. Digital Vertigo: How Today's Online Social Revolution Is Dividing, Diminishing, and Disorienting Us author Andrew Keen pages 256 publisher St. Martin's Press rating 8/10 reviewer Ben Rothke ISBN 0312624980 summary Critique of Web 3.0 While definitions of Web 3.0 vary greatly; Keen focuses on the personalization aspect. His view is that the current Internet culture and the wave of Web 3.0 social software is debasing society.

In this well-researched book, Keen presents two theses: that Web 3.0 is turning into an Orwellian infrastructure and that the hype of the Web 3.0 prognosticators is all hype. For the first point, it is a false premise, while the later has significant merit.

Keen has a misinterpretation of Big Brother and 1984. The book has scores of references to George Orwell, Big Brother, 1984 and related themes. Orwell describes Big Brother as the dictator of a totalitarian state, where the ruling party wields total power over the inhabitants.

In the society that Orwell describes, everyone is under complete surveillance by the authorities. Since the publication of 1984, the term has been synonymous for abuse of government power, particularly in respect to civil liberties, often specifically related to mass surveillance.

It is hard, if not impossible to see how Facebook and other social media services, which are voluntary and operate on an opt-in model, are anything close to totalitarianism and forced surveillance. The notion that Facebook is absolutism flies in the face of its tens of thousands of groups and topics, often in conflict with each other. Ironically, Keen never mentions the fact that Facebook founder Mark Zuckerberg was born in 1984.

One of the inherent problems with Facebook is that even if a person likes something, it is unclear if they bought the item, truly like it, or simply liked it to enter a raffle or help a friend. That is one of the reasons why General Motors Co. recently announced plans to stop advertising with Facebook. They found that that paid Facebook ads have little impact on consumers car purchases.

And therein is the rub; while all of that information is somewhat nebulous within the databases of Facebook, there is another organization, where substantial amounts of a person's most personal data is stored. That is an organization Keen seems oblivious to. That company is Experian, the largest of the big 3 credit firms.

While someone may like the New York Times on Facebook, Experian knows if the person has a subscription to the Times, what type of subscription they purchased, how long they have been a subscriber and how they paid for it. That is but one small example of the myriad data Experian has. Experian is not a social media company, they are not part of the Web 3.0 social revolution, yet they are significantly more dangerous than Facebook, Twitter and LinkedIn combined; a fact the book never discusses.

While Keen is critical of the social media wonks that the future will be social, he assumes that their prognostications of a social future are completely accurate. But as Facebook's growth has slowed and the fruits of its IPO stalled, there are many people who are simply tiring of social media.

In the introduction, Keen astutely quotes British philosopher John Stuart Mill that privacy is not only essential to life and liberty it's essential to the pursuit of happiness, in the broader and deepest sense. Keen sees social media in direct contradiction to that notion of privacy.

He closes the chapter with the observation estimating that in 2020; about 50 billion intelligent networked devices such as his BlackBerry Bold will be in use, many of which will be gathering personal data. Note though that at the recent 14th Annual AT&T Cyber Security Conference, one of the speakers put that number closer to 500 billion.

In chapter 1, Keen quotes Julian Assange that Facebook is that world's most comprehensive database about people, their relationships, names, address, locations, and more. Keen accepts that observation as gospel, uses it as an underpinning in the book, oblivious to Experian, which is interminably more comprehensive and authoritative than Facebook will ever be.

Case in point, many people put their birthday on Facebook as January 1, as it is a required field. While that Facebook data is utter rubbish, Experian has the person's true DOB.

Chapter 1 closes with numerous social media services being termed Orwellian services. It is hard to understand how an opt-in system is Orwellian. The chapter then closes with the histrionic question of "has Nineteen Eighty-Four finally arrived on all of our screens".

The histrionics continue with Orwell and its derivatives being used nearly 10 times on the first page of chapter 2. With that, Keen does note the importance of privacy and how it is being significantly eroded in social media. He quotes social media research scientist Dr. Julie Albright that privacy is taking a back seat to the notion that our every thought, act or desire should be publicized.

There are interesting insights in chapter 2 where he writes that social media has enabled new kinds of collective stupidity, and that it makes it hard for people to think for themselves; rather they simply cite what has already been cited.

He also notes that social media makes it effortless to destroy a life of integrity and a person's reputation. He notes that in our hypervisible age, all it takes is a camcorder and a Skype account to destroy someone's life; using the Dharun Ravi case as an example.

A point Keen perceptively makes is that there is little evidence that with all the sharing in social media, that it actually makes people more forgiving or tolerant. Rather it fuels a mob culture of intolerance, Schadenfreude and revengefulness. He writes that the tolerance that Jeff Jarvis thought Web 3.0 would bring, are in fact fueling the corrosive belligerence that has infected much of the snarky, gotcha public discourse in contemporary society.

Keen writes in depth about Mark Zuckerberg's notion of frictionless sharing and is concerned about its privacy consequences. Yet Zuckerberg's grand plan will only work if everyone opts in, which is still quite speculative.

In chapter 8, much of Keen's fears are allayed when he writes that the truth is that most of us don't want to share everything we read, watch and listen to online. In June 2012, noted security guru Marcus Ranum announced that he was deleting his Facebook account due to the inanity of the posts and invitations.

Keen himself said that he stopped using Facebook as he was embarrassed by some of the things people put up so he decided to close his account; calling it one of the best things he'd ever done online. With that, frictionless sharing goes nowhere.

Chapter 5 — The Cult of the Social, presents some of the most perceptive thoughts in the book. Keen quotes historian John Tresch that today's social media systems encourages people to manage their fame machine, with the goal to build followers and establish their own cloud of glory;but gaining nothing in the long-term.

The book closes with John Stuart Mill's notion that remaining human requires us to sometimes disconnect from society, to remain private, autonomous and secret. The alternate Mill recognized was the tyranny of the majority and the death of individual liberty; which Keen notes is not an unrealistic fear.

Another observation of Mill's that our uniqueness as a species lies in our ability to stand apart from the crowd, to disentangle ourselves from society, to be let alone and to be able to think and act for ourselves. For the proponents of Web 3.0, they see our uniqueness as a species as being social; for Keen, it is the antithesis.

In the book, Keen advocates that we need to ensure the balance between our public and private lives and is rightfully scared of those that say we are heading into a world that will no longer have privacy. Mills notion of the fundamentals of privacy mean that if we abandon it, we lose some of our essence as human beings.

Keen lets the reader know that he is not a Luddite and doesn't advocate completely abandoning social media. As a Twitter devotee, he has found the time to write over 10,000 tweets and amass nearly 20,000 followers.

Overall, Digital Vertigo: How Today's Online Social Revolution Is Dividing, Diminishing, and Disorienting Us is a book well worth reading. Keen raises countless fundamental questions of the underlying hazards of Web 3.0. He writes of our often blind infatuation with this new thing called Web 3.0 in which people are reveling far too much of their inner self, just for the use of a free service.

Ben Rothke is the author of Computer Security: 20 Things Every Employee Should Know.

You can purchase Digital Vertigo: How Today's Online Social Revolution Is Dividing, Diminishing, and Disorienting Us from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

MassDosage writes "Having developed software for nearly fifteen years, I remember the dark days before testing was all the rage and the large number of bugs that had to be arduously found and fixed manually. The next step was nervously releasing the code without the safety net of a test bed and having no idea if one had introduced regressions or new bugs. When I first came across unit testing I ardently embraced it and am a huge fan of testing of various forms — from automated to smoke tests to performance and load tests to end user and exploratory testing. So it was with much enthusiasm that I picked up How Google Tests Software — written by some of the big names in testing at Google. I was hoping it would give me fresh insights into testing software at "Google Scale" as promised on the back cover, hopefully coupled with some innovative new techniques and tips. While partially succeeding on these fronts, the book as a whole didn't quite live up to my expectations and feels like a missed opportunity." Read below for the rest of MassDosage's review. How Google Tests Software author James Whittaker, Jason Arbon, Jeff Carollo pages 281 publisher Addison Wesley rating 6/10 reviewer Mass Dosage ISBN 978-0321803023 summary Testing at Google scale The book is written in an informal, easy to read manner and organized in such a way that readers can read chapters in any order or just choose to focus on the parts that interest them. One annoying layout choice is to highlight and repeat certain key sentences (as is often done in magazines) resulting in one reading the same thing twice, often only words away from the original sentence. Thankfully this is only the case in the first two chapters, but it highlights the variable quality of this book — possibly due to the authors having worked separately on different chapters. How Google Tests Software isn't a book for people new to testing or software development. The authors assume you know a fair amount about the software development lifecycle, where testing fits into this and what different forms testing can take. It is also largely technology neutral, using specific examples of testing software that Google uses only to illustrate concepts.

After a brief introduction as to how testing has evolved over time at Google the book devotes a chapter to each of the key testing-related roles in the company: the 'Software Engineer in Test' (SET), the 'Test Engineer' (TE) and the 'Test Engineering Manager' (TEM). SETs are coders who focus on writing tests or frameworks and infrastructure to support other coders in their testing. The TE has a broader, less well-defined role and is tasked with looking at the bigger picture of the product in question and its impact on users and how it fits into the broader software ecosystem. These two sections form the bulk of the book in terms of pages and interesting content. The TEM is essentially what the name says — someone who manages testers and testing and coordinates these activities at a higher level within Google.

The descriptions of each of these testing roles highlights the ways Google's thinking about testing has matured and also shows how some of these approaches differ from other companies. There are also explanations of the tools and processes that people in these roles use and follow and this for me was the most interesting part of the book. Topics covered include: specific bug tracking and test plan creation tools; risk analysis; test case management over time; and automated testing. Particularly of note are discussions on using bots to perform testing of web pages to detect differences between software releases, cutting down on the amount of human interaction required as well as the opposite approach — using more humans via "crowd sourced testing" among first internal and then select groups of external users. The tools that Google utilizes to simplify tester's jobs by recording steps to reproduce bugs and simplifying bug reporting and management sound very useful. Many of the tools described in the book are open source (or soon to be opened) and are probably worth following up on and investigating if this is what you do for a living.

In addition to the main body of text most chapters also include interviews with Google staff on various testing related topics. Some of these are genuinely interesting and give the reader a good idea of how testing is tackled at Google on a practical level. However some of the interviews fall into the "navel gazing" camp (especially when the authors interview one of themselves) and feel more like filler material. I enjoyed the interviews with Google hiring staff the most — their take on how they recruit people for testing roles and the types of questions they ask and qualities they look for make a lot of sense. The interview with the GMail TEM was also good and illustrated how the concepts described in the book are actually performed in practise. The interviews are clearly marked and can thus be easily skipped or skim read but one wonders what more useful text could have been included in their place.

The book wraps up with a chapter that attempts to describe how Google intends to improve their testing in the future. The most valuable point here is how testing as a separate function could "disappear" as it becomes part and parcel of the product being developed like any other feature, and thus the responsibility of all of the people working on the product as opposed to it being a separate thing. Another key point made throughout the book is how the state of testing at Google is constantly in flux which makes sense in such a fast moving and innovative company but leaves one questioning how much of this book will still be relevant in a few year's time.

How Google Tests Software isn't a bad book but neither is it a great one. It has some good parts and will be worth reading for those who are interested in "all things Google." For everyone else I'd recommend skimming through to the parts that grab your attention most and glossing over the rest.

You can purchase How Google Tests Software from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

jkauzlar writes "Believe it or not, it's been 18 years since Design Patterns by Gamma, et al, first began to hit the desks of programmers world-wide. This was a work of undeniable influence and usefulness, but there is criticism however that pattern-abuse has lead to over-architected software. This failure is perhaps due to wide-spread use of patterns as templates instead of understanding their underlying 'grammar' of this language such that it may be applied gracefully to the problem at hand. What's been missing until now is a sufficiently authoritative study of design patterns at this 'grammatical' level of abstraction. Jason McC. Smith, through a surprisingly captivating series of analytic twists and turns, has developed a theory of Elemental Design Patterns that may yet rejuvenate this aging topic." Keep reading for the rest of Joe's review. Elemental Design Patterns author Jason McC. Smith pages 368 publisher Addison-Wesley Professional rating 9/10 reviewer Joe Kauzlarich ISBN 978-0321711922 summary Software Design Much as developing a large taxonomy of star-types in astronomy lead to and enabled theories of star formation, or a classification of organic life lead to studies of genetics, it makes sense that the large volumes of collected object-oriented design patterns should somehow lead to a generic understanding of them. Smith actually approached this in an attempt to solve a very practical problem: given the variety of ways a particular pattern can be implemented, how can one be recognized programmatically with a degree of certainty?

What's most fascinating about Elemental Design Patterns is the analysis performed in working out a solution to the question of how a pattern may be defined in a way that's language-agnostic and flexible to differing implementations. This was a success: his resulting pattern recognition tool even found unintentional usages of well-known design patterns in a large legacy code base, which could then be refactored from the ugly 'accidental usage' to transform apparent chaos into maintainable order.

The basic idea is that every pattern is composed of elemental patterns. For example, the 'Factory Method' pattern may be decomposed into four EDPs (elemental design patterns): 'Create Object', 'Fulfill Method', 'Conglomeration' and 'Retrieve'. The 'Pattern Instance Notation', introduced in this book, and which serves as an extension to UML, helps visualize the relationships between the four sub-patterns and the larger pattern. No doubt readers will find the notation useful in their own work.

This premise's success or failure hinges on two questions: are the set of patterns really elemental? and can the set of patterns be complete? Oddly, the patterns listed in the book are NOT complete: "this book touches on only one-quarter, at best, of the possible EDPs that exist" (p. 107). The fact that this book (which defines 16 patterns in depth) is only the beginning of a project is not well-communicated. Those who might benefit from a complete listing of EDPs (i.e. analysis tool makers) might be puzzled at how to immediately put this book to use if it's not complete. After all, Smith insists in the Preface that "this book is meant to be used." To me, this implies it should serve as more than a basis for research or design-skills edification.

As for them being elemental, in the sense that all possible 'macro-patterns' may be built from them, Smith backs up this claim with the help of a mathematical formal system called rho-calculus, which is introduced in some depth in the appendix, but avoided in the body of the text for readability's sake. Readers wanting a full mathematical treatment are referred to Smith's Ph.D thesis.

What makes the book worth reading and re-reading is in the methods employed to analytically derive EDPs. As dull as I probably make it sound, Smith gives the entertaining first half of the book an almost 'novelistic', first-person quality in which the reader is engaged to experience Smith's insights first-hand. In a sense, the EDPs are 'unfolded' from simple concepts like the degrees of method or object similarity in a method-call relationship.

Understanding this point is important to understanding EDPs: a method call is not just a method call from a 'micro-patterns' perspective. Calling a very different method on the same object is semantically distinct from calling a very similar method on a very different object. The first is described by the EDP 'Conglomeration' (breaking larger tasks into subtasks); the second, by the EDP 'Redirection' (redirecting a process to another object). Of course, the terms 'similar' and 'different' are fuzzy qualifiers to programmers and there's bound to be some debate on how these terms are applied. Smith, in order to make this distinction, puts faith in the developer's ability to name classes and methods. But anyway, such 'semantic' relationships are the real building-blocks of the higher-level patterns. Once other object-oriented principles are considered, like inheritance, the EDP list grows.

The importance of Elemental Design Patterns from a designer's perspective should now be more clear. I kept stressing the word 'semantic' in the last paragraph because what this book strives to do is provide a *language* for describing object-oriented structure that, first of all, doesn't rely on the OO language itself (C++, Smalltalk, Java, Javascript, etc), and more notably, which takes into account the designer's purpose for employing simple devices like method calls and class extension. As I said earlier, a method call is not just a method call. There may be a dozen or so 'structural' reasons to call a method, and each reason is given it's own 'word' (i.e. EDP) in Smith's language. It stands to reason that a designer with a firmer grasp on his own intentions is a more effective designer.

You can purchase Elemental Design Patterns from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

theodp writes "Q. What do you get when you surround the image of Men in Black star Will Smith trying on sunglasses with a pitch for 'MIB Bill Smith Dark Shades'? A. U.S. Patent No. 8,180,688. 'Many people consume broadcast media such as television shows and movies for many hours a week,' Amazon explained to the USPTO in its patent application for a Computer-Readable Medium, System, and Method for Item Recommendations Based on Media Consumption. 'The consumed broadcast media may depict a variety of items during the course of the transmission, such as clothing, books, movies, accessories, electronics, and/or any other type of item.' So, does Amazon's spin on As Seen on TV advertising deserve a patent?"

benrothke writes "Elementary Information Security, based on its title, weight and page length, I assumed was filled with mindless screen shots of elementary information security topics, written with a large font, in order to jack up the page count. Such an approach is typical of far too many security books. With that, if there ever was a misnomer of title, Elementary Information Security is it." Read below for the rest of Ben's review Elementary Information Security author Richard E. Smith pages 800 publisher Jones &amp;amp;amp;amp;amp;amp;amp;amp; Bartlett Learning rating 10/10 reviewer Ben Rothke ISBN 978-1449648206 summary Information security magnum opus For anyone looking for a comprehensive information security reference guide - Elementary Information Security is it. While the title may say elementary, for the reader who spends the time and effort to complete the book, they will come out with a complete overview of every significant information security topic.

The book is in fact a textbook meant to introduce the reader to the topic of information security. But it has enough content to be of value to everyone; security notices or experienced professional.

Author Richard Smith notes that if you want to get a solid understanding of information security technology, you have to look closely at the underlying strengths and weakness of information technology itself, which requires a background in computer architecture, operating systems and computing networking.

With that, Elementary Information Security is a tour de force that covers every information security topic, large and small. The book also provides a relevant overview of the peripheral topics that are embedded into information security.

In 17 chapters covering over 800 pages, the book is well organized and progressively gets more complex. Two large chapters of the book are freely available online, with chapter 3 here and chapter 9 here. The early chapters focus on the fundamentals of computers and networking, and the core aspects of information security. The chapters progress in complexity and deal with distributed systems and more complex security topics. The mid-chapters deal with cryptography, starting with an introduction to the topic, into more complex topics and scenarios. One is hard-pressed to find an information security topic not covered in the book.

Chapter 1 is on Security from the Ground Up and lays the groundwork for what security is. Various topics around risk are detailed; such as identifying, prioritizing and assessing risks.

Chapter 2 is on Controlling a Compute rand reviews the underlying architecture around computers.

For some people, much of their learning about information security is based on rote memorization. In the book, Smith eschews this and each chapter closes with a glossary of topics, and penetrating questions. There are also problem definitions which detail practical situations with the hope that the reader can create and adequate security solution. The reader who spends extra time reviewing the questions will find that it will significantly help in their mastering the myriad topics.

The goal of the questions and exercises is to make the knowledge real. Some of the exercises include watching movies with computer security related topics such as The Falcon and the Snowman, Crimson Tide, and others. For example, in The Falcon and the Snowman, the author asks the reader to identify two types of security measure that would have helped prevent theft of the crypto keys. In Crimson Tide, it asks the reader to consider the missile launch procedures portrayed in the film and asks if it is possible for a single person to launch a nuclear missile. Another scenario is that under what circumstances a recipient should accept an unauthenticated message. It also asks the reader to give an example of a circumstance in which accepting an unauthenticated message would yield the wrong result.

The book is not meant as a For Dummies guide to the topic, and it assumes a college-level comprehension of relevant mathematical concepts. Note though that the requisite math is detailed in the sections on encryption and cryptography.

The book is also the first textbook certified by the NSA to comply with the NSTISSI 4011 standard, which is the federal training standard for information security professionals. The author notes on his blog that in order to gain that certification, he had to map each topic required by the standard to the information as it appears in the textbook.

Given the value of the book, (ISC) should consider using this title as a reference for their CISSP certification. With all of the CISSP preparation guides available, even the Official (ISC)2 Guide to the CISSP CBK, one is hard pressed to find a comprehensive all-embracing security reference such as this. Some may even want to simply use this book as their definitive CISSP study guide.

For those looking for a single encyclopedic reference on information security, they should look no further than Elementary Information Security. Richard Smith has written a magnum opus on the topic, which will be of value for years to come.

Ben Rothke is the author of Computer Security: 20 Things Every Employee Should Know.

You can purchase Elementary Information Security from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

benrothke writes "Elementary Information Security, based on its title, weight and page length, I assumed was filled with mindless screen shots of elementary information security topics, written with a large font, in order to jack up the page count. Such an approach is typical of far too many security books. With that, if there ever was a misnomer of title, Elementary Information Security is it." Read below for the rest of Ben's review Elementary Information Security author Richard E. Smith pages 800 publisher Jones &amp;amp;amp;amp;amp;amp;amp;amp; Bartlett Learning rating 10/10 reviewer Ben Rothke ISBN 978-1449648206 summary Information security magnum opus For anyone looking for a comprehensive information security reference guide - Elementary Information Security is it. While the title may say elementary, for the reader who spends the time and effort to complete the book, they will come out with a complete overview of every significant information security topic.

The book is in fact a textbook meant to introduce the reader to the topic of information security. But it has enough content to be of value to everyone; security notices or experienced professional.

Author Richard Smith notes that if you want to get a solid understanding of information security technology, you have to look closely at the underlying strengths and weakness of information technology itself, which requires a background in computer architecture, operating systems and computing networking.

With that, Elementary Information Security is a tour de force that covers every information security topic, large and small. The book also provides a relevant overview of the peripheral topics that are embedded into information security.

In 17 chapters covering over 800 pages, the book is well organized and progressively gets more complex. Two large chapters of the book are freely available online, with chapter 3 here and chapter 9 here. The early chapters focus on the fundamentals of computers and networking, and the core aspects of information security. The chapters progress in complexity and deal with distributed systems and more complex security topics. The mid-chapters deal with cryptography, starting with an introduction to the topic, into more complex topics and scenarios. One is hard-pressed to find an information security topic not covered in the book.

Chapter 1 is on Security from the Ground Up and lays the groundwork for what security is. Various topics around risk are detailed; such as identifying, prioritizing and assessing risks.

Chapter 2 is on Controlling a Compute rand reviews the underlying architecture around computers.

For some people, much of their learning about information security is based on rote memorization. In the book, Smith eschews this and each chapter closes with a glossary of topics, and penetrating questions. There are also problem definitions which detail practical situations with the hope that the reader can create and adequate security solution. The reader who spends extra time reviewing the questions will find that it will significantly help in their mastering the myriad topics.

The goal of the questions and exercises is to make the knowledge real. Some of the exercises include watching movies with computer security related topics such as The Falcon and the Snowman, Crimson Tide, and others. For example, in The Falcon and the Snowman, the author asks the reader to identify two types of security measure that would have helped prevent theft of the crypto keys. In Crimson Tide, it asks the reader to consider the missile launch procedures portrayed in the film and asks if it is possible for a single person to launch a nuclear missile. Another scenario is that under what circumstances a recipient should accept an unauthenticated message. It also asks the reader to give an example of a circumstance in which accepting an unauthenticated message would yield the wrong result.

The book is not meant as a For Dummies guide to the topic, and it assumes a college-level comprehension of relevant mathematical concepts. Note though that the requisite math is detailed in the sections on encryption and cryptography.

The book is also the first textbook certified by the NSA to comply with the NSTISSI 4011 standard, which is the federal training standard for information security professionals. The author notes on his blog that in order to gain that certification, he had to map each topic required by the standard to the information as it appears in the textbook.

Given the value of the book, (ISC) should consider using this title as a reference for their CISSP certification. With all of the CISSP preparation guides available, even the Official (ISC)2 Guide to the CISSP CBK, one is hard pressed to find a comprehensive all-embracing security reference such as this. Some may even want to simply use this book as their definitive CISSP study guide.

For those looking for a single encyclopedic reference on information security, they should look no further than Elementary Information Security. Richard Smith has written a magnum opus on the topic, which will be of value for years to come.

Ben Rothke is the author of Computer Security: 20 Things Every Employee Should Know.

You can purchase Elementary Information Security from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

eldavojohn writes "The Logic of Chance: The Nature and Origin of Biological Evolution is a comprehensive snapshot of the latest research of biological evolution. The text is written by Eugene V. Koonin, an editor for a journal and researcher at NCBI. The book, although lacking in foundational knowledge and often foregoing explanation of research, presents a comprehensive and well-referenced view of modern evolutionary research. It is heavily laden with acronyms and jargon specific to biology and evolution. As a result, reading it requires either prior knowledge or a high tolerance for looking up these advanced topics with the reward of it being an extremely eye opening and enjoyable read worthy of your time." Keep reading for the rest of eldavojohn's review. The Logic of Chance: The Nature and Origin of Biological Evolution author Eugene V. Koonin pages 516 publisher FT Press Science rating 7/10 reviewer eldavojohn ISBN 978-0132542494 summary An outline of a fundamentally new evolutionary synthesis reflecting key advances in genomics, systems biology and biological physics. First off, my background is primarily in computer science although I took courses in bioinformatics in my undergrad and have maintained an interest in evolution since evolutionary and genetic algorithms were supposed to revolutionize computer science when I was in school. Unfortunately, my lack of biology caused the text to be extremely tedious (so much googling) for some chapters while my strong statistical background made other chapters very much enjoyable. For most readers this presents a large barrier of entry. When the author discusses neural networks being used to categorize prokaryotic genes, it may be insufficient to the reader to understand what that means. As a result, this book's audience is a relatively small set of people: 1) biology graduates with strong statistical knowledge or 2) someone willing to work very hard to understand advanced terms and concepts in both fields. Please proceed knowing that a biologist's review of this same book could very well sound entirely different from mine. Also, Koonin wastes very few words in this book, the text is dense and if you are unable to complete reading this review due to jargon there is a low chance you'll be able to tolerate it in the book. To sample some of this book, there is a short PDF containing chapter one or Google Books offering the first 147 pages at the time of this writing — you will see that this review barely scratches the surface of what is covered in this information-dense book.

Secondly, I will preface my review of the technical aspects of this book with my reason for giving it a score of 7 out of 10. The introduction to this book sets very lofty goals. One of them being the hope that this book does for evolution what A Brief History of Time did for physics. That is a seriously tall order and gave me correspondingly high hopes for this book. Koonin, unfortunately, is a very gifted writer and is unafraid of using exceedingly complex sentences such as this gem from page 117 (deliberately taken out of context):

"It has been known for years that a widespread form of global regulation in bacteria is mediated by cAMP, with the participation of diverse adenylate cyclases (a striking case of NOGD); numerous proteins containing cAMP sensors, such as the GAF domain; and the CRP, FNR, and other transcription regulators, also containing cAMP-binding domains."

That sentence is typical of Koonin's writing — lengthy and intricately peppered with many acronyms (only one of which had been described well enough for me earlier in the text). Of course, that paragraph comes with a reference to a paper (like almost all of the paragraphs in this book) from 2010 by Seshasayee so the reader is free to seek external resources if these sentences are daunting.

Considering all of this, I read A Brief History of Time in high school and, despite not having had a physics course yet, learned a lot from it. I attribute that, mostly, to the fact that the sentences are simple and straightforward. Not only that but A Brief History of Time did a great job of building upward from the foundational mechanics of physics while somehow remaining refreshingly brief. This is not the case in The Logic of Chance but I will rush to the book's defense somewhat on that charge. Prior to having read this book, I would have stated my desire that the text start from the basics and work its way up. After reading this book and understanding this field better than I ever have, I now agree that the subject matter of evolution would demand quite the epic tome to accomplish such a feat. I do hope to see future versions of this book with more concise and clear sentences as well as more fundamental concepts explained. If I could have begged Koonin to add one thing to this book, it would be a glossary in the back spanning many hundreds of pages for ignorant readers like myself. Right now this book is for graduate students and academia whereas A Brief History of Time could almost be consumed by anyone who made it through the public school system.

I also sympathize with Koonin's herculean task because modern evolutionary studies seem relatively young compared to other fields like particle physics. As a result, Koonin must (and does) concede in some sections that there still exists largely debated theories. These debates often concern things about which we may never know the absolute truth like the branching factor of a tree of evolution on Earth some indeterminable time ago. As more and more prokaryotes and eukaryotes are added to their statistical algorithms, this may become clearer and yield revelations like the genetic makeup of the last eukaryotic common ancestor (LECA) and free this text of many pages devoted to questions surrounding such origins of life. But for now Koonin must tediously cover all his bases to introduce such things to the reader.

The book starts off by establishing the fundamentals of evolution up until the consolidation of Modern Synthesis. This includes purifying selection, drift, draft, fitness landscapes, etc until Darwinian Evolution was combined with genetics. At this point, the substrate of evolution (the genome) lead to evolutionary genomics. In particular Koonin concentrates on the statistics applied at the molecular level including distance methods, maximum parsimony, maximum likelihood, Bayesian inference and a similar analysis of phylogenetic methods. Koonin establishes early on that evolutionary research can no longer rely merely on phenotypic effects but rather there is a vast array of concrete changes happening at a molecular level.

The book moves on into comparative genomics and discusses extensively the intricate differences between the genomes of viruses, bacteria, archaea and eukaryota. Koonin exhaustively compares these groups through statistics and lays a brief foundation of relationships between genes. From this point on the book is heavily infested with the terminology of homologous, orthologous and paralogous genes. In addition to those the author discusses In-/Out-paralogous, co-orthologous and groups of orthologous (COG) genes. For people unfamiliar with this world, bookmarking and referring to Box 3-1 on page 56 is strongly advised. For the layperson, I believe an expansion of such a graphic would be a great addition to this book. Inside this part, the book also covers a simple but often misunderstood core piece of evolution and that is that evolution has the basic elementary events at the level of gene and genome evolution: substitution, deletion/loss, insertion, recombination/HGT and duplication. Over and over on Slashdot, I see comments that indicate a confusion or perception of evolution being one big monolithic thing. Koonin obviously reads or even studies a lot of other academic fields and tries to explain "the gene universe" as a space-time where there are a few dense clusters of core genes represented in most genomes but most of that space-time is occupied by a huge number of increasingly sparse "nebulae" consisting of rare genes. The author says of this universe: "This organization of the gene universe is distinctly fractal--that is, it appears at all scales of evolutionary distances."

As if that wasn't enough to prove that a definitive phenome narrative (what I alluded to earlier as desired) would be a bad idea, the next section moves on to systems biology and a heavier statistical look at genomics. Beyond the gene status (present or not present) exist two classes of variables: intensive evolutionary variables and extensive phenomic variables. At this point, we're not even talking about tangible things like eye or hair color but rather the underlying mechanisms to those sorts of things like proteins and how they are folded. Everywhere Koonin uses italics, the reader should pay special attention as I found these to be the most interesting key points (example: "Highly expressed genes evolve slowly"). In defining the nature of the evolutionary process, the author covers important concepts like fitness graphs that contain multiple local maxima to demonstrate how non-optimal progressions can occur. Furthermore this section makes it clear that adaptation is not the be-all end-all of evolution. The extensive discussion of the quantifiable properties of genome architecture, functioning and evolution are defined more so by non-adaptive, stochastic processes. Here (and in many later sections) Koonin attempts to use metaphors like Jacob's tinkering and ratchets to help the reader understand these complex concepts but I felt that these metaphors were still so far abstracted that the text could use anything linking these processes to tangible observations in organisms. Again I cannot hold this as a flaw for, after reading the book, it's clear that such a request would be viewed as sophomoric and evidence that I am unable to progress past The Origin of the Species (this book's key objective).

Koonin then moves on to the prokaryotic world and examines their genes and operons while paying special attention to an odd case: cyanobacteria. Most importantly in the prokaryotic domain, extensive comparative genomics has revealed a concept called horizontal gene transfer (HGT). I was personally hoping that Koonin would seize upon this novel concept and its importance in bacterial antibiotic resistance and how bacteria can evolve to dissolve novel compounds. For better or for worse, Koonin sticks to the pure purpose of this book and extensively covers important HGT discoveries like the convergence of protein sequences in similar groups of bacteria and archaea. Some selfish genes rely so heavily on horizontal mobility that they are dubbed "mobilomes" and Koonin discusses their aspects extensively. Darwin's Tree of Life concept was a very small eukaryotic part of the big picture that Koonin tries to re-invent as the "Forest of Life" or "Web of Life" (considering HGT). A whole chapter is devoted to discussing its properties and graphically visualizing its structure based on extensive surveys and what we know today.

From there the author discusses the origins of eukaryotes, Last Eukaryotic Common Ancestor (LECA), the branching factor of its evolution, its relative distance to the point of symbiogenesis in proposed evolutionary trees and the many competing theories about that tree. This section of the book spends considerable time examining the inferred origins of basic eukaryotic cell functioning and also discusses at length the archaeal roots of elaborate systems with the exception of the mitochondrion. This chapter also looks at the perplexing features of introns in eukaryotic genes. Koonin then tackles the misconceptions and abuses of the word complexity in all aspects of evolution. He applies information theory to the genetic code and notes that "information (entropy) tells us very little about the meaningful information content or complexity of a genomic sequence." It is then suggested that a new way to compute entropy and complexity is to examine the alignment of orthologous sequences instead of single sequences. For people interested in information theory, chapter eight is the most fruitful where Koonin proposes a computable formula for biological (evolutionary) information density. Like Claude Shannon's ability to infer many important aspects of communication, Koonin's modifications allow us to calculate that perceptually complex organisms possess more "entropic" genomes while perceptually less complex organisms like bacteria have the tightly packed and information dense "informational" genomes. After establishing these studies in information theory, Koonin is able to argue that neutrality of mutations that are fixed during evolution is the null hypothesis for all molecular evolutionary theories. All of this aids the author in discussing why evolution progressed passed single celled organisms that already had 1,000 to 1,500 genes to larger sets of genes in multicelled organisms.

Chapter nine tackles the modalities of Darwinian, Larmarckian and Wrightean evolutionary theories. This chapter improves upon the simplistic triad of heredity-variance-selection that defines Modern Synthesis by showing that the relationship between population size and environmental stress determines which of the three modalities is expressed the most in evolution while at the same time observing the importance of entropy (noise) at all levels of transmission. Koonin shows that by combining very well known molecular mechanisms we can achieve a complex scenario like Jean-Bapteste Lamarck's proposed modality of evolution. The text gives viruses the same treatment which, despite my assumption that they would be easier to analyze, appear to have many of the same complexities that prokaryotes and eukaryotes have. Possibly even more so given the effects of the Red Queen Hypothesis and all of the counterdefense genomes in some viruses. Furthermore the cellular empire and virus empires have two-way exchanges of genes. The truth is we know very little about the virus world — considering its size and history — and the author postulates that viromes in unknown and unstudied viruses consist largely of uncharacterized "dark matter" (again, borrowing terms from cosmologists).

Koonin then approaches the next logical step backwards: the last universal common ancestor (LUCA). He starts by listing the arguments that cellular life indeed had a common ancestor and looks at competing theories (for example cell organization complexity versus genetic complexity leading to different models of varying degrees of cellularity). In chapter twelve, Koonin covers the topic that is often the hardest to imagine — the origin of life. This is interesting and particularly difficult because the translation system itself at some point evolved. Interestingly enough, these 60 protein-coding genes and ~40 structural RNA genes are the only complex ensemble of genes that are conserved across all extant cellular life forms. So, of course, the point in the evolutionary tree where this had developed is discussed as well as the Darwin-Eigen cycle. The latter requiring a system of a far greater complexity in order to be started. So the author begins examining the proposition that over time and due to their catalytic properties ribozymes lead to processive synthesis of peptides (long enough to be the first proteins). After discussing the eleven stages this would have to encompass, the author discusses the existing skepticism of models that try to explain how replication and transcription came about. This chapter also tackles geochemical and chemical propositions on the origin of life — something that has been discussed on Slashdot before. This research centers on networks of inorganic compartments consisting of catalytic surfaces with gradients of heat and acidity that could have supported primordial organic chemistry.

The book ends with a chapter devoted to reiterating topics as well as asking important questions like whether or not another biological evolution model is necessary/feasible as well as caution against logic like the progress fallacy or criticizing a concept like "the selfish gene" because it sounds "undignified." Though these are tempting arguments because of their simplicity, they have proven fruitless. A diagram on page 412 reminds us just how complex the flow of genetic material is between the virus empire and the cellular empire.

There are two appendices to this book and, perhaps because they use a softer language, they were much more accessible to me yet posed more questions than answers. Appendix A concentrates on the philosophy of postmodernism, the infeasibility of synthesis and the distrust of metanarratives. The author argues that any paradigm presented must include oversimplification and that we merely replace them with better metanarratives. It is also important to ask these questions about the current paradigms for without them we would never have come up with drift, draft and various neutral ratchets to improve old models. Koonin references Hawking and Mlodinow with the concept of model-dependent realism which stresses that scientists merely construct models that are in turn swapped out for better models given how well they explain data and predict the outcomes of experiments. Lastly Koonin refers to Popper's famous falsification paradigm and his subsequent position on how invaluable evolution is purely on the grounds that it arms us to model and understand specific experiments. The second appendix deals with roughly estimating the probability of life arising given inflationary cosmology. I know this back of the envelope math has become popular given recent discoveries of exoplanets in the news but I felt the few references to the "many worlds in one" model deserved to be placed in a separate book. Nevertheless, Koonin covers both the strong and weak forms of the anthropic principle and looks at the connotations they hold for evolution.

The references at the end of this book are extensive — 38 pages of two line references. It should probably be mentioned that Koonin's references to his own work consist of two of these pages although at no point did it sound like he was unfairly proffering his theories over others. At certain points I had to wonder whether or not I was reading a lightly adjusted abstract from a peer reviewed paper or a book. This is most evident in one of the figures of an appendix on page 437 that reads "This is a formulation of the 'weak' anthropic principle adopted for the context of this paper." Since it is a graphic and in the appendix, it's forgivable but caused me to wonder if the rest of the book couldn't be more seamlessly tied together with transitionary language for novices like myself. Amazingly, I found maybe one grammatical error and no typos in this book which was a refreshing experience for a first edition. Also, this is one of the best bound books I've had the pleasure of reading, its spine has held up to hours of laying it flat open while I googled for a better understanding. While $50 is pricey, the book is built to last and this $10 premium over the kindle edition is worth it if you must hold a physical copy of a book. It saddened me to be reminded that some states struggle with including the core concepts of Darwinian evolution anywhere in their K-12 curriculum. And should those students desire to break new ground in this modern field, texts like The Logic of Chance are that much further away from them.

You can purchase The Logic of Chance: The Nature and Origin of Biological Evolution from amazon.com. Slashdot welcomes readers' book reviews — to see your own review here, read the book review guidelines, then visit the submission page

Sasayaki writes "Hugh Howey's Wool, the self-published sci-fi story that's made him the best selling Indie sci-fi author of 2012 and currently the best selling sci-fi author on Amazon.com, has found its way into the hands of Ridley Scott (director of Alien, Prometheus and others)... who loved it. Rumor is the Hollywood movie will be coming to cinemas in 2013 or 2014. With Fifty Shades of Grey and now Wool getting the attention of Hollywood, it's clear the self-publishing revolution is here to stay."

theodp writes "His old day job at Gawker entailed calling BS on tech's high-and-mighty, but Ryan Tate still found things to like about Silicon Valley. In The 20% Doctrine, Tate explores how tinkering, goofing off, and breaking the rules at work can drive success in business. If you're lucky, your boss may someday find Tate's book in his or her conference schwag bag and be inspired enough by the tales of skunkworks projects at both tech (Google, Flickr, pre-Scott Thompson Yahoo) and non-tech (Bronx Academy of Letters, Huffington Post, Thomas Keller Restaurant Group) organizations to officially condone some form of 20% time at your place of work. In the meantime, how do you manage to find time to goof off to get ahead?"

jsuda writes "You would think that geeks would be as interested in fitness as dogs are of TV. After all, geeks already put in hours of finger dancing on keyboards, assembling hefty code fragments, and juggling PHP programming functions. Although intended, in part, as a guide to real physical fitness the book, Fitness for Geeks, entices geeks with what they are really interested in–the science of fitness, nutrition, and exercise. In 11 chapters over 311 pages (including notes and an index) author, Bruce W Perry, describes in great detail the science of fitness and all of its components–food selections, timings, and fastings; exercising of all types; sleep, rest, and meditation; the benefits of hormesis (shocking the body with stresses); and the benefits of natural sunlight." Read on for the rest of jsuda's review. Fitness For Geeks: Real Science, Great Nutrition, and Good Health author Bruce W Perry pages 336 publisher O'Reilly Media rating 6/10 reviewer jsuda ISBN 1449399894 summary shows the hacker and maker communities how to bring science and software into their nutrition and fitness routines. One of the major themes is respect for ancestral behaviors relating to fitness, as he sees the human body as having built-in "software" (biological and physiological "pathways") regulating its needs for certain foods and nutrients, its affinities for sprinting and intermittent fasting, and a preference for sunlight. These behaviors were evolutionary-based adaptations to their environment which in some ways was much more physically stressful than ours is now.

He argues that modern humans have gotten way too far away from their ancestral roots at the expense of their health and fitness. They would be better served by committing to behaviors which are modeled after those of our distant predecessors. That means large doses of natural sunlight, exercise programs emphasizing high demand tasks like sprinting, food selections high in quality fats and proteins and low in processed foods and sugars, and intermittent fastings. In other words, channel your inner caveman.

He supports his thesis with reference to hundreds of scientific studies. However, he doesn't sufficiently explain why modern human lifespans are so much longer than that of the ancients despite diets high in Twinkies, exercise defined as walking down the hall to the Coke machine, and light exposure limited to LCD illumination.

While the major interest of the book for geeks is in the science, Mr. Perry is also advocating real improvement in personal health and fitness. The author is a software engineer and computer-topic writer and also a serious runner, biker, and outdoor enthusiast. He seems to be a very intense proponent of maximum personal fitness both as an instructor and personally where he tracks and measures nearly every physical thing he does during the day. He monitors and measures macro nutritional ratios (carbohydrates, fats, proteins); micro nutritional consumption levels (vitamins, minerals, and phytochemicals); exercise metrics like energy use (Metabolic Equivalents of Tasks--MET's); the times, rhythms, and patterns of exercise program elements; and more.

Like a serious geek, he uses all the latest and greatest hardware and software tools to monitor and measure including GPS devices, motion detectors, smart phone apps of all kinds, and web-based trackers and analyzers. He describes many of the features of apps like FitBit, Endomondo, Fitocracy, and Garmin Connect, including screenshots of configurations, data charts, result pages, and comparison charts. He highlights use of web-based databases especially the nutritional information available at the USDA National Nutrient Database.

Mr. Perry also throws in a bit of food and food marketing politics as he emphasizes buying from local food suppliers, or even better, growing your own food and hunting your evening's meal. He shuns supermarket products, for the most part, even providing strategies on how best to navigate the typical mega markets to avoid being psychologically and emotionally manipulated by marketing techniques which attempt to get the consumer to buy more than they need, pricier items, and the latest junk foods they happen to be promoting that week. Mr. Perry is one serious guy!

I don't think that he is a typical health-concerned person or even a typical geek, although he is an independent spirit with great curiosity about things he's interested in. He seems to be serious about fitness to an idiosyncratic degree. In addition to all of the monitoring and measuring, he experiments with up to four different fasting strategies, goes for cold water swims, and does a variety of push-ups while waiting for boarding at the airport.

His book, I think, would appeal primarily to serious health freaks or competitive athletes who have the time and need to micromanage their eating, sleeping, and physical activities, and later analyzing all of the accumulated data.

The author writes knowledgeably and comprehensively about his topics and provides a lot of detail, especially on the tracking and measuring apps. He includes a handful of sidebar interviews with nutritional and fitness experts, some photos and graphics, and tosses in a few code references like anti-patterns and the random function, among others. What isn't in the book is referenced to websites containing more specific information, data, and videos.

Although he sprinkles some personal anecdotes and humor into the writing, overall, the book, while well organized, is a slow, often mind jumbling read. There is almost too much information, too many options to try out for some activities, and not enough focus. It will not win any literary awards. To some readers, it may be sort of like reading lab reports.

A lot of geeks like reading lab reports and there is a sufficient number of competitive athletes and health fanatics who'll find this book quite valuable and interesting.

You can purchase Fitness For Geeks: Real Science, Great Nutrition, and Good Health from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

New submitter nuvoleweb writes "Drupal Intranets with Open Atrium, by Tracy Charles Smith is a comprehensive guide to Open Atrium, the popular open source Intranet system. Open Atrium is a derivative (distribution) of Drupal specifically meant for group collaboration, and the author works in the Open Atrium core team at Phase2 Technology." Read below for the rest of Andrea's review. Drupal Intranets with Open Atrium author Tracy Charles Smith pages 284 publisher Packt Publishing rating 8/10 reviewer Andrea Pescetti ISBN 978-1-84951-112-4 summary A good manual for (prospective) end users of Open Atrium The book has a clear focus. It's tailored to people that have no experience with Drupal: it is ideal for organizations or companies that are considering to deploy Open Atrium internally and need an end-user manual, and it suits this task perfectly. On the other hand, this book won't be useful to developers and site builders who want to extend or customize Open Atrium. While the book was written based on Open Atrium 1.0, it still applies perfectly to the current version, Open Atrium 1.3.

Decision-makers who just need to assess whether Open Atrium can be the right solution for them will probably find answers already in Chapter 1, which gives a very good overview on the features and possibilities offered by the tool. After explaining the fundamental concept of groups (Open Atrium is meant for teamwork and it supports multiple teams, with independent work spaces), the author presents each feature available in Open Atrium with a sample screenshot and a summary. The only drawback is due to an inherent shortcoming: the Open Atrium features have deceptive names (for example, the Blog is actually meant for Discussions, while the Notebook is rather a Wiki), so the author cleverly renames them to clarify their meaning; but in doing so he is at times slightly inconsistent (the Notebook feature is called Wiki, Documents, Notebook and Handbook) with the potential to actually confuse a newcomer.

The target public will likely want to skip Chapters 2 and 3, that deal with system administration and installation. The installation instructions for Mac and Windows users (for Linux-based systems it would be enough to recommend to install the standard LAMP stack) are very detailed and comprehensive, and include important tips such as how to downgrade PHP in case of compatibility problems. A section explains how to use PHPMyAdmin to create the needed MySQL database, and it could be slightly simplified by proposing to create the database directly at the account creation. The book explains how to install Drupal, but this is only useful for troubleshooting, and not required for Open Atrium; then it proceeds with clear, illustrated, step-by-step instructions for Windows and Mac. Some Mac users might be put off by the lengthy command-line instructions proposed to perform operations that are easily done through the GUI, like copying files. The browser-based installation instructions are very clear, and they only miss a couple warnings: first, that the installation will automatically send a welcome e-mail; second, that the "Check for updates" checkbox will be discussed later, in Chapter 12. The final section is a great introduction to the administration panel, perfect for newcomers to know what they should and what they shouldn't do with it.

The "missing Open Atrium manual" is in Chapters 4 to 10. Anyone wanting to understand how Open Atrium works will find clear instructions here, and, whether you are evaluating Open Atrium or you are already using it and want proper documentation, your needs will be fulfilled by the time you finish Chapter 10. Everything is explained very clearly, with plenty of screenshots and examples.

The manual begins (Chapters 4-6) with two transversal topics to the Open Atrium administration, i.e., users and dashboard management. An alternative approach would probably be more effective for people new to Open Atrium, i.e., they should first become familiar with the key concept of Groups in Open Atrium and learn user and dashboard management only after Groups have been understood; this would allow to avoid several forward-references in Chapters 4 and 5 and to avoid explaining group creation twice, both in Chapter 5 and 6. However, Groups are properly covered in Chapter 6, even providing a sample mapping of an organization into Open Atrium groups. Some usability quirks of Open Atrium are also explained and workarounds are provided. Upon finishing this section, you will understand how to structure your Intranet in groups, what features you should enable in each group and how you can provide different front pages ("dashboards") for different groups or even different users.

The rest of the manual (Chapters 7-10) is a comprehensive guide to the four most important features in Open Atrium: Document Library, Blogs, Case Tracker and Calendar. About 100 pages with screenshots explain all details about the core features, ranging from the rather obvious functionality to advanced tips to make the most out of your Open Atrium installation. For example, there are valuable suggestions on the benefits of tagging content, hiding unwanted options in content creation, referencing content and other built-in functionality that is not immediately understandable, especially for users without prior experience in Drupal systems. The chapters are easily readable, with the only issue, again, that confusing synonyms are needed to cater for the awkward Open Atrium terminology (using case, bug, ticket, issue to mean the same concept).

The book then moves on to topics that will only be useful to the site administrator. For example, it explains how the site administrator can define new priority values and set default assignees in the Case Tracker. Then it moves on to more advanced tasks, like handling Views, but people wanting to configure the Open Atrium views will need a level of experience beyond the simple guided example shown in the book. On one side, this information is good since it explains basic customizations that most companies will want to apply; on the other side, the examples shown in the book are quite specific and cannot be generalized, i.e., you won't be able to configure the Blog based on how customizing the Case Tracker works. A long section is dedicated to running cron.php in order to keep the search index up-to-date, even though it would have been nice to mention poormanscron as an alternative and user-friendly solution. A good explanation of Drupal caching follows, with appropriate remarks explaining why block cache is unsuitable for Open Atrium. The book recommends the "all-in-one" upgrade strategy, i.e., waiting for distribution updates instead of upgrading individual modules as they are available, and this is fine, since indeed the Open Atrium maintainers are making a good job with a regular release schedule for security updates. A major shortcoming is a discussion on where the additional modules should be placed in the Open Atrium tree; at least, it should be mentioned that placing them in the Open Atrium profile may cause upgrade problems, and that the cleanest solution is to place them under sites/all. The book is completed by an Appendix listing Drupal resources and discussing briefly the concept of Drupal Features and Drupal theming, namely tips for Open Atrium subtheming.

In the end, this is a great book if you are an end user, or prospective user, of Open Atrium, especially in a corporate environment. If you already have some experience with building Drupal sites, you won't find anything new or interesting here, but you should definitely recommend it to your clients to save a lot of time to you and them.

You can purchase Drupal Intranets with Open Atrium from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

benrothke writes "While Julius Caesar likely never said 'Et tu, Brute?' the saying associated with his final minutes has come to symbolize the ultimate insider betrayal. In The CERT Guide to Insider Threats: How to Prevent, Detect, and Respond to Information Technology Crimes, authors Dawn Cappelli, Andrew Moore and Randall Trzeciak of the CERT Insider Threat Center provide incontrovertible data and an abundance of empirical evidence, which creates an important resource on the topic of insider threats. There are thousands of companies that have uttered modern day versions of Et tu, Brute due to insidious insider attacks and the book documents many of them." Read on for the rest of Ben's review. The CERT Guide to Insider Threats: How to Prevent, Detect, and Respond to Information Technology Crimes author Dawn Cappelli, Andrew Moore, Randall Trzeciak pages 432 publisher Addison-Wesley Professional rating 10/10 reviewer Ben Rothke ISBN 978-0321812575 summary Definitive resource on insider threats The book is based on work done at the CERT Insider Threat Center, which has been researching this topic for the last decade. The data the threat center has access to is unparalleled, which in turn makes this the definitive book on the topic. The threat center has investigated nearly 1,000 incidents and their data sets on the topic are unrivaled. With that, the book truly needs to be on the desktop of everyone tasked with data security and intellectual property protection.

The book provides a unique perspective on insider threats as the CERT Insider Threat Center pioneered the study of the topic, and has exceptional and empirical data to back up their findings. While there are many books on important security topics such as firewalls, encryption, identity management and more; The CERT Guide to Insider Threats is the one of the first to formally and effectively tackle the extraordinary devastating problem of trusted insiders who misappropriate data.

In the introduction, the authors write that a common misconception is that insider threat risk management is the responsibility of IT and information security staff members exclusively. The reality is that it is the responsibility of senior management to ensure that there is an overarching program to deal with insider threats at the enterprise level. Surpassingly and shockingly, far too few organizations have insider threat programs in place, and the book has scores of stories and case studies on those organizations that have become victims. While senior management created information security solutions to secure the perimeter; they were oblivious to the data leakage emanating from the interior network.

The authors reiterate that it is critical that all levels of management recognize and acknowledge the threat posed by insiders and take appropriate steps to mitigate malicious insiders. While it is impossible to stop every attack, what management can certainly do is build resiliency into their organizations infrastructure and business processes. This enables the organization to detect the attacks earlier and minimize the financial and operational impact. The book provides the specific details on how an organization can precisely do that.

In 9 detailed chapters and 6 appendices, the book provides a comprehensive and exhaustive analysis of the problem and menace of insider threats. After completing the book, one is well-prepared to initiate an insider threat program. The book provides examples of insider crimes from nearly every industry segment and ample data to share with management to convince them that the threats, both to their intellectual property and corporate profits, are very real.

After a high-level overview of the topic in chapter 1, the next chapter gets into the details of insider IT sabotage. While some think that stopping IT sabotage is next to impossible, the authors detail and have identified distinct patterns in nearly every IT sabotage case. The book details those patterns and also presents mitigation strategies, both technical and non-technical, to deal with those threats.

The chapter provides fascinating insights into how these crimes are carried out. The authors note that by their very nature, these attacks require technical sophistication and privileged access and are usually carried out by sysadmins, DBA's and programmers. A surprising CERT finding is that the majority of the attacks occur after the insider has been terminated or quit the organization. Part of the problem is that many organizations don't have a process in place to immediately terminate access when a worker resigns or is fired. In addition, 25% of the cases were carried out by full-time contractors.

Chapter 3 provides an intriguing look at the issue of insider theft of intellectual property (IP). Any firm that has a sizable amount invested in their IP (i.e., anything you can put on a USB stick) needs to take this chapter to heart. One of the many misconceptions CERT research has uncovered on this topic is that sysadmins are indeed not the biggest threat to IP, even though they have complete access to networks, systems and data.

According to the CERT data, they have not found a single case in which a sysadmin stole IP. Rather the biggest threat to IP is insider theft by scientists, engineers, programmers or salespeople. Also, CERT found that about a third of the IP cases were carried out for the benefit of a foreign government of organization, with China having more cases of IP theft than the other 9 countries combined.

Given the nature of China and its appetite for data theft, the book is surprisingly silent on specific suggestions in which to deal with threats from China. I would have liked to have seen at least a chapter dedicated to this topic.

The chapter continues and provides detailed lists of issues leading to job dissatisfaction that can lead a trusted employee or contractor to commit IP theft, and provides detailed steps on what companies can do to stop it.

Chapter 4 details everything you need to know about insider fraud. A fascinating statistic detailed is that the average insider fraud crime spans about 15 months, with half of the crimes lasting 5 months or more. The authors write that insider fraud is typically a long and ingoing crime. All of this is happening, over the course of months and years, and the organizations being pilfered are oblivious to it.

The book is worth reading for chapter 6 alone, which details best practices for the prevention and detection of insider threats. The best practices in chapter 6 give the reader a framework for establishing an insider threat program. Many of the best practices detailed are elements of a good security program, so they should not be news to anyone. Some of the best practices include: security awareness training, physical security controls, separation of duties, and perhaps the most blatantly obvious suggestion of them all: deactivate access following termination.

Another fascinating fact detailed in the book is that almost all insiders involved in acts of IT sabotage displayed behavioral indicators prior to committing their crimes. Some of those indicators include: conflicts with coworkers or supervisors, improper use of data assets, sanctions and rule violations. Organizations that act on these precursors can prevent the insider crimes from taking place.

Aside from its lack of coverage on how to specifically deal with the China threat, the only other lacking in the book is that in all of the examples and case studies, even those whose breaches are publicly known, organizations are not mentioned by name.

According to author Dawn Cappelli, Technical Manager at the CERT Insider Threat Center, they took that approach based on interviews for approximately 230 of their cases, with prosecutors, investigators, victim organization, or convicted insiders. In those interviews they guaranteed confidentiality of the information they obtained. Therefore, CERT considers the success of their research directly related to their reputation in the community for being trustworthy for maintaining confidentiality. While there reasoning makes sense, anonymous case studies are often unsatisfying

Insider threats are pervasive and indisputable. Organizations such as the CERT Insider Threat Center and individuals like Antonio Rucci provide vital services evangelizing about this critical topic. This entertaining video of Rucci from DEFCON 17 is a great primer on the topic.

Most of the firms who fall victim to insider threats are oblivious to them as they occur. The book details effective and operational security practices which can help every organization create an insider threat program to counterattack the majority of insider attacks.

When it comes to insider threats, the only way to avert them is to have a prevention program in place. In The CERT Guide to Insider Threats: How to Prevent, Detect, and Respond to Information Technology Crimes, the authors have created an invaluable guidebook, with myriad details in which to enable the reader do that. The facts around insider threats speak for themselves. Anyone charged with protection of corporate data should ensure this book is on their required reading list. If not, and they fall victim to an insider attack, they have no one to blame but themselves.

Ben Rothke is the author of Computer Security: 20 Things Every Employee Should Know.

You can purchase The CERT Guide to Insider Threats: How to Prevent, Detect, and Respond to Information Technology Crimes from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

benrothke writes "While Julius Caesar likely never said 'Et tu, Brute?' the saying associated with his final minutes has come to symbolize the ultimate insider betrayal. In The CERT Guide to Insider Threats: How to Prevent, Detect, and Respond to Information Technology Crimes, authors Dawn Cappelli, Andrew Moore and Randall Trzeciak of the CERT Insider Threat Center provide incontrovertible data and an abundance of empirical evidence, which creates an important resource on the topic of insider threats. There are thousands of companies that have uttered modern day versions of Et tu, Brute due to insidious insider attacks and the book documents many of them." Read on for the rest of Ben's review. The CERT Guide to Insider Threats: How to Prevent, Detect, and Respond to Information Technology Crimes author Dawn Cappelli, Andrew Moore, Randall Trzeciak pages 432 publisher Addison-Wesley Professional rating 10/10 reviewer Ben Rothke ISBN 978-0321812575 summary Definitive resource on insider threats The book is based on work done at the CERT Insider Threat Center, which has been researching this topic for the last decade. The data the threat center has access to is unparalleled, which in turn makes this the definitive book on the topic. The threat center has investigated nearly 1,000 incidents and their data sets on the topic are unrivaled. With that, the book truly needs to be on the desktop of everyone tasked with data security and intellectual property protection.

The book provides a unique perspective on insider threats as the CERT Insider Threat Center pioneered the study of the topic, and has exceptional and empirical data to back up their findings. While there are many books on important security topics such as firewalls, encryption, identity management and more; The CERT Guide to Insider Threats is the one of the first to formally and effectively tackle the extraordinary devastating problem of trusted insiders who misappropriate data.

In the introduction, the authors write that a common misconception is that insider threat risk management is the responsibility of IT and information security staff members exclusively. The reality is that it is the responsibility of senior management to ensure that there is an overarching program to deal with insider threats at the enterprise level. Surpassingly and shockingly, far too few organizations have insider threat programs in place, and the book has scores of stories and case studies on those organizations that have become victims. While senior management created information security solutions to secure the perimeter; they were oblivious to the data leakage emanating from the interior network.

The authors reiterate that it is critical that all levels of management recognize and acknowledge the threat posed by insiders and take appropriate steps to mitigate malicious insiders. While it is impossible to stop every attack, what management can certainly do is build resiliency into their organizations infrastructure and business processes. This enables the organization to detect the attacks earlier and minimize the financial and operational impact. The book provides the specific details on how an organization can precisely do that.

In 9 detailed chapters and 6 appendices, the book provides a comprehensive and exhaustive analysis of the problem and menace of insider threats. After completing the book, one is well-prepared to initiate an insider threat program. The book provides examples of insider crimes from nearly every industry segment and ample data to share with management to convince them that the threats, both to their intellectual property and corporate profits, are very real.

After a high-level overview of the topic in chapter 1, the next chapter gets into the details of insider IT sabotage. While some think that stopping IT sabotage is next to impossible, the authors detail and have identified distinct patterns in nearly every IT sabotage case. The book details those patterns and also presents mitigation strategies, both technical and non-technical, to deal with those threats.

The chapter provides fascinating insights into how these crimes are carried out. The authors note that by their very nature, these attacks require technical sophistication and privileged access and are usually carried out by sysadmins, DBA's and programmers. A surprising CERT finding is that the majority of the attacks occur after the insider has been terminated or quit the organization. Part of the problem is that many organizations don't have a process in place to immediately terminate access when a worker resigns or is fired. In addition, 25% of the cases were carried out by full-time contractors.

Chapter 3 provides an intriguing look at the issue of insider theft of intellectual property (IP). Any firm that has a sizable amount invested in their IP (i.e., anything you can put on a USB stick) needs to take this chapter to heart. One of the many misconceptions CERT research has uncovered on this topic is that sysadmins are indeed not the biggest threat to IP, even though they have complete access to networks, systems and data.

According to the CERT data, they have not found a single case in which a sysadmin stole IP. Rather the biggest threat to IP is insider theft by scientists, engineers, programmers or salespeople. Also, CERT found that about a third of the IP cases were carried out for the benefit of a foreign government of organization, with China having more cases of IP theft than the other 9 countries combined.

Given the nature of China and its appetite for data theft, the book is surprisingly silent on specific suggestions in which to deal with threats from China. I would have liked to have seen at least a chapter dedicated to this topic.

The chapter continues and provides detailed lists of issues leading to job dissatisfaction that can lead a trusted employee or contractor to commit IP theft, and provides detailed steps on what companies can do to stop it.

Chapter 4 details everything you need to know about insider fraud. A fascinating statistic detailed is that the average insider fraud crime spans about 15 months, with half of the crimes lasting 5 months or more. The authors write that insider fraud is typically a long and ingoing crime. All of this is happening, over the course of months and years, and the organizations being pilfered are oblivious to it.

The book is worth reading for chapter 6 alone, which details best practices for the prevention and detection of insider threats. The best practices in chapter 6 give the reader a framework for establishing an insider threat program. Many of the best practices detailed are elements of a good security program, so they should not be news to anyone. Some of the best practices include: security awareness training, physical security controls, separation of duties, and perhaps the most blatantly obvious suggestion of them all: deactivate access following termination.

Another fascinating fact detailed in the book is that almost all insiders involved in acts of IT sabotage displayed behavioral indicators prior to committing their crimes. Some of those indicators include: conflicts with coworkers or supervisors, improper use of data assets, sanctions and rule violations. Organizations that act on these precursors can prevent the insider crimes from taking place.

Aside from its lack of coverage on how to specifically deal with the China threat, the only other lacking in the book is that in all of the examples and case studies, even those whose breaches are publicly known, organizations are not mentioned by name.

According to author Dawn Cappelli, Technical Manager at the CERT Insider Threat Center, they took that approach based on interviews for approximately 230 of their cases, with prosecutors, investigators, victim organization, or convicted insiders. In those interviews they guaranteed confidentiality of the information they obtained. Therefore, CERT considers the success of their research directly related to their reputation in the community for being trustworthy for maintaining confidentiality. While there reasoning makes sense, anonymous case studies are often unsatisfying

Insider threats are pervasive and indisputable. Organizations such as the CERT Insider Threat Center and individuals like Antonio Rucci provide vital services evangelizing about this critical topic. This entertaining video of Rucci from DEFCON 17 is a great primer on the topic.

Most of the firms who fall victim to insider threats are oblivious to them as they occur. The book details effective and operational security practices which can help every organization create an insider threat program to counterattack the majority of insider attacks.

When it comes to insider threats, the only way to avert them is to have a prevention program in place. In The CERT Guide to Insider Threats: How to Prevent, Detect, and Respond to Information Technology Crimes, the authors have created an invaluable guidebook, with myriad details in which to enable the reader do that. The facts around insider threats speak for themselves. Anyone charged with protection of corporate data should ensure this book is on their required reading list. If not, and they fall victim to an insider attack, they have no one to blame but themselves.

Ben Rothke is the author of Computer Security: 20 Things Every Employee Should Know.

You can purchase The CERT Guide to Insider Threats: How to Prevent, Detect, and Respond to Information Technology Crimes from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

stoolpigeon writes "It is a well known fact that the United States has an obesity problem. There are numerous causes that ultimately lead to an imbalance in the ratio between the number of calories taken in to the number of calories burned. The size of the American diet industry is another good indicator of how widespread the problem has become. Clay Johnson believes that the issues the U.S. has with food have become mirrored in how we consume information." Read below for the rest of stoolpigeon's review. The Information Diet author Clay A. Johnson pages 160 publisher O'Reilly Media rating 8/10 reviewer stoolpigeon ISBN 978-1449304683 summary A Case for Conscious Consumption Understanding, and buying into, this metaphor of information obesity is key to The Information Diet. Johnson is aware of this and the text never wanders far from the comparisons. He begins with an extensive telling of the physical obesity issue that plagues the United States and then always frames the rest of his work in nutritional/fitness terms. A few chapters are "Welcome to Information Obesity", "The Symptoms of Information Obesity", "Attentions Fitness" and "How to Consume." Readers who don't buy into the parallels are going to have a really hard time with the book. The comparison and prescriptions for behavior never wander far from the picture and so it's not something one can brush off early on and then ignore for the rest of the book. I think that Johnson is right, so I dug into the book, eager to see what he recommended.

I don't think that anyone would argue about the physical obesity problem. I think what readers may be skeptical about is this idea of information obesity. The premise that Johnson puts forward is that we have access to more information than ever before, much in the same way that developed nations have more food available than ever before. (I will let the reader continue to draw the parallels — this example should be enough to figure it out.) While we have more information than ever before, not all information is equal. Some information is good for us and some is not. Another problem is that we tend to seek certain kinds of information that can give us a skewed and inaccurate view of the world we live in. People have access to more information yet they become more ignorant.

Johnson is an activist. Much of his life has been about affecting change. He is very upfront about this and the book contains a large amount of biographical information. Of course this is because he must. Johnson is laying out an argument for digging past the fluff, the bias and finding ways to be informed by facts. But he has his own built in bias and internal spin that he must counter even as he encourages the reader to do the same. I think that for the most part he has managed to do this well, not necessarily by being completely objective but by being transparent. Some of his examples felt a little weak to me, but this is because I had such a different approach to the event, topic or people that he chose as examples. I think his underlying observations were correct, and his sharing freely about his background and default positions helped me to reconcile his main point with my reservations about the specific examples.

The first six chapters are part of the introduction section and lay out Johnson's case for the information obesity problem. The next four chapters are the actual "Information Diet". Here Johnson moves from describing the problem to full on advocacy. Always striving for objectivity Johnson is always quick to describe what science is out there to give light to his position. The problem is that there just isn't much of it out there. This means that the diet itself is a mix of what has seemed to work well for Johnson himself and some broad recommendations. This may be frustrating to anyone who is looking for hard and fast direction. It's not that Johnson doesn't give concrete suggestions, it's just that he can't claim any assurance that they will work for anyone but himself. That said, I think there is a good chance that many of his ideas about how we spend our time taking in information, how we find sources and tools as well as attitudes that may help seem to be good. I think that anyone who moves from being unaware of the issue to being intentional in how they take in information is better off by that change alone.

Working through this process of finding the "diet" that works for someone is something they may want to do with others. With this in mind, and I think reflecting Johnson's bent as an activist, there is an Information Diet web site with a blog, resources and information on things like events. It is tied into some social tools and so one is able to interact with other information dieters.

Unfortunately this site is at once a marketing tool for the book (hoped 'movement' I guess) and this reflects the constant tension that exists in the fact that Johnson is at once pushing for social change and seeking to profit at the same time. He is constantly in danger, while writing and in the external resources for the book, of violating the principles he is endorsing. A friend recently told me, "David Benatar, author of Better Never to Have Been: The Harm of Coming into Existence, which argues against procreation, dedicates this book to his parents." It's that appearance of contradiction that pops up here as well. I'm told to filter out more noise, seek out better information and twitter and if I like the idea here are the buttons to let the world know on Facebook, Twitter, g+ or email. It's not that this can't all be reconciled, it is just jarring. This is something that will drive skeptics nuts and I dinged my rating of the book for it, though I think the good outweighs the bad in this regard. Just because the site exists, I don't think that invalidates the thought and I don't have to go there. I feel I've benefited from the book alone.

The book is squarely aimed at an American audience. That's pretty clear from the get-go. Much of Johnson's life has been involved in American politics, the obesity metaphor works well for an American audience and so it makes sense that this would be the scope of the work. I think that is unfortunate because I believe there is a broader application for his ideas with regard to how information is processed and the explosion in the amount of information available. A person who is not an American could read the book and I am sure find some good things to take away but understanding many of the stories and examples would be difficult without some knowledge and understanding of American culture and recent history.

The third section of the book, "Social Obesity", Johnson returns to his enumeration of the ills caused by information obesity. The people who lose out due to poor information habits are not just the individuals but the society as a whole. Johnson invites readers to become a part of a "Vast Rational Conspiracy." I believe he is genuine in this call to action and that is what allows me to forgive some of the efforts around the book that look more self-serving. I believe he is truly trying to fuel a fundamental shift in discourse and knowledge in the United States. This also causes me to be more sympathetic about the geographical focus, though I think it is only fair that readers from other countries be warned. Johnson has created a call to action and he's starting with his home. I am sure he would love to see it spread and move beyond the borders of his native country. The skeptic would again see this happiness as a function of increased personal gain. I'm a little more optimistic, or maybe just a sucker.

This last section is the shortest. It includes a note to programmers that ought to at least be a bit of an ego boost, as they learn they are the new "scribes" of our age. Or having, as Johnson puts it, "...a better ability to figure out the world than anybody else." The appendix with further reading has some great pointers to good reading on-line and in books.

I've rated The Information Diet 8 of 10 because I think Johnson at moments loses the battle to not engage in the kind of objectivity that he advocates and because the book has such a regionally focused audience. That said, it has changed my behavior and I think that it has a positive place. In fact I've become an advocate for many of the ideas, even when I don't recommend the book itself. I recently ran into a barrage of emails from various co-workers advocating that we "turn off technology" because it is too distracting from real life. I found this to be rather annoying because there are always distractions and tech is also important and a force for better lives. The ideas in The Information Diet have given me options to offer people that let them gain control of the information sources in their life rather than giving up and just shutting them all off.

Will the The Information Diet have a great impact over time? I am really not sure. I think that it is definitely a precursor of things to come. Just by being published it will encourage others to copy it and I think we will see the parallel to physical diet and eating continue. But will Johnson finally achieve his goal of making the world a better place? Only time will tell, but I think it is a noble effort.

You can purchase The Information Diet: A Case for Conscious Consumption from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

You recently got the chance to ask a group of MIT researchers questions about fusion power, and they've now finished writing some incredibly detailed answers. They discuss the things we've learned about fusion in the past decade, how long it's likely to take for fusion to power your home, the biggest problems fusion researchers are working to solve, and why it's important to continue funding fusion projects. They also delve into the specifics of tokamak operation, like dealing with disruption events and the limitations on reactor size, and provide some insight into fusion as a career. Hit the link below for a wealth of information about fusion. 1. What have we learned?
by jank1887

Fusion is one of those technologies that is always '50 years away,’ even 50 years ago, maybe even 50 years from now. So, looking at what's actually happened recently: What do we actually know now that we didn't know 10-15 years ago that gives support to the notion that we're making progress? Or, what are the 'big' things we know now? Similarly, what are the things we still don't know that we could reasonably expect to find answers for in the next 10-15 years?

MIT Researchers: As researchers in this field, we have heard the expression "Fusion is 50 years away and always will be" more times than we would like to admit. The implication of this statement is that no real progress has been made in the field, which is simply not true! We have made a great deal of progress, even in the last 10–15 years (which have been very lean times for funding). We’ll try to summarize some of the new findings, in no particular order:

1) Internal Transport Barriers/Reversed Shear operation –
We have actually discovered a way to improve upon the performance that we get in H- mode plasmas. These improvements come in the form for so called internal transport barriers. In the past 10–15 years we have begun to understand how to modify the current flowing in tokamak plasmas so that we create effectively what is a barrier in the middle of the plasma. Like the edge barrier in H-mode plasmas, this barrier restricts particles and energy from escaping the plasma and enhancing the overall performance. 2) I-mode –
In just the last 5 years, a new operational regime has been discovered on the Alcator C-Mod tokamak at MIT. This is termed the I-mode, or “Improved L-mode” regime. When the tokamak is operated in this manner it exhibits excellent energy confinement properties, keeping the plasma hot. At the same time the plasma does an excellent job of expelling impurities which dilute the fusion fuel and reduce the number of fusion reactions which can occur. It is particularly important to us as it was first observed on Alcator C-Mod, and is now under active development at many other tokamaks around the world.

3) Development of Predictive Models –
Great advances have been made in the development of predictive computer models, such as gyrokinetic and magnetohydrodynamic (MHD) formulations. Years of experiments have revealed that plasma turbulence is often primarily responsible for the loss of particles and energy from fusion reactors. In the past 10–15 years we have developed advanced models which are thought to contain sufficient physics to simulate plasma turbulence and predict the performance of future fusion devices. At this time we are in the process of validating these models, i.e. comparing them directly with experiment to ensure they are correct, but we are approaching the ability to reliably predict the performance of fusion plasmas without the need for a fusion reactor. This can motivate engineering design and operational choices for future fusion devices.

4) Self-acceleration of the plasma (intrinsic rotation) –
Over the past decade, it has been discovered (on Alcator C-Mod and elsewhere) that plasmas can spontaneously rotate, at speeds of tens of kilometers per second. (Imagine the donut-shaped plasma spinning on its axis.) This turns out to have beneficial effects for stabilizing turbulence at the edge, as the spinning plasma causes the turbulent eddies to break up before they can carry hot plasma out of the core. This is an exciting area of research that could have big implications for the performance of a tokamak reactor.

5) Disruption mitigation –
One of the main problems with a tokamak is the ‘disruption’, when the plasma energy is suddenly lost, stopping any fusion that is occurring and requiring a restart of the reactor. (See the question below for a lot of detail about this!) In extreme cases, these disruptions can cause damage to the wall of the tokamak – which would require repairs before the machine can be restarted. Over the past decade, we have developed techniques to mitigate these disruptions, causing the plasma to come to a rapid shutdown that does not negatively affect the wall condition. Work is underway to scale these techniques up to a reactor-size device (ITER).

6) ELM control/avoidance –
Another longstanding problem with tokamaks is periodic ‘bursts’ of energy from the edge called Edge-Localized Modes (ELMs). In today’s devices, ELMs are not a problem, but in ITER and future reactors, they could carry enough energy to damage the wall in the divertor region (where most of the energy comes out). There has been rapid progress lately (past 15 years) in ways to control these ELMs by making them more rapid and smaller, such as using resonant magnetic perturbation (RMP) coils to distort the shape of the confining magnetic field, or ‘pellet pacing’ (firing small pellets of deuterium fuel into the machine 50–60 times per second, which triggers an ELM), or vertical ‘kicks’ in which the control system suddenly jogs the plasma position a few centimeters vertically, also triggering an ELM. Between these techniques and the recently discovered I-mode (which doesn’t have ELMs), this is a problem that is well on the way to being solved.

7) High-Z walls –
This is a particular point of pride for Alcator C-Mod. Running a tokamak with walls made of refractory metals has many advantages because of the extreme capacity of these materials to absorb heat loads, but there are disadvantages as well, such as how radiative these high atomic number elements are if they get into the plasma as impurities, or how metallic materials distort when they melt, rather than ablating like carbon-fiber composites. Alcator C-Mod (which has a molybdenum wall) and other tokamaks have recently shown that it is possible to reliably run a tokamak with high-Z refractory metal walls, which will almost certainly be a feature of future reactors.

2. Power Loss Scenario in Alcator C-Mod?
by eldavojohn

Not to raise any fears -- rather out of genuine curiosity -- what happens when the magnetic fields that hold the 90,000,000 degrees Celsius plasma in place fail or loser power on the Alcator C-Mod? I understand it's probably in prototype mode, but what sort of safety advantages or disadvantages do Alcator C-Mod designs offer over conventional, large-scale designs? Does the plasma come into contact with the toroidal superconducting coil? Then what?

Geoff Olynyk answers: Actually, that’s exactly what my research is on! The event you describe is called a "disruption." Holding a hot plasma stationary using magnetic fields without it ever touching material surfaces is very difficult – Richard Feynman once compared it to trying to "hold Jello with rubber bands." For any number of reasons, like a magnetic coil losing power, the control system not being able to juggle the plasma position quickly enough, or the plasma hitting a stability limit (pressure or density goes too high), it’s possible for the plasma to hit the wall. The most important thing to know, though, is that when this occurs (and it does, frequently, in today’s experiments – although it’ll have to be a very rare occurrence in a real power reactor so it produces uninterrupted electricity), it is no risk to the environment or to safety.

To understand what happens, you have to realize that the plasma is very, very light. In the Alcator C-Mod tokamak, it has a mass of only about 0.001 grams – about one- fiftieth as much as the smallest drop of water you can get from an eyedropper. (This is with a plasma volume of about a cubic meter – a fusion plasma is actually a pretty good vacuum!) So even though it’s very hot, it doesn’t actually have a lot of thermal stored energy to flow into the wall if confinement is suddenly lost. There is actually more energy stored in the current flowing in the plasma (in C-Mod, about a million amperes), which also gets deposited on the wall. In C-Mod, thermal stored energy is about 50– 150 kJ and magnetic stored energy is almost 1000 kJ. The problem is that as we go to larger machines (like ITER, or a reactor), the amount of stored energy in the plasma scales like the cube of the size, and the wall area only scales like the square of the size. So the energy deposited per square meter of wall area gets worse (larger) as we go up in machine size.

The plasma doesn’t hit the superconducting coils - it hits (really, deposits its energy on) the “first wall” of the chamber closest to the plasma. So, we do two things to make sure that the walls can survive these disruption events. The first is making them out of materials that can take a blast of heat, like tungsten, or else materials that ablate away rather than melting, like carbon fiber composites. The second is to develop “disruption mitigation” systems which can cause the plasma to radiate all its energy evenly over the entire wall surface, spreading the heat out and lessening the chance of causing localized melting. But I want to stress again - disruptions are an operational problem, meaning they might cause a power plant to be offline for a while, but they’re not a safety problem. There is no chance of a runaway reaction or meltdown in a fusion reactor.

3. Ubiquitous Fusion Power
by monsted

When will fusion power my house (or vehicle)?

MIT Researchers: This is obviously an impossible question to answer, but we can give some thoughts about when it might happen, and why. First, the current official plan is that ITER will demonstrate net fusion gain (Q = 10, that is, ten times more fusion power out than heating power put in) in about 2028 or 2029. (Construction will be done by about 2022 but there’s a six-year shakedown process of steadily increasing the power and learning how to run the machine before the full-power fusion shots.) At that point, designs can begin for a “DEMO”, which is the fusion community’s term for a demonstration power plant. That would come online around 2040 (and would putt watts on the grid, although probably at an economic loss at first), and would be followed by (profitable, economic) commercial plants around 2050.

This seems like a long time, and it is, but it’s important to understand that this is not the only possible path. You might say that we’re not a certain number of years away from a working fusion power plant, but rather about $80-billion away (in worldwide funding). We’ll get into this more in response to one of the other questions, but there are other experiments that could be done in parallel with ITER that would certainly speed up the goal of a demonstration power plant, if there were the money for it. Here is a graph based on a 1976 ERDA (predecessor to today’s DOE) fusion development plan, showing their four paths to a reactor, as well as a business-as-usual funding case that would never lead to a reactor, and in black is the actual funding amounts. (All values are adjusted to 2012 dollars.)

In the U.S. at least, fusion funding hasn’t been anywhere close to what would be required for a “crash program” to get to a reactor. If it were, it would probably be possible to have a demonstration reactor in about twenty years. (This is not actually that long - given that it takes almost a decade to build a large fission reactor or hydroelectric dam!)

Fusion has a reputation of “always being thirty years away” (or fifty, or twenty). We want to address that head-on here: aside from a few over-optimistic predictions made in the very early days of magnetic fusion research (the 1950s), this reputation is undeserved. The reason it has taken so long to get to breakeven (ITER) is because since the end of the 1970s, funding for fusion research has been continually slashed, up to today, when the U.S. is proposing shuttering one of three remaining tokamak experiments, the Alcator C-Mod device at MIT that we all work on. Despite this, progress has been continuous. But if we had the money, we would be getting there quicker.

4. What are the economic numbers for a successful, commercial reactor?
by kestasjk
I know that the economics of larger reactor = more economical are well known with tokamaks. Does this mean you have a good idea of the minimum cost / generating capacity of the first commercial reactors? If so, what do those numbers look like?
7. Lower Limit on Tokamak Design
by gyepi
Are there any good guesstimates on how small a tokamak-based fusion reactor (which produces more energy than it consumes) can become? Theoretical limitations on the size of the reactor would have obvious implications for pragmatic issues.

MIT Researchers: Questions 4 and 7 are similar and we answer them together here.

The current thinking is that a tokamak fusion reactor will be about 1 gigawatt electrical, and about 2–3.5 gigawatts thermal (depending on how high-temperature the blanket is and thus how thermally efficient it can be). This is about the size of a current fission reactor or large coal-fired power plant.

Fusion researchers are working on smaller designs, though! At MIT, some students are working on a concept for a 350–500 MW (thermal) class fusion reactor, which would be cheaper to field and thus more likely to be built by private industry with limited access to capital. This is still early work, though, and the economic analysis is not done yet.

Cost estimates for a new technology like fusion cannot be terribly reliable, but several studies suggest that, with suitable developments in science and technology, the costs could be competitive with other methods of electricity generation. We recommend you read the ARIES-AT study (google it), which goes through all the factors that go into the cost of electricity (COE) for a fusion reactor, and compares their concept to other electricity generation options (fission, fossil fuels, etc.) A key advantage of fusion is in what economists call "external costs." These are costs borne by society as a whole and not by the generating industry. Environmental pollution, nuclear proliferation, and military operations to protect oil supplies are all examples of external costs for energy.

5. What Problems are Holding Back Successful Reactions?
by Bucc5062

Can you explain to a non-scientist what the biggest stumbling blocks are for an effective fusion reaction? Is it truly a matter of throwing money down an energy hole, or are there verifiable, measurable benchmarks that lead us from one step to the next? I.e. we’ve achieved X, now we need Y; when we get Y, we get Z and then achieve fusion. Is it the technology holding us back, the politics, or the science?

MIT Researchers: We know exactly what we need to do. Not everything has a solution yet – that’s why it’s still a research project! – but we generally know what the big challenges are to get to a working magnetic fusion reactor. Here is a non-exhaustive list:

• 1 – Non-inductive current drive. We can’t rely on inductors to drive the plasma current since they are inherently pulsed (not steady-state). We think that lower hybrid current drive might be the solution, and are actively researching this on Alcator C-Mod.
• 2 – Confining a 'burning plasma.' This is the big question that ITER will resolve – can we really confine a plasma that is dominantly self-heated – that is, most of its energy comes from fusion reactions rather than external heating. Will new instabilities appear? Or can we confine the plasma as we expect we can.
• 3 – Confining a steady-state burning plasma while avoiding off-normal events. We have to do both of the previous points at the same time! And we can’t have disruptions too often or else the power plant won’t have a high enough duty factor. The goal is to have disruptions (which require a shutdown) occur less than once per year.
• 4 – Validated predictive capability for fusion-grade plasmas. We have made great progress in this field already (see our answer to an earlier question), but it’s not at the point yet that, say, fluid mechanics codes are, where Boeing can design an entire plane in the computer before ever building a scale model. We need our models of fusion plasma behavior to be accurate and reliable enough to design first-of-a-kind machines that we are 100% sure will work the way we think they will.
• 5 – Diagnosing a burning plasma. It’s really hard to tell any of the properties of the plasma even today, when we use pure deuterium fuel (instead of ‘live’ deuterium–tritium fuel), and our plasmas are colder than they would be in a reactor! You can’t, for example, stick a thermometer in to tell the temperature! We have to use subtle effects like bouncing a laser beam off the electrons and telling the temperature from the Doppler shift of the laser from the moving electrons (a technique known as Thomson scattering). Making these diagnostics work in the reactor environment, with higher plasma temperatures and a ferocious flux of neutrons coming out, is a great challenge.
• 6 – Better understanding of plasma–wall interactions. The plasma is confined by magnetic fields, and ideally doesn’t touch the wall at all, except in a very small area called the divertor. This means that the material challenges in the divertor are severe – we have to figure out a way to operate the plasma so that it’s hot in the center, but cold near the divertor, so that it doesn’t erode the wall too fast. This will be a limiting factor on how long you can run a fusion power plant for before you have to shut it down in order to do maintenance. Ideally, we’d want this to be every 2 years or so, like fission power plants today.
• 7 – Materials for plasma-facing components. We need to develop new materials that can withstand the high temperatures of the wall of a fusion reactor while resisting neutron damage and not becoming too activated by the neutrons that will pass through them. (There is some progress on this front with ferritic steels and silicon carbide.)
• 8 – Magnets that meet the plasma physics requirements and allow reactor maintainability at reasonable costs. (Some of us are working on demountable superconducting coil concepts that may eventually be the solution to this!)
• 9 – Design and materials for tritium fuel cycle and power extraction. Fusion reactors will breed their own tritium fuel from deuterium – this process has to be experimentally tested on a large scale (which will obviously require a burning plasma tokamak).
• 10 – Reliability, availability, maintainability, and inspectability (RAMI) of the reactor designs. We have to show that our concepts for reactors really are as good as we think they can be.

The point is that it’s not a money pit. There are unsolved challenges, but we know what they are, and with adequate support, these challenges will be overcome. This is why we are urging everyone to go to fusionfuture.org and write Congress asking them to keep supporting U.S. fusion research! (It’s very easy – there’s a link at the right on the website.)

6. NIMBY
by GeneralTurgidson

How do you explain the safety/benefits of fusion to a generation of people terrified of nuclear anything?

MIT Researchers:This is where fusion really shines. The two big problems (at least, perceived problems) of fission reactors are the risk of a meltdown, and what you do with the high-level radioactive waste. Fusion has neither of these issues!

Regarding the first, the reason why a worst-case accident in a fission reactor can be so devastating is because there is a lot of fuel in the reactor at any one time. There are well known accidents at Chernobyl (where the reaction ‘ran away’, making more power than the reactor was designed to handle) and Fukushima, where the fission chain reaction was safely shut down, but the cores melted down when the tsunami knocked out the cooling systems, due to ‘decay heat’ which is produced by the used fuel even after shutdown.

In a fusion reactor, it’s a completely different story. There will be less than a gram of fuel in a reactor at any one time—fresh deuterium–tritium fuel is continually added as it is burned—and so a runaway reaction is simply not possible. Decay heat isn’t a problem in a pure fusion system, again because there just isn’t any fuel sitting there undergoing nuclear reactions once the reactor is shut down. In general, this is one area where it’s a benefit that a fusion reaction is so hard to sustain! We have to try really hard to keep the plasma hot enough to undergo fusion in the first place, so if we just turn off the heating and fuelling systems, the fusion reaction will shut down very quickly.

As for the second benefit of fusion (waste), the reaction is completely different from that in a fission reactor. In fission, uranium (or other heavy elements like plutonium) split into pieces, producing hundreds of different isotopes, some of which are radioactive, with half-lives ranging from fractions of a second to millions of years. In fusion, the reaction is simple, deuterium + tritium helium + neutron. So there is no “waste” from the unburned fuel – any tritium that isn’t burned gets pumped out of the chamber and recirculated back in.

This is not to say that there will be no radioactive waste from a fusion plant. The reactor vessel itself will become activated because of the flux of neutrons passing through it, and will have to be treated accordingly when the plant is decommissioned (after, say, a 50-year operational period). But it’s important to note that this kind of radioactive waste is of a much lower level – it won’t have to be stored for very long before it will be “cool” enough to simply bury in the ground safely. And there is active research going on into new materials for fusion reactors that are more resistant to activation by neutrons, such as ferritic steel and silicon carbide.

Finally, fusion has great advantages for nuclear non-proliferation. Creating enough fission power plants to avoid climate change would mean that the plutonium moving around the world would be enough to create about 100,000 nuclear weapons. For fusion, it is much more difficult to use a reactor to make fuel for weapons. This is also something that we think a nuclear-skeptical public will appreciate about fusion power.

All of us are strong supporters of fission power, and we agree that at times, the nuclear power industry has not received a fair shake when compared to other sources of energy. But we think that the advantages of fusion power speak for themselves, and the public will be able to understand the risks and will support the construction of these plants. Obviously, having media that are able to explain things clearly and fairly are a necessity.

8. What do the numbers really look like?
by Erich

ITER is a hugely expensive project, and won't produce a commercially viable power generation system. In a lot of areas where research is done on things which don't work yet -- rockets, bridges, transmission systems, etc -- there's a general idea of how things might be able to "scale up" to meet the goals. Is tokamak fusion really in sight of being a commercially viable source of energy? If we need unobtanium to make a commercially viable reactor, wouldn't it make sense to wait until the materials are viable before making even larger tokamaks? Or is it still worth learning from these new, bigger, more expensive reactors?

MIT Researchers: You are exactly correct in your statement; ITER is an expensive project which will not produce electricity upon completion. However, ITER’s main purpose is not to put watts on the grid, but to demonstrate the scientific feasibility of fusion by creating a Q=10 plasma (10 times as much energy out as we put in). We do have a good idea of how to proceed with devices following ITER, namely DEMO, a full demonstration fusion power plant which will use the steam cycle to generate electricity from the fusion reactor. The basic layout of a reactor can be found here: http://www.fusionfuture.org/what-is-alcator- c-mod/c-mod-for-energy/

Although there is still plenty of research which remains, fusion is in sight of being a commercially viable energy source. We believe that we now understand the physics well enough to create the appropriate plasma conditions (this will be demonstrated on ITER) and we are working on the engineering challenges that lay between us and a commercial fusion reactor.

It is obviously impossible to predict when fusion will put power on the grid since the estimate can change drastically based on demand and overall funding levels. You are however, correct in noting that some of the biggest challenges involve the discovery/ development of materials which can resist the unique and harsh conditions associated with fusion reactors, namely, high heat and neutron fluxes. Due to its importance to the success of future devices, this is a very active and important area of research.

The international fusion community is attempting to address these issues in the following manner: Given the scope of the ITER project and the time required to build and test it, we are planning on constructing a materials testing facility named, IFMIF which stands for International Fusion Materials Irradiation Facility. This facility should be operated at the same time as ITER and will be addressing the materials issues associated with an eventual fusion power plant while ITER is demonstrated the scientific feasibility of a fusion reactor.

Given the time-scales for reactor construction, we think it would be unwise to wait for this materials testing to be complete before starting new machine construction. Addressing the remaining problems in parallel will most likely result in the quickest path to fusion energy.

9. Careers in Fusion?
by benjfowler

As practicing researchers, can you tell us about the health of the pipeline of young researchers coming into the field? Is there a glut of trained physicists at this stage, or is there still a need for trained specialists to enter the field, especially with ITER and follow-on machines coming online in the next couple of decades?

Nathan Howard answers: At this point in time fusion is actually a pretty healthy field in terms of young researchers and with emergence of the next generation devices such as ITER, there should be an influx of researchers stepping up to meet the need for trained specialists on these next gen devices. Currently in Europe and Asia, emphasis on fusion research is ramping up to support the research needs. These newly trained researchers are going to be the scientists working on ITER in 10-15 years.

Unfortunately, the US fusion program is in danger of going the opposite direction of the Asian and European programs. The current proposals made by the US are threatening the health of fusion in the US. The President’s 2013 budget proposal calls for drastic cuts to the domestic fusion budget to pay for increased funding for the ITER budget. However, if these cuts continue, there will not be a field for the young researchers to enter and the US fusion program is in danger of dissolving before ITER comes online.

This does not mean that a need for trained specialist will not remain, it just means that the young researchers in Europe and Asia will be filling these positions. Dr. Stewart Prager, the head of Princeton Plasma Physics Lab said it best, “We have a clear choice before us: The United States can either design and build fusion energy plants or we can buy them from Asia or Europe.”

As a young researcher myself, I am particularly affected by the choices that the US is currently making. Myself and other graduate students have been urging others who support fusion research to contact congress and tell them to continue to fund domestic fusion research. We put together a website, www.fusionfuture.org, which provides more information and people the ability to quickly and easily contact their congressmen to tell them to support research. Please support US fusion research and check out the site.

12. Patents?
by Anonymous Coward

Will patents get in the way of your research?

MIT Researchers: In general, we find that the tokamak labs of the world are extremely cooperative; patents have never been a problem. It does seem likely that the technologies supporting power plants will be highly patentable, but the sort of scientific knowledge we’re accumulating at present really isn’t. At some point, we expect to move from a collaborative to a competitive phase – but we’re not there yet.

11. What level of investment would get fusion going?
by Tragek
Do you think a program the size of the Apollo program could kickstart fusion to general availability? Or would a smaller program suffice?
14. What could you do with unlimited resources?
by petes_PoV
Given $1 trillion, the pick of the best brains in the world to work willingly on the project, a large enough location away from any and all governmental regulation and every facility you could ever need - when would fusion be commercially viable?

MIT Researchers: Questions 11 and 14 are similar and we have answered them together.

Any kind of question asking about a hypothetical massive increase in funding is tricky to answer. We probably couldn’t even spend a trillion dollars if we wanted to – just because it would take a long time to get enough people trained in plasma physics and fusion energy.

We can say this: an increase in funding would allow for different paths to be tried in parallel, like stellarators, tokamaks (ITER), spherical tokamaks, etc. Plus, we could build a facility in the United States to study the problem of plasma–wall interactions, which is a very important topic that has not been adequately studied up to this point (see our answer above about what steps are needed to get to a reactor).

We think that we’re roughly $80-billion away from a reactor. At current levels of funding (worldwide), that’s about 40 years. Even given access to huge amounts of money, it’s unlikely that a working reactor could be built in less than a decade – there are just too many facilities to build between current devices and a full-scale reactor in order to ensure success. But we could certainly do it faster than 40 years!

We want to note that “crash” programs like Apollo or the Manhattan Project succeeded because they took risks – they started work on building their systems before they had done all the homework. That is inherently risky, but these risks are mitigated by pursuing alternatives in parallel. Something similar could be done in fusion, given the money.

15. Your favorite books?
by eldavojohn

I'm not a physicist (software guy), but I've taken a few physics classes. At an early age I found a tattered copy of George Gamow's One Two Three . . . Infinity, which, although incorrect in some parts (I guess that's why they revised it and that's why 'speculations' was in the title), was perfectly written for my then-fifth-grade mind. It set me on a path toward science, and a few weeks ago I saw the same 1960s Viking Press edition and flipped through it, noticing what was slightly off and remembering it. I've since grown to love other obvious books by authors like Hawking, Penrose, Hofstadter, etc. So, quite simply, what are your favorite books for all minds, young and old? Also, can you annotate which are written for the layman's entry into the given field and which are written to encompass the field for the researcher? I find that some books start off with the jargon so strong and the references and footnotes so thick that you start to have to re-read every paragraph, as they're clearly condensing entire historic papers into lengthy sentences. Any fiction books worthy of influencing your work and desires?

Ian Hutchinson: My all time favorite novel is Godric by Fredrick Buechner. It's a wonderful first-person portrait of the prior life of a medieval hermit. My favorite physics teaching text is the Feynman Lectures on Physics, which comes from a remarkable effort by the most widely acclaimed american physicist of the 20th century to explain really advanced physics to undergraduates.

I really don't enjoy the genre of books that combine science popularization with metaphysical speculation. They are of course quite popular, but most are philosophically naive in a way that I find annoying.

Anne White: I like detective/adventure stories. I also enjoy reading plays, poetry and short stories – some authors I read over and over are Wolfgang Borchert, Julio Cortazar, Ray Bradbury and Samuel Beckett.

Recently, I've enjoyed reading The End of the Affair by Graham Greene, People of the Book by Geraldine Brooks, Jane Eyre by Charlotte Bronte and Her Fearful Symmetry by Audrey Niffenegger.

Influential books/stories that I remember reading when I was young : The Pearl (John Steinbeck), Catch-22 (Joseph Heller), Flatland, and Ender's Game.

Dennis Whyte:

• For science non-fiction books, it’s a tie: The Selfish Gene by Richard Dawkins, and Wonderful Life by Stephen Jay Gould.
• Novel (in general subject area of science): The Baroque Cycle by Neal Stephenson
• Speculative fiction: Starship Troopers by Robert Heinlein

Geoff Olynyk: The Making of the Atomic Bomb by Richard Rhodes is the best non-fiction book I’ve ever read. It’s a bit long, but is a fascinating, well-written exploration of the project to develop the atom bomb (both in the U.S. and elsewhere).

This is not a science book, but The Rebel Sell by Joseph Heath and Andrew Potter (sold in the United States as Nation of Rebels) changed my life. I was into counterculture, "culture jamming," anti-advertising, that kind of stuff, and this book made me seriously reconsider all of it. I now understand that trying to be unique is futile in a world of seven billion, and I should just try to be a good person and do good for the world (hence working on fusion!) Potter’s follow-up The Authenticity Hoax, explores the search for authenticity in more detail, but it’s not nearly as good of a book as Rebel Sell.

Nathan Howard: I first became interested in physics by reading about astrophysics. I was specifically interested in black holes and so one of the first books I read (after some of the popular books by Hawking which are written for general audiences, e.g. A Brief History of Time) was a book by Kip S. Thorne called Black Holes and Time Warps. I really enjoyed this book. It did not require much technical background, just some basic mathematics, and it gave good explanations of black holes, relativity, and gravitational waves.

16. Why is fusion more useful than exploiting thorium?
by gestalt_n_pepper

I understand that in the long term, we would want fusion. But we face increasing energy problems over the next 50 years and severe energy problems before 2100. Wouldn't it make sense to allocate research and development resources to something that we know works?

MIT Researchers: First of all, fusion will be putting watts on the grid before 2100. It’s not going to be tomorrow, but it’s not going to be a hundred years, either.

We know how to build thorium fission reactors. It's been done. They have none of the major attractions of a fusion reactor in terms of safety, fuel resources, reduced waste, or non-proliferation. Worldwide thorium fuel resources are about the same as those of uranium. Thorium reactors might become part of the commercial fission reactor mix in the future, but they don't offer transformative possibilities for nuclear power the way fusion does.

That said, we think that the that the scale of the energy/climate problem demands that we (meaning: government and private industry where appropriate) pursue multiple lines of development into new energy sources. Obviously nobody wants to waste taxpayer money, so all proposals have to be evaluated for chance of success – but today, it’s limited by funding more than by a lack of good ideas. This shouldn’t be the case.

The key thing we want to get across is that it shouldn’t be a contest between “fund fusion” or “fund thorium research”. Fusion is extremely important for humankind and should be funded – if thorium fission also has promise, it should be funded too.

17. How is fusion power harnessed?
by circletimessquare

The talk is always about reaching break-even with fusion. What about capturing the power? Are we generating heat that will drive steam turbines? What schemes exist for capture and harnessing the power generated by fusion?

MIT Researchers: In a magnetic fusion reactor, each deuterium-tritium fusion produces a 3.5 MeV (mega- electronvolt) alpha particle (helium nucleus) which deposits its energy in the plasma (this self-heating is how you can have an ‘ignited’ plasma which doesn’t require much or any external heating), and a 14.1 MeV neutron, which deposits its energy in a thick lithium blanket surrounding the toroidal reaction chamber. But in the end, all of it comes out as heat!

For a conservative fusion reactor design, this heat would be removed by a primary cooling loop (high-pressure steam or some sort of liquid metal) which would give the heat to a secondary steam loop (Rankine cycle) in a heat exchanger (steam generator). The steam would then turn a turbine, producing electricity, just like in a fission or coal power plant.

Of course, with a thermal process like a steam cycle, one is always limited by the Carnot efficiency, which increases as the temperature of the high-temperature reservoir goes up. So there are also designs to use a very high-temperature (800–1000 C) gas cooling loop and a Brayton cycle.

But the short answer is: the alpha power is captured by the plasma, and the neutron power is captured by the blanket. It all comes out as heat, which is used to heat a working fluid, which turns a turbine, producing electricity. This is not expected to be a technological problem – the challenge is in getting a confined thermonuclear plasma to produce the fusion energy in the first place!

19. Fusion Milestone Prizes?
by Baldrson

In 1992, with the assistance of fusion technologists such as Robert W. Bussard, I developed legislative language for a series of 12 milestones, each of which would be awarded a $(1992)100M prize for the achievement of objectives toward the attainment of practical fusion energy. This legislation also provided a grace period during which scientists and technologists that had been working on the US fusion program would be provided full salaries, without obligation, during which time they could seek support for their ideas to achieve these milestones. This legislation presaged a number of other prizes including the X-Prize and BAFAR / CATS prize. In 1995, Robert W. Bussard submitted this legislation to all relevant Congressional committees, copying all US plasma physics laboratories. Needless to say, the legislation wasn't passed. Do you think the time is right?

MIT Researchers: We think that the current approach, in which government-funded labs are not in direct competition, but have to justify their funding to the agency (in our case, the DOE), is the best option for the moment. Perhaps the X-PRIZE approach might work for the alternative concepts? (see our answer below regarding Polywell/Dense Plasma Focus/ IEC etc.)

20. ITER
by MpVpRb

Is the ITER project good science? Or is it a politically-motivated, pork-laden boondoggle?

MIT Researchers: ITER is absolutely good science. Governments representing over half the population of the world are backing the project because it is the logical next step – a prototype reactor that will produce ten times more fusion energy than heating power put in, for a few minutes at a time. It is also pushing forward the development of fusion reactor technology (materials, control systems, remote handling systems, etc.). The U.S. fusion community endorsed ITER as the best option for a next-step experiment at the Snowmass II conference in 2002 (see proceedings here).

All of that said, the cost of ITER has risen substantially from the original estimates, and because overall magnetic fusion funding has remained nearly flat in the United States, the U.S. contribution to ITER is threatening to swallow up the entire domestic program. This is starting with the planned closure of Alcator C-Mod in September 2012, but unless more money is allocated to fusion research, all three U.S. tokamak facilities are at risk in the next few years.

Graduate students at Alcator C-Mod have put together a web page explaining the problem: http://www.fusionfuture.org/faq/the-fusion-budget-problem/ and we urge you to go to this website and click the link to contact your member of Congress and urge them to fully fund a strong domestic program and the U.S. contribution to ITER!

21. NIF
by Grond

Is the NIF approach even plausibly capable of generating electricity in a useful way? Or is it purely a research platform / smokescreen for nuclear weapons research?

MIT Researchers: The primary mission of the National Ignition Facility (NIF) is "stockpile stewardship." That is, to ensure that U.S. nuclear weapons continue to be a credible deterrent. This is why NIF is funded by the National Nuclear Security Agency (the agency in charge of the nation’s nuclear stockpile), not the DOE Fusion Energy Sciences program. Thus, the weapons research mission of NIF is not a smokescreen, but is actually the publicly acknowledged primary objective for the facility.

Some researchers at NIF believe that their inertial fusion approach can be used for an energy source as well. We don’t want to speculate here on the plausibility of the LIFE (Laser Inertial Fusion Energy) concept. There is a National Academy of Science review of the prospects of inertial fusion energy under way right now; the final report is expected to be published before the end of this year.

18. Dense Plasma Focus
by mbradmoody
Do you see any merit in the "dense plasma focus" approach to commercial fusion power production, specifically the work of the Lawrenceville Plasma Physics group?
22. Focus Fusion / aneutronic fusion?
by mwk88
Focus Fusion Society is posting research on their project to do aneutronic (e.g. Proton Boron (pB11)) fusion. The concept sounds great, and as an engineer, I find several parts of their design, such as direct extraction of electric power, to be elegant. Is this credible research or pie-in-the-sky? I have not seen much mention of them in mainstream fusion research.
23. Polywell Fusion
by mknewman
What do you think of the efforts at EMC2 Fusion and Polywell Fusion? They seem to be making real, measurable, and open results, but the mainstream physics community seems to ignore this progress.
24. What’s wrong with IECs / Fusor?
by claytongulick
Why aren't IEC reactors based on Farnsworth's designs taken more seriously? From what I understand, IECs have been more effective at producing fusion, and they are cheap to build. People even build them in the garage. From everything I've read, no one really takes the "fusor" seriously in the fusion science realm, and it's considered a dead line of inquiry. I've never understood why.

MIT Researchers: These four questions (18, 22–24) are answered together here.

None of us are experts on inertial electrostatic confinement, magnetized target fusion / dense plasma focus, or Polywells, and so we don’t want to say too much about the specifics of those designs. We can say the following:

1. The amount of money that is being spent, especially in the United States, on fusion is far lower than the field deserves, given its track record and potential. This sounds self-serving, but we think it’s justifiable based on the facts. The graph we posted above shows how the fusion budget is far lower today than it was thirty years ago, even as we continue to make steady progress toward a reactor and the seriousness of the coupled energy/climate problem becomes more obvious.

The alternate confinement concepts program has also seen cuts. (“Alternative” in DOE Fusion Energy Sciences parlance means, basically, anything that isn’t tokamaks, stellarators, or laser [inertial] fusion.) The Levitated Dipole Experiment, an innovative magnetic-confinement arrangement based on planetary magnetic fields, was cancelled just as they were about to add significant auxiliary heating for the first time. And these small-scale alternative confinement projects are not very expensive! Some of these alternative concepts may very well be promising and deserve taxpayer money to be developed.

2. But on the other hand, these groups need to show that they deserve funding. It’s not enough to just tease these promising results and be secretive about the methods or technologies. Public funding can only come when the details are published in the open literature, and subjected to the scrutiny of peer review and the wider community reading the papers. The (hot) fusion community is still living with the aftermath of the cold fusion scandal from a quarter century ago - so it’s very important for the proponents of these alternate concepts to push the researchers to publish their results in peer-reviewed journals. Whatever negatives the tokamak might have, one thing you can’t say about it is that the research has been too secretive, and this has allowed the funding agencies to make the judgement that the tokamak is currently the most promising route to a fusion reactor, which is why this line of research gets the most money.

Special thanks to Dr. Martin Greenwald, Prof. Ian Hutchinson, Asst. Prof. Anne White, Prof. Dennis Whyte, Nathan Howard, and Geoff Olynyk for taking the time to answer our questions.

Amazon's Kindle Fire has been out long enough to build up a hefty stock of returned units; reader DeviceGuru writes "If you're quick, you might be able to snag a refurbished unit for $139 at Amazon. The company introduced the Fire at the end of 2011 at the loss-leader price point of $199, though it's rumored to cost around $210 to build. So at $139, you'd be getting the Android-powered tablet well below cost. Step one: buy refurbed Kindle Fire. Step two: root it and enjoy!" For this price, I'd be out trying to hog a few of these, if they had GPS and at least one camera. Update: 03/29 19:37 GMT by T : Reader Eldavojohn points out that this was a short-lived opportunity, now past.

stoolpigeon writes "HTML5 is the latest version of HTML. In fact, it is still under development — but HTML5 brings so many highly-desired capabilities that browsers have begun to implement it and many projects already take advantage of it. Often an HTML5 project employs more technology than just HTML, and the label has come to include the use of CSS3 and JavaScript as well. There are a number of resources out there to help one use HTML5 and recently I've been using the HTML5 Developer's Cookbook by Chuck Hudson and Tom Leadbetter." Read on for the rest of stoolpigeon's review. HTML5 Developer's Cookbook author Chuck Hudson, Tom Leadbetter pages 480 publisher Addison-Wesley Professional rating 9/10 reviewer stoolpigeon ISBN 978-0-321-76938-1 summary HTML5 Developer's Cookbook I like the cookbook format myself in situations like this. I'm already familiar with HTML but I want to learn about the new features that exist in HTML5. This means I'm not nearly as interested in explanations, especially in the basics, as I am in getting a big diff on the languages with lots of examples and only as much explanation as necessary. Though the trick for authors is to walk the fine line between too much explanation and not enough. If they get too wordy, it really isn't a cook book any more. Not enough explanation and it can become difficult to understand all the issues that come to bear with an example. This is especially true when dealing with something that is new and still in development.

HTM5 Developer's Cookbook walks this line well. Hudson and Leadbetter have organized the recipes into various categories and further labeled them with a level of difficulty. Recipes are marked as beginner, intermediate and advanced. I found the labels helpful because while I've mucked about with HTML and its corresponding tech, I felt more comfortable easing in on the beginner end first. If I were working with someone who was a true beginner to working with any kind of development, I would probably not start them off with a cook-book. I think that is especially the case here because so much of HTML is not covered. This is not an exhaustive resource on HTML but rather a set of explanations and examples on what is new or different in this latest version of HTML.

The book itself begins with a quick review of how we got to where we are, a bit of HTML history. The chapters follow this pattern, starting with some history where needed and an explanation of the new technology driving the examples that are to follow. Then there are the recipes themselves, followed up by any helpful information and a summary. There's more prose than I've seen in many other cook-books but in this case I didn't see it as a negative. The authors assume that readers are familiar with the old approach and they need to explain how the new approach is different. In some cases tags have changed meaning, this needs to be spelled out.

Hudson and Leadbetter deal with handling how various browsers support (or don't) the various aspects of HTML5 that they highlight. This is especially important as everything is still in flux. Though if past history is any indicator, even if the spec were completely nailed down, there would still be differences between browsers. This does bring up an important question though. This book has a definite shelf life. As HTML5 continues to develop there are many parts that may become inaccurate. This is true of most tech books, but doubly so in this case. If someone is looking for a timeless tome on the topic, this wouldn't be it. In my case, it's a timely resource to get up to speed quickly, from a single source that I trust. I can search the web and find a mixed bag or turn to this one spot to get quickly up to speed.

I had an electronic version of the book made available from the publisher for this review. I've found that format to be very helpful in this case. It keeps me from feeling at all guilty about buying a book with such a narrow window of usefulness. I also really enjoy being able to jump straight to recipes. There is a list of just the recipes at the end of the book that are linked directly to each that make this especially easy. I'm rapidly moving away from dead tree books, and I didn't feel any reason here to miss that format. (On a side note, I got the page count above from Amazon. I wonder what metric we'll be using to judge book size in the future? Word count?)

All of the chapter titles and recipes are available on line. From new structural elements to integrating with devices, there are plenty of practical and useful examples. I couldn't find a clear statement in the text of the book on readers being given the freedom to use the recipes directly in code. This surprised me so I checked with the publisher and they told me that all code is free to use. Maybe that is not necessary here because everything shown is just an example of following the specification, but given the current climate with regards to intellectual property I wanted to be sure.

I've rated the book 9 out of 10 due to the fact that I think the authors do a great job of not wasting my time but instead quickly deliver what I need. If you want to get a feel for what is up with HTML5 yourself, I recommend this as a great option. If you are interested in a more comprehensive review of HTML in general or how to create web pages, I would find something more suited to providing an introduction to web programming.

You can purchase HTML5 Developer's Cookbook from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

benrothke writes "The Chicago Manual of Style (CMS), now in its 16th edition, is the de facto style guide for American writers. It deals with aspects of editorial practice, grammar, usage, document preparation and more. It's just one of many style guides for writers. The Microsoft Manual of Style, just released in its 4th edition, attempts to do for the technical writers what the CMS has done for journalists and other writers." Read below for the rest of Ben's review. Microsoft Manual of Style author Microsoft Corporation pages 464 publisher Microsoft Press; rating 10/10 reviewer Ben Rothke ISBN 978-0735648715 summary Invaluable guide to becoming a better technical writer A style guide or style manual is a set of standards for the writing and design of documents, either for general use or for a specific publication, organization or field. The implementation of a style guide provides uniformity in style and formatting of a document. There are hundreds of different style guides available — from the The Elements of Style by Strunk and White, to the Associated Press Stylebook and Briefing on Media Law and many more.

Microsoft's goal in creating this style manual is about standardizing, clarifying and simplifying the creation of content by providing the latest usage guidelines that apply across the genres of technical communications. The manual has over 1,000 items, so that each author does not have to make the same 1,000 decisions.

Anyone who has read Microsoft documentation knows it has a consistent look, feel and consistency; be it a manual for Visual C#, Forefront or Excel. With that, the Microsoft Manual of Style is an invaluable guide to anyone who wants to better the documentation they write.

For example, many writers incorrectly use words such as less, fewer, and under as synonymous terms. The manual notes that one should use less to refer to a mass amount, value or degree; fewer to refer to a countable measure of items, and not to use under to refer to a quantity or number.

Style guides by their very nature of highly subjective and no one is forced to take accept the Microsoft style as dogma. The authors themselves (note that the book was authored by a group of senior editors and content managers at Microsoft, not a single individual) note that they don't presume to say that the Microsoft way is the only way to write. Rather it is the guidance that they follow and are sharing it with the hope that the decisions they have made for their content professionals will help others promote consistency, clarity and accuracy. With that, they certainly have achieved that goal.

The book is made up of two parts; with part 1 comprised of 11 chapters on general topics.

Chapter 1 is about Microsoft style and voice and has basic suggestions around consistency, precision, sentence structure and more. The chapter also has interesting suggestions on writing bias-free text. It notes that writers should do their best to eliminate bias and to depict diverse individuals from all walks of life in their documentation. It's suggested to avoid terms that may show bias with regards to gender, race, culture, ability, age and more. Some examples are to avoid terms such as chairman, salesman and manpower; and use instead moderator, sales representative or workforce.

The manual also notes that writers should attempt not to stereotype people with disabilities with negative connotations. It suggests that documentation should positively portray people with disabilities. It emphasizes that documentation should not equate people with their disability and to use terms that refer to physical disabilities as nouns, rather than adjectives.

The book takes on a global focus and notes that since Microsoft sells its products and services worldwide, content must be suitable for a worldwide audience. For those writing for a global audience, those sections of the manual should be duly considered.

The manual also cautions authors to avoid too many technical terms and jargon. The danger of inappropriate use of technical terms is that people who don't think of themselves as computer professionals consider technical terms to be a major stumbling block to understanding. The manual suggests whenever possible, to use common English words to get the point across, rather than technical one.

The book provides thousands of suggestions on how to write better documentation, including:
do not use hand signs in documentation — nearly every hand sign is offensive somewhere
do not refer to seasons unless you have no other choice – since summer in the northern hemisphere is winter in the southern hemisphere
spell out names of months – as 3/11/2012 can refer to March 11, 2012 in some places and November 3, 2012 in others
use titles, not honorifics, to describe words such as Mr. or Ms. – not all cultures have an equivalent to some that are common in the United States, such as Ms.

Chapter 6 is on procedures and technical content, and explains that consistent formatting of procedures and other technical content helps users find important information quickly and effectively. In the section on security, the style guide notes not to make statements that convey the impression or promise of absolute security. Instead, the writer should focus on technologies or features that help achieve security; and suggests to be careful when using words such as safe, private, secure, protect,and their synonyms or derivatives. It is best to use qualifiers such as helps or can help with these words.

As noted earlier, the style guide is simply a guide, not an absolute. In the book Eats, Shoots & Leaves: The Zero Tolerance Approach to Punctuation, author Lynne Truss write of terms that are grammatically incorrect, but so embedded into the language, that they are what she terms a lost cause. With that, the style guide has the pervasive use of the term all right, as opposed to alright.

According to dictionary.com, although alright is a common spelling in written dialogue and in other types of informal writing, all right is used in more formal, edited writing. My own preference is that alright is clearer and ultimately more concise. In this guide, I found that Microsoft's preference for all right to be distracting.

Differences aside, part 1 provides vital assistance to any writer that is interested in writing effective content that educates the reader in the clearest manner possible. The book is the collective experience of thousands of writers and their myriad sets of documentation. The book provides page after pages of unique information.

Part 2 is a usage dictionary that is a literal A-Z of technical terms, common words and phrases. The goal of the usage dictionary is to give the reader a predictable experience with the content and to ensure different writers usage a standard usage of the same term. Some interesting suggestions in the usage dictionary are:

access rights – an obsolete term. Use user rights
collaborator – do not use collaborator to describe a worker in a collaborative environment unless you have no other choice as it is a sensitive term in some countries. Specifically, being a collaborator in a third-world country can get one killed.
email – do not use as a verb. Use send instead.
master / slave – do not use as the terminology, although standard in the IT industry, may be insulting to some users. The manual notes that its use is prohibited in a US municipality.
press – differentiate between the terms press, type, enter, and use, and to use press, not depress, hit or strike when pressing a key on the keyboard

Some of the terms suggested are certainly Microsoft centric, such as:
blue screen – they suggest not to use blue screen, either as a noun or a verb to refer to an operating system failure. Use stop or stop error instead
IE – never abbreviate Internet Explorer; always use the full name

Say what you will about Microsoft, but any technical writer who is serious about being a better writer can learn a lot from the writers at Microsoft. Microsoft is serious and passionate about documentation and it is manifest in this style guide.

Microsoft has been criticized for their somewhat lukewarm embrace of open source. With the Microsoft Manual of Style, Microsoft is nearly freely sharing a huge amount of their intellectual capital. At $29 for the paperback and $10 for the Kindle edition, the manual has a windfall of valuable information at a bargain-basement of a price.

This guide is a comprehensive manual for the serious writer of technical documentation, be it a high school student or veteran author. In fact, to describe the guide as comprehensive may be an understatement, as it details nearly every facet of technical writing, including arcane verb uses.

Many authors simply write in an ad-hoc manner. This manual shows that effective writing is a discipline. The more disciplined the writer, the more consistent and better their output. Anyone that wants to be a better writer will undoubtedly find the Microsoft Manual of Style an exceptionally valuable resource.

Ben Rothke is the author of Computer Security: 20 Things Every Employee Should Know.

You can purchase Microsoft Manual of Style from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

benrothke writes "The Chicago Manual of Style (CMS), now in its 16th edition, is the de facto style guide for American writers. It deals with aspects of editorial practice, grammar, usage, document preparation and more. It's just one of many style guides for writers. The Microsoft Manual of Style, just released in its 4th edition, attempts to do for the technical writers what the CMS has done for journalists and other writers." Read below for the rest of Ben's review. Microsoft Manual of Style author Microsoft Corporation pages 464 publisher Microsoft Press; rating 10/10 reviewer Ben Rothke ISBN 978-0735648715 summary Invaluable guide to becoming a better technical writer A style guide or style manual is a set of standards for the writing and design of documents, either for general use or for a specific publication, organization or field. The implementation of a style guide provides uniformity in style and formatting of a document. There are hundreds of different style guides available — from the The Elements of Style by Strunk and White, to the Associated Press Stylebook and Briefing on Media Law and many more.

Microsoft's goal in creating this style manual is about standardizing, clarifying and simplifying the creation of content by providing the latest usage guidelines that apply across the genres of technical communications. The manual has over 1,000 items, so that each author does not have to make the same 1,000 decisions.

Anyone who has read Microsoft documentation knows it has a consistent look, feel and consistency; be it a manual for Visual C#, Forefront or Excel. With that, the Microsoft Manual of Style is an invaluable guide to anyone who wants to better the documentation they write.

For example, many writers incorrectly use words such as less, fewer, and under as synonymous terms. The manual notes that one should use less to refer to a mass amount, value or degree; fewer to refer to a countable measure of items, and not to use under to refer to a quantity or number.

Style guides by their very nature of highly subjective and no one is forced to take accept the Microsoft style as dogma. The authors themselves (note that the book was authored by a group of senior editors and content managers at Microsoft, not a single individual) note that they don't presume to say that the Microsoft way is the only way to write. Rather it is the guidance that they follow and are sharing it with the hope that the decisions they have made for their content professionals will help others promote consistency, clarity and accuracy. With that, they certainly have achieved that goal.

The book is made up of two parts; with part 1 comprised of 11 chapters on general topics.

Chapter 1 is about Microsoft style and voice and has basic suggestions around consistency, precision, sentence structure and more. The chapter also has interesting suggestions on writing bias-free text. It notes that writers should do their best to eliminate bias and to depict diverse individuals from all walks of life in their documentation. It's suggested to avoid terms that may show bias with regards to gender, race, culture, ability, age and more. Some examples are to avoid terms such as chairman, salesman and manpower; and use instead moderator, sales representative or workforce.

The manual also notes that writers should attempt not to stereotype people with disabilities with negative connotations. It suggests that documentation should positively portray people with disabilities. It emphasizes that documentation should not equate people with their disability and to use terms that refer to physical disabilities as nouns, rather than adjectives.

The book takes on a global focus and notes that since Microsoft sells its products and services worldwide, content must be suitable for a worldwide audience. For those writing for a global audience, those sections of the manual should be duly considered.

The manual also cautions authors to avoid too many technical terms and jargon. The danger of inappropriate use of technical terms is that people who don't think of themselves as computer professionals consider technical terms to be a major stumbling block to understanding. The manual suggests whenever possible, to use common English words to get the point across, rather than technical one.

The book provides thousands of suggestions on how to write better documentation, including:
do not use hand signs in documentation — nearly every hand sign is offensive somewhere
do not refer to seasons unless you have no other choice – since summer in the northern hemisphere is winter in the southern hemisphere
spell out names of months – as 3/11/2012 can refer to March 11, 2012 in some places and November 3, 2012 in others
use titles, not honorifics, to describe words such as Mr. or Ms. – not all cultures have an equivalent to some that are common in the United States, such as Ms.

Chapter 6 is on procedures and technical content, and explains that consistent formatting of procedures and other technical content helps users find important information quickly and effectively. In the section on security, the style guide notes not to make statements that convey the impression or promise of absolute security. Instead, the writer should focus on technologies or features that help achieve security; and suggests to be careful when using words such as safe, private, secure, protect,and their synonyms or derivatives. It is best to use qualifiers such as helps or can help with these words.

As noted earlier, the style guide is simply a guide, not an absolute. In the book Eats, Shoots & Leaves: The Zero Tolerance Approach to Punctuation, author Lynne Truss write of terms that are grammatically incorrect, but so embedded into the language, that they are what she terms a lost cause. With that, the style guide has the pervasive use of the term all right, as opposed to alright.

According to dictionary.com, although alright is a common spelling in written dialogue and in other types of informal writing, all right is used in more formal, edited writing. My own preference is that alright is clearer and ultimately more concise. In this guide, I found that Microsoft's preference for all right to be distracting.

Differences aside, part 1 provides vital assistance to any writer that is interested in writing effective content that educates the reader in the clearest manner possible. The book is the collective experience of thousands of writers and their myriad sets of documentation. The book provides page after pages of unique information.

Part 2 is a usage dictionary that is a literal A-Z of technical terms, common words and phrases. The goal of the usage dictionary is to give the reader a predictable experience with the content and to ensure different writers usage a standard usage of the same term. Some interesting suggestions in the usage dictionary are:

access rights – an obsolete term. Use user rights
collaborator – do not use collaborator to describe a worker in a collaborative environment unless you have no other choice as it is a sensitive term in some countries. Specifically, being a collaborator in a third-world country can get one killed.
email – do not use as a verb. Use send instead.
master / slave – do not use as the terminology, although standard in the IT industry, may be insulting to some users. The manual notes that its use is prohibited in a US municipality.
press – differentiate between the terms press, type, enter, and use, and to use press, not depress, hit or strike when pressing a key on the keyboard

Some of the terms suggested are certainly Microsoft centric, such as:
blue screen – they suggest not to use blue screen, either as a noun or a verb to refer to an operating system failure. Use stop or stop error instead
IE – never abbreviate Internet Explorer; always use the full name

Say what you will about Microsoft, but any technical writer who is serious about being a better writer can learn a lot from the writers at Microsoft. Microsoft is serious and passionate about documentation and it is manifest in this style guide.

Microsoft has been criticized for their somewhat lukewarm embrace of open source. With the Microsoft Manual of Style, Microsoft is nearly freely sharing a huge amount of their intellectual capital. At $29 for the paperback and $10 for the Kindle edition, the manual has a windfall of valuable information at a bargain-basement of a price.

This guide is a comprehensive manual for the serious writer of technical documentation, be it a high school student or veteran author. In fact, to describe the guide as comprehensive may be an understatement, as it details nearly every facet of technical writing, including arcane verb uses.

Many authors simply write in an ad-hoc manner. This manual shows that effective writing is a discipline. The more disciplined the writer, the more consistent and better their output. Anyone that wants to be a better writer will undoubtedly find the Microsoft Manual of Style an exceptionally valuable resource.

Ben Rothke is the author of Computer Security: 20 Things Every Employee Should Know.

You can purchase Microsoft Manual of Style from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

An anonymous reader writes "Today Amazon announced that a science fiction writer has become the Kindle's all-time best-selling author. Last June Suzanne Collins, who wrote the Hunger Games trilogy, was only the fourth author to sell one million ebooks, but this month Amazon announced she'd overtaken all her competition (and she also wrote the #1 and #2 best-selling ebooks this Christmas). In fact, 29 of the 100 most-highlighted passages on the Kindle were written by Collins, including 7 of the top 10. And on a separate list of recent highlights, Collins has written 17 of the top 20 most-highlighted passages." It's pretty interesting to go through the top-100 list and look at the passages people think are worth highlighting. Taken out of context, many of them could be patched together and re-sold as a self-help book. None are quite so eloquent as #18 in the recent highlights.

An anonymous reader writes "Today Amazon announced that a science fiction writer has become the Kindle's all-time best-selling author. Last June Suzanne Collins, who wrote the Hunger Games trilogy, was only the fourth author to sell one million ebooks, but this month Amazon announced she'd overtaken all her competition (and she also wrote the #1 and #2 best-selling ebooks this Christmas). In fact, 29 of the 100 most-highlighted passages on the Kindle were written by Collins, including 7 of the top 10. And on a separate list of recent highlights, Collins has written 17 of the top 20 most-highlighted passages." It's pretty interesting to go through the top-100 list and look at the passages people think are worth highlighting. Taken out of context, many of them could be patched together and re-sold as a self-help book. None are quite so eloquent as #18 in the recent highlights.

Michael J. Ross writes "Prior to Google+, the company's previous attempts at social networking — Orkut, Dodgeball, Jaiku, Wave, and Buzz — were largely failures, and tended to frustrate users who had devoted time and effort to contributing content and establishing connections with other users, only to see the services wither on the vine. In contrast, Google+ appears to be receiving far more nurturing by the Internet behemoth, and as a result has arguably better chances of not just surviving, but expanding to the point of eventually challenging Twitter and Facebook. Like its rivals, Google+ offers online help information to explain to newcomers the basics of how to use the service. But there is little to no advice on how to make the most of its capabilities, and even the basic functionality is not always clearly explained. That is the purpose of a new book, Google+: The Missing Manual." Keep reading for the rest of Michael's review. Google+: The Missing Manual author Kevin Purdy pages 232 pages publisher O'Reilly Media rating 7/10 reviewer Michael J. Ross ISBN 978-1449311872 summary An introduction to Google's social networking service. Authored by Kevin Purdy, the book was published by O'Reilly Media, on 30 December 2011, under the ISBN 978-1449311872. The publisher's page has a brief description of the book, its table of contents, some comments on the book from customers and reviewers, a couple errata (as of this writing), and links for purchasing the print version (such as the one kindly provided to me by the publisher) and/or the e-book versions (in EPUB, MOBI, and PDF formats). The "missing CD" page has links to most if not all of the online resources mentioned in the text.

Like the other entries in the Missing Manual series, this one starts with the basics, and builds upon that foundation. It does not assume any knowledge of Google+, or even possession of a Google account.

The book's material is organized into nine chapters, for a total of 232 pages. The first chapter, "Getting Started," explains exactly how to join Google+, invite friends to your new network, and configure your profile, including your privacy settings and a photo (even tweaking it online). The second chapter, "Managing Contacts with Circles" covers how to create new circles, edit and organize existing ones, share them with other Google+ users, and find people to add to your circles. But, oddly, the information is not presented in that logical order. The author explicates the advantages of using more than the default four circles provided by Google. Some points are repeated, but briefly enough that it is inconsequential.

While the first two chapters lay the foundation for joining Google+ and setting up your account and circles, the next three chapters explore the details of using this service — starting with "Streams, Sharing, and Privacy," which explains the various types of streams (main, circle, Notification, and the now-defunct Incoming stream), as well as the user interface elements for those streams and the individual posts they comprise. The author also demonstrates how to write your own posts, specify who gets to see them, edit your posts, and interact with the posts submitted by other users. The next chapter explores the important topic of notifications, which are sent as e-mail messages, smartphone messages, etc. Helpfully, the author discusses the differences between the user interfaces of the Android and iPhone notification apps. The subsequent chapter fully explains how to share photos and videos with other Google+ users, as well as how to upload and perform basic editing of images. However, it may have been more logical to present the latter information before the former.

For people who want the capabilities previously only provided by commercial web conferencing services, hangouts might be the most welcome feature of Google+. Chapter 6 explains how to set up and participate in these videos/audio meetings online, as well as how to incorporate Google Chat, YouTube videos, and Android devices. The subsequent chapter, "Searching and Sparks," has plenty of advice on how to search for other Google+ users and the content they contribute. The penultimate chapter dives into the differences you may encounter when using Google+ on small screen devices — specifically, Android and Apple smartphones and tablets. The last chapter, which is the briefest of the bunch, is also likely to prove the least useful to most readers, as it covers how to get started playing the games built into Google+.

The book does not cover Google+ Pages, which was likely introduced after the final draft of the book was submitted to the publisher. Readers are directed to an untitled 14-page PDF file that covers the essentials of Google+ Pages. Oddly, the publisher's page links to that file with the text "Download Example Code"; but there is no example code for this book. The supplement contains a few flaws: "box pop-up box" (page 4), "using a promoting your Page" (9), and "his her name" (11).

Speaking of which, given the relatively modest number of pages in this book, and the limited amount of text on each one, this book contains far too many errata: "works different" (page xiii; echoes of Apple's infernal "Think Different" marketing campaign?), "If typing web addresses by hand that isn't" (page 3), "a different a social networking site" (4), "she's added you [to] her" (54), "added to [the] +Add box" (58), "even if [you] just" (79), "and the[n] click the" (79), "settings that lets you can choose" (83), "modicum [of] more fuss" (105), "share its photos [with] specific circles" (117), "where [the] photo" (124), "just like [the] lightbox view" (126), "and or" (147; should read "and/or"), "an job" (148), "how to [use?] Google+ running" (169), "search find" (170), "bring up to the same list" (180), "The form exact" (185; should read "The exact form"), "you can't get start" (191), "in in" (193), and "a box let you know" (194).

Some of the statements in the narrative are odd — for instance, "Halloween right around October 31" (page 7; when else would Halloween occur?). Other phrases are poorly worded — for instance, "whenever you feel irked or like something must be broken" (44), "maybe an extra like a link" (60), and "select an item from the menu that appears to see only circle-related notifications" (80). Lastly, at least one pair of verbs have inconsistent form ("start" and "mentioning" on page 62). All of these blemishes should have been caught by the copyediting crew. But for the most part, the narrative is straightforward. It is occasionally livened up with a bit of humor, which is good, because portions of the text begin to sound the same, as a result not so much of the author's writing, but more the Google+ interface itself.

Only a few technical errors are immediately evident — for instance, on page 61, the author refers to a for-loop in computer code incorrectly: "+1 is a common way of making a program run over and over again." But it is not a program that is being repeated, but rather a code block.

Scattered throughout the text are numerous text boxes — most of which are labeled "Note" or "Tip." Unfortunately, they are set in a font that is a bit too small for comfortable reading. Also, there does not appear to be any difference among these types of information sections, yet there are at least half a dozen different names for them.

All of the key topics are nicely illustrated with sample screenshots, in grayscale, oftentimes with relevant controls circled or otherwise indicated. The only weakness is that the author typically does not mention which figure is being referenced in the text — not that that would help much anyway, since none of them have figure numbers. It's usually clear from the context, but not always.

Yet the very existence of this book may give readers some pause: If a book of this size is required to explain how to use a social networking service aimed at the general public, perhaps the Google+ user interface needs to be overhauled and made more intuitive? Yet that process is probably underway, because Google+ is under constant revision. Thus there will be portions of the text and screenshots that differs somewhat from the current incarnation of the user interface and its features. But for most of these instances, it is easy enough to determine how what you read in the book correlates with what you might see on the screen.

The primary weakness of this book is that it does not attempt to explain how Google+ might be integrated into a business's online marketing strategy, nor how it compares against Facebook or Twitter in terms of its advantages and disadvantages. In fact, as noted above, the book addresses Google+ Pages only in a supplementary document. Such information would have made this entry in the Missing Manual series far more valuable.

However, one forte of this book is that the author has clearly put effort into learning and explaining the privacy implications of the various Google+ features — critical in this era of evaporating privacy and data breaches on an unprecedented scale.

On balance, he largely achieves his objective. Google+: The Missing Manual is an informative and approachable introduction to Google's social network.

Michael J. Ross is a freelance web developer and writer.

You can purchase Google+: The Missing Manual from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

jsuda writes "For those billions of people for whom the current political-economic system doesn't work–the Occupy Wall Street people, the Tea Partiers, the 99%-ers and have-nots, the middle and lower classes, and the rest of the unwashed masses, Occupy World Street is a starburst of enlightenment and a practical vision of hope for a new and advanced society." Read on for jsuda's review Occupy World Street: A Global Roadmap for Radical Economic and Political Reform author Ross Jackson pages 336 publisher Chelsea Green Publishing rating 9/10 reviewer jsuda ISBN 1603583882 summary shows how a handful of small nations could take on a leadership role; create new alliances, new governance, and new global institutions; and, in cooperation with grassroots activists, pave the way for other nations to follow suit. The book is subtitled appropriately "A Global Roadmap for Radical Economic and Political Order." It functions in a substantial way as the missing "content" for the Occupy Wall Street movement people who know that global capitalism and its political elite are screwing the middle and lower classes and the world environment but don't know exactly how they are doing it and how to change things. The book provides an unusually lucid analysis of the American political-economic system which should make clear to the Tea Partiers what their real targets of rage should be (it's not merely the Democrats nor the federal government.) Nearly everyone else who wants a "big picture" comprehensive analysis of the global economic system will be educated by this book.

The author, Ross Jackson, identifies who and what is responsible for the 2008 financial meltdown and many other problems in society. Most prominent are a seriously-flawed "neo-liberal economic philosophy" and the political-elite class which sponsors that philosophy for self-interested reasons at the expense of the rest of us. Jackson makes clear that economic philosophical theory is not value free and is class politics in disguise. But way more importantly than the mere class versus class struggle, the neo-liberal economic philosophy has created severe energy and environmental problems which are almost certain to lead soon to major economic and political disruptions affecting the entire globe.

The author's main perspective is as an environmentalist; he utilizes a systems approach of an overarching environmental model where the global environment is a closed, finite system and the economic, political, and other topics are subsystems of the whole. The book explains (in six parts and 17 chapters) how and why our existing economic model is failing and will create environmental, economic, and political chaos unless it is replaced soon with an economic model emphasizing "sustainability" and "development" versus simple "unlimited growth." Jackson explains in the second half of the book what we can do about it, hopefully before it's too late for future generations to have a chance for civilized life.

I have never heard before of Mr.Jackson, but he is bound to be (or at least should be) hailed as a top-notch public intellectual. He is a brilliant analyst of global economics, politics, and environmental matters; and a clever synthesist of the relevant economics, politics, philosophy, environmental science, psychology, sociology, history, physics, and biology, which apply to his examination.

He has an unusually broad and diverse background as a global currency trader, executive of a nonprofit environmental organization, software designer and businessman, and degrees in engineering physics, industrial management, and operations research. This may explain, in part, his ability to see major categories of human life with such a wide lens while also being able to analyze the subcategories and the factual data.

Part One explains the scientific and economic reasons why the neo-liberal approach of unending growth is unsustainable and a lie. It is a lie because it implies, at least, that everyone has a chance ultimately to achieve the high level of consumption of the successful capitalists and that the high consumption gravy train will go on forever. He uses biological, environmental, and mathematical data to show that the neo-liberal assumption of infinite natural capital has already resulted in net deficits of global energy resources, and that the world (and the neo-liberal economic system) will end frightfully unless we reduce population, give up the idea of "more of everything is better," redesign and downsize our economies, use less fossil energies, and emphasize sustainability.

The next two parts explain the politics and human factors which drive the irrational economic policies. He goes into good detail about historical economic theory from the mercantile period, to the classical free trade period, to our existing neo-liberal period. He clearly explains how and why the 2008 financial crisis occurred and why it is likely to repeat itself, and how the current debt crisis in Europe (and elsewhere) happened and why the European Union is not equipped even now to successfully deal with it. Any effort to address it (using the existing neo-liberal strategies) will be temporary and the crises will deepen.

His discussions on the neo-liberal insistence on a deregulated economic environment, free flow of global capital, and the use of exotic financial instruments and transactions, especially naked short sales, are the clearest I've read about how these elements de-stabilized the global economy. They will continue to do so as long as those who (very lucratively) benefit from them (the political elite) insist upon them regardless of the consequences to hapless small nations and their economies, small businesses, and people like you and me. He thoroughly and lucidly explains how this political-economic philosophy destroys real democracy, including in America. What we have, he says, is a corporatocracy which dominates much of political and social life through the forces of wealth and ideology.

Mr. Jackson is also a political-economic visionary of the highest order as shown in the second half of the book by his "break away" strategy where he sets out his alternative environmentalist paradigm. It is a new worldview emphasizing the finite reality of our natural resources, especially energy ones, and how we should alter much of what we do to comply with that reality. He argues for a new set of social values harmonious with a holistic sense of people and nature being part of one "system." The values of that system include smallness, localization, quality versus quantity, interrelationships, and long-term perspectives.

These values are organized into a moderately sophisticated set of new global political and economic institutions modeled much like the European Union but emphasizing environmental issues and designed to satisfy long-term environmental needs. This process will also lead to enhancing of true human values in the political sphere, especially in more effective democracies.

The "breaking away" strategy starts with small nation states building a new economic paradigm based upon the environmental perspective, rejecting the flawed and elitist global institutions we have now (the WTO, World Bank, and the International Monetary Fund), and even developing new currency systems. The nation states will be supported by a grassroots activist movement which will create local eco-communities and more self-reliant economies while lobbying existing political powers to get on board with the new paradigm. The measurements of success will not be GNP or GDP but the broader-based measures of social happiness and human rights. (Take the case of the nation of Bhutan which measures its activity by a standard called "Gross National Happiness Index.")

The parts of the book explaining the roles of the neo-liberal economic philosophy and the political elite are solidly presented and not really new. The program of change he proposes, however, is new and intellectually sound. Being intellectually sound, however, is not sufficient to affect change. There is a gap, it seems, between the ideas and what is necessary to activate people at the grassroots level. Relatively few people in reality will even read this book. The ideas need to be connected to "street-level" understandings, perhaps tied to basic human values of respect and dignity. The roadmap proposed here, Mr. Jackson acknowledges, needs much more development.

You can purchase Occupy World Street: A Global Roadmap for Radical Economic and Political Reform from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

First time accepted submitter benrothke writes "It is said that the song Wipe Out launched a generation of drummers. In the world of information security, the classic Applied Cryptography: Protocols, Algorithms, and Source Code in C by Bruce Schneier may have been the book that launched a generation of new cryptographers. Schneier's latest work of art is Liars and Outliers: Enabling the Trust that Society Needs to Thrive. For those that are looking for a follow-up to Applied Cryptography, this it is not. In fact, it is hard to classify this as an information security title and in fact the book is marked for the current affairs/sociology section. Whatever section this book ultimately falls in, the reader will find that Schneier is one of the most original thinkers around." Keep reading for the rest of Ben's review. Liars and Outliers: Enabling the Trust that Society Needs to Thrive author Bruce Schneier pages 384 publisher Wiley rating 10/10 reviewer Ben Rothke ISBN 978-1118143308 summary Brilliant book on trust and society, and it complex interrelation In Applied Cryptography Schneier dealt with the pristine world of mathematical cryptography where aspects of pure mathematics could be demonstrably proven. For example, non-repudiation is absolutely provable.

In Liars and Outliers, Schneier moves from the pristine world of mathematics into the muddy world of human trust. Non-repudiation is no longer an absolute in a world where a Windows kernel can be compromised and end-users can be victims of social engineering.

The book addresses the fundamental question of how does society function when you cant trust everyone. Schneier notes that nothing in society works without trust. Its the foundation of communities, commerce, democracy, in truth — everything. And Schneier deals extensively with social and moral pressures that effect trust.

Liars and Outliers is very similar to books by Umberto Eco, that have a Renaissance feel to them; bringing myriad and diverse topics together. Schneier does this here and intertwines topics such as game theory, evolution, surveillance, existentialism and much more. Schneier's brilliance is that he is able to connect seemingly disparate dots around information security and society, and show how they are in truth tightly coupled.

In the book, Schneier makes note of those that don't follow the rules. He calls these people defectors, and these are the liars and outliers of the book. The book notes that everything is a trade-off, and these defectors are the ones that try to break the rules.

An overall theme of the book, in which Schneier touches and references sociology, psychology, economics, criminology, anthropology, game theory and much more, is that society can't function without trust. He writes that in our complex interconnect and global society, that we need a lot of trust.

Schneier makes frequent reference to Dunbar's number, which he first references in chapter 2. Dunbars number was first proposed by British anthropologist Robin Dunbar and is a theoretical cognitive limit to the number of people with whom one can maintain stable social relationships. It is generally in the area of 150. So when someone sees a person with 3,000 Facebook friends, something is clearly amiss.

In chapter 9 on institutional pressures, Schneier takes a very broad look at threats facing society today. One of the biggest perceived threats we have today is terrorism, and the book astutely notes that we can never ensure perfect security against terrorism.

If Schneier had his way, the TSA budget would be measured in the millions, not billions of dollars. He incisively observes that all the talk of terrorism as an existential threat to society is utter nonsense. As long as terrorism is rare enough (which it is), and most people survive (which they do), society will survive. He writes that while that observation is true, it is not politically viable for our leaders to come out and say that.

While the book is heavy on the people focus, Schneier also acknowledges that sometimes and for some people, the incentives to commit crimes are worth the risk. To deal with those, that is where security technologies come into play.

An interesting observation made in chapter 10 around technology is that sometimes the technological changes have absolutely nothing to do with the societal dilemma being secured. For example, he notes that between the ubiquity of keyboards and the tendency for teachers to focus on standardized tests, cursive is no longer being taught that much in schools. The result is that signatures are more likely to be either printed text is an illegible scrawl; making them easier to forge; which in turns creates new security risks.

In the book Schneier makes scores of astute observations on how society functions around security. He notes in chapter 16 that we are currently in a period of history where technology is changing faster than it ever has. The worry is that if technology changes too fast, the attackers will be able to innovate so much faster than society can that the imbalance become even greater; with failures that negatively affect society.

In many of the examples in the book, Schneier paints a dark picture given the advantage that the attackers and defectors have. But he also notes that we are in a period of history where the ability for large-scale cooperation is greater than it has ever been before. On that topic, he refers to the book The Penguin and the Leviathan: How Cooperation Triumphs over Self-Interest by Yochai Benkler where he writes that the Internet can and has enabled cooperation on a scale never before seen. And that politics, backed by science, is ready to embrace this new cooperation.

On the lighter side, in chapter 17, Schneier notes that Mussolini didn't make the trains run on time; he just made it illegal to complain about them.

Schneier notes at the end of the book that its lesson isn't that defectors will inevitably ruin everything for everyone. Rather that we as a society need to manage societal pressure to ensure that they don't.

Liars and Outliers is an absolutely fascinating and groundbreaking book. In this election year where the candidates attempt to make sweeping simplistic promises to fix complex problems, Schneier simply answers that in our complex society, there are no simple answers.

In Applied Cryptography Bruce Schneier demonstrated he was quite the smart guy. In Liars and Outliers, he shows he is even smarter than most of us first thought.

Ben Rothke is the author of Computer Security: 20 Things Every Employee Should Know.

You can purchase Liars and Outliers: Enabling the Trust that Society Needs to Thrive from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

First time accepted submitter benrothke writes "It is said that the song Wipe Out launched a generation of drummers. In the world of information security, the classic Applied Cryptography: Protocols, Algorithms, and Source Code in C by Bruce Schneier may have been the book that launched a generation of new cryptographers. Schneier's latest work of art is Liars and Outliers: Enabling the Trust that Society Needs to Thrive. For those that are looking for a follow-up to Applied Cryptography, this it is not. In fact, it is hard to classify this as an information security title and in fact the book is marked for the current affairs/sociology section. Whatever section this book ultimately falls in, the reader will find that Schneier is one of the most original thinkers around." Keep reading for the rest of Ben's review. Liars and Outliers: Enabling the Trust that Society Needs to Thrive author Bruce Schneier pages 384 publisher Wiley rating 10/10 reviewer Ben Rothke ISBN 978-1118143308 summary Brilliant book on trust and society, and it complex interrelation In Applied Cryptography Schneier dealt with the pristine world of mathematical cryptography where aspects of pure mathematics could be demonstrably proven. For example, non-repudiation is absolutely provable.

In Liars and Outliers, Schneier moves from the pristine world of mathematics into the muddy world of human trust. Non-repudiation is no longer an absolute in a world where a Windows kernel can be compromised and end-users can be victims of social engineering.

The book addresses the fundamental question of how does society function when you cant trust everyone. Schneier notes that nothing in society works without trust. Its the foundation of communities, commerce, democracy, in truth — everything. And Schneier deals extensively with social and moral pressures that effect trust.

Liars and Outliers is very similar to books by Umberto Eco, that have a Renaissance feel to them; bringing myriad and diverse topics together. Schneier does this here and intertwines topics such as game theory, evolution, surveillance, existentialism and much more. Schneier's brilliance is that he is able to connect seemingly disparate dots around information security and society, and show how they are in truth tightly coupled.

In the book, Schneier makes note of those that don't follow the rules. He calls these people defectors, and these are the liars and outliers of the book. The book notes that everything is a trade-off, and these defectors are the ones that try to break the rules.

An overall theme of the book, in which Schneier touches and references sociology, psychology, economics, criminology, anthropology, game theory and much more, is that society can't function without trust. He writes that in our complex interconnect and global society, that we need a lot of trust.

Schneier makes frequent reference to Dunbar's number, which he first references in chapter 2. Dunbars number was first proposed by British anthropologist Robin Dunbar and is a theoretical cognitive limit to the number of people with whom one can maintain stable social relationships. It is generally in the area of 150. So when someone sees a person with 3,000 Facebook friends, something is clearly amiss.

In chapter 9 on institutional pressures, Schneier takes a very broad look at threats facing society today. One of the biggest perceived threats we have today is terrorism, and the book astutely notes that we can never ensure perfect security against terrorism.

If Schneier had his way, the TSA budget would be measured in the millions, not billions of dollars. He incisively observes that all the talk of terrorism as an existential threat to society is utter nonsense. As long as terrorism is rare enough (which it is), and most people survive (which they do), society will survive. He writes that while that observation is true, it is not politically viable for our leaders to come out and say that.

While the book is heavy on the people focus, Schneier also acknowledges that sometimes and for some people, the incentives to commit crimes are worth the risk. To deal with those, that is where security technologies come into play.

An interesting observation made in chapter 10 around technology is that sometimes the technological changes have absolutely nothing to do with the societal dilemma being secured. For example, he notes that between the ubiquity of keyboards and the tendency for teachers to focus on standardized tests, cursive is no longer being taught that much in schools. The result is that signatures are more likely to be either printed text is an illegible scrawl; making them easier to forge; which in turns creates new security risks.

In the book Schneier makes scores of astute observations on how society functions around security. He notes in chapter 16 that we are currently in a period of history where technology is changing faster than it ever has. The worry is that if technology changes too fast, the attackers will be able to innovate so much faster than society can that the imbalance become even greater; with failures that negatively affect society.

In many of the examples in the book, Schneier paints a dark picture given the advantage that the attackers and defectors have. But he also notes that we are in a period of history where the ability for large-scale cooperation is greater than it has ever been before. On that topic, he refers to the book The Penguin and the Leviathan: How Cooperation Triumphs over Self-Interest by Yochai Benkler where he writes that the Internet can and has enabled cooperation on a scale never before seen. And that politics, backed by science, is ready to embrace this new cooperation.

On the lighter side, in chapter 17, Schneier notes that Mussolini didn't make the trains run on time; he just made it illegal to complain about them.

Schneier notes at the end of the book that its lesson isn't that defectors will inevitably ruin everything for everyone. Rather that we as a society need to manage societal pressure to ensure that they don't.

Liars and Outliers is an absolutely fascinating and groundbreaking book. In this election year where the candidates attempt to make sweeping simplistic promises to fix complex problems, Schneier simply answers that in our complex society, there are no simple answers.

In Applied Cryptography Bruce Schneier demonstrated he was quite the smart guy. In Liars and Outliers, he shows he is even smarter than most of us first thought.

Ben Rothke is the author of Computer Security: 20 Things Every Employee Should Know.

You can purchase Liars and Outliers: Enabling the Trust that Society Needs to Thrive from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

YokimaSun writes "Sony has today released the PSVita in the U.S. and Europe. The console comes with features such as dual touch pads at the front and rear, dual cameras at the front and rear, dual analog sticks, a 5-inch OLED screen, GPS, six-axis motion sensors and a three-axis electronic compass. The PSVita is Sony's attempt at stealing the thunder away from the 3DS but also bringing back the gamers lost to the likes of Android and iOS Devices. The PSVita in Japan sold massively on its first release week but since has struggled and sold less than the PSP. With this in mind sites like Amazon have been offering many different deals to entice people to buy the console. Can Sony stop homebrewers from taking over this console?"

New submitter rescrv writes "Key-value stores (like Cassandra, Redis and DynamoDB) have been replacing traditional databases in many demanding web applications (e.g. Twitter, Google, Facebook, LinkedIn, and others). But for the most part, the differences between existing NoSQL systems come down to the choice of well-studied implementation techniques; in particular, they all provide a similar API that achieves high performance and scalability by limiting applications to simple operations like GET and PUT. HyperDex, a new key-value store developed at Cornell, stands out in the NoSQL spectrum with its unique design. HyperDex employs a unique multi-dimensional hash function to enable efficient search operations — that is, objects may be retrieved without using the key (PDF) under which they are stored. Other systems employ indexing techniques to enable search, or enumerate all objects in the system. In contrast, HyperDex's design enables applications to retrieve search results directly from servers in the system. The results are impressive. Preliminary benchmark results on the project website show that HyperDex provides significant performance improvements over Cassandra and MongoDB. With its unique design, and impressive performance, it seems fittng to ask: Is HyperDex the start of NoSQL 2.0?"

jkauzlar writes "The standard Oracle JVM has about sixty 'developer' (-XX) options which are directly related to performance monitoring or tuning. With names such as 'UseMPSS' or 'AllocatePrefetchStyle', it's clear that Joe Schmo Code Monkey was not meant to be touching them, at least until he/she learned how the forbidding inner recesses of the JVM work, particularly the garbage collectors and 'just-in-time' compiler. This dense, 600-page book will not only explain these developer options and the underlying JVM technology, but discusses performance, profiling, benchmarking and related tools in surprising breadth and detail. Not all developers will gain from this knowledge and a few will surrender to the book's side-effect of being an insomnia treatment, but for those responsible for maintaining production software, this will be essential reading and a useful long-term reference." Keep reading for the rest of jkauzlar's review. Java Performance author Charlie Hunt and Binu John pages 693 publisher Addison Wesley rating 9/10 reviewer Joe ISBN 0-13-290525-6 summary Java performance monitoring and tuning In my experience, performance tuning is not something that is given much consideration until a production program blows up and everyone is running around in circles with sirens blaring and red lights flashing. You shouldn't need a crisis however before worrying about slow responsiveness or long pauses while the JVM collects garbage at inconvenient times. If there's an opportunity to make something better, if only by five percent, you should take it, and the first step is to be aware of what those opportunities might be.

First off, here's a summary of the different themes covered:

The JVM technology: Chapter 3 in particular is dedicated to explaining, in gory detail, the internal design of the JVM, including the Just-In-Time Compiler and garbage collectors. Being requisite knowledge for anyone hoping to make any use of the rest of the book, especially the JVM tuning options, a reader would hope for this to be explained well, and it is.

JVM Tuning: Now that you know something about compilation and garbage collection, it's time to learn what control you actually have over these internals. As mentioned earlier, there are sixty developer options, as well as several standard options, at your disposal. The authors describe these throughout sections of the book, but summarize each in the first appendix.

Tools: The authors discuss tools useful for monitoring the JVM process at the OS level, tools for monitoring the internals of the JVM, profiling, and heap-dump analysis. When discussing OS tools, they're good about being vendor-neutral and cover Linux as well as Solaris and Windows. When discussing Java-specific tools, they tend to have bias toward Oracle products, opting, for example, to describe NetBean's profiler without mentioning Eclipse's. This is a minor complaint.

Benchmarking: But what good would knowledge of tuning and tools be without being able to set appropriate performance expectations. A good chunk of the text is devoted to lessons on the art of writing benchmarks for the JVM and for an assortment of application types.

Written by two engineers for Oracle's Java performance team (one former and one current), this book is as close to being the de facto document on the topic as you can get and there's not likely to be any detail related to JVM performance that these two men don't already know about.

Unlike most computer books, there's a lot of actual discussion in Java Performance, as opposed to just documentation of features. In other words, there are pages upon pages of imposing text, indicating that you actually need to sit down and read it instead of casually flipping to the parts you need at the moment. The subject matter is dry, and the authors thankfully don't try to disguise this with bad humor or speak down to the reader. In fact, it can be a difficult read at times, but intermediate to advanced developers will pick up on it quickly.

What are the book's shortcomings?

Lack of real-world case studies: Contrived examples are provided here and there, but I'm really, seriously curious to know what the authors, with probably two decades between them consulting on Java performance issues, have accomplished with the outlined techniques. Benchmarking and performance testing can be expensive processes and the main question I'm left with is whether it's actually worth it. The alternatives to performance tuning, which I'm more comfortable with, are rewriting the code or making environmental changes (usually hardware).

3rd Party tool recommendations: The authors have evidently made the decision not to try to wade through the copious choices we have for performance monitoring, profiling, etc, with few exceptions. That's understandable, because 1) they need to keep the number of pages within reasonable limits, and 2) there's a good chance they'll leave out a worthwhile product and have to apologize, or that better products will come along. From my point of view, however, these are still choices I have to make as a developer and it'd be nice to have the information with the text as I'm reading.

As you can see, the problems I have with the book are what is missing from it and not with what's already in there. It's really a fantastic resource and I can't say much more than that the material is extremely important and that if you're looking to improve your understanding of the material, this is the book to get.

You can purchase Java Performance from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

New submitter brennanw writes "Anyone who was active on mp3.com during the late 90s/early 2000's will find Amazon.com's KDP Select awfully familiar: authors who make their works exclusive to Amazon compete for a pool of money. Any time someone 'borrows' one of their books, they get a cut of a monthly sum (700K in January, 600K for February) based on how many of their books were checked out vs. how many other author's books were checked out. This is almost identical to the 'Payback for Playback' service MP3.com provided musicians a little over a decade ago. Payback for Playback effectively destroyed the original MP3.com artist community, and I don't think KDP Select is going to be much different for the self-publishing community that is growing on Amazon."

New submitter Hector's House writes "'Nothing is certain. Nothing is secure,' reflects one of the characters in Paolo Bacigalupi's novel The Windup Girl. In 23rd century Bangkok, life for many hangs by a thread. Oil has run out; rising seas threatens to engulf the city; genetically engineered diseases hover on Thailand's borders; and the threat of violence smolders as government ministries vie for power. Environmental destruction, climate change and novel plagues have wiped out many of the crop species that humanity depends on: the profits to be made from creating — or stealing — new species are potentially enormous. After a century of collapse and contraction, Western business sees hope for a new wave of globalization; Thailand's fiercely guarded seed banks may provide just the springboard needed." Keep reading for the rest of Aidan's review. The Windup Girl author Paolo Bacigalupi pages 376 publisher Night Shade Books rating 8 reviewer Aidan McKeown ISBN 978-0356500539 summary Dystopian action thriller set in 23rd century Bangkok In a street market, Anderson Lake—a prospector for a US agribusiness giant—comes across an entirely new fruit. Drawn by the promise that it might lead him to the Thai kingdom's seed banks, he follows a trail that leads him to the backstreet club run by dissipated expat Raleigh. Here he encounters Emiko, the "windup girl" of the title. In the club's signature live sex show, she is subjected to—quite graphically described—abuse on stage. Genetically engineered in Japan as a "New Person", to be companion, secretary and translator to wealthy patrons, Emiko—a sort of transgenic geisha—has been abandoned in Bangkok by her former patron. Having been trained since infancy to be compliant, and carrying canine DNA that makes life outside of a strict hierarchy unthinkable, Emiko is trapped both by her own nature and by her characteristic tick-tock stuttery movements, hardcoded into her to make her manufactured origins immediately apparent. Genetically "unclean", Emiko daily faces the threat of extermination by the environment police: she takes to the streets only at night, when she can more easily "pass". Lake is fascinated by the exotic Emiko; she in turn is drawn to him, not least as an escape from slavery—even possibly to the fabled north, where New People reputedly live in freedom. Their relationship is an ambiguous one. Lake is not inherently a tender character (he considers the murder of business associates who threaten his plans). Moreover, his status as an unwelcome corporate outsider already puts him at risk; a transgressive liaison with a "windup" endangers him further. Emiko herself (like the Thai authorities) doesn't feel that she is genuinely human. However, she is fully capable of experiencing pain and loss and—with devastating results—rage.

Bacigalupi's novel is not new, nor is it obscure: published in 2009, it went on to win the highly esteemed Nebula and Hugo awards for science-fiction writing in 2009 and 2010. However, it deserves a place on the pages of slashdot, both for its vision of the future, and how naturally that is embedded in a well-crafted, intelligent action thriller. The book takes a qualified view of our future technological development. Fossil fuel depletion has resulted in a retraction of progress. Now, human and animal labour wind massive crank shafts—a dramatic ramping up of the technology used in hand-cranked radios and windup lanterns. Everything is recycled: even sewage produces methane to light the city's gas lamps. Where technology has leaped forward is in genetic engineering. This has yielded startling benefits: megodonts, hybrid beasts of burden, the result of the splicing of the DNA of elephants with that their massive prehistoric ancestors. It has also imposed dire costs: laboratory-manufactured plagues have swept the planet, Thailand surviving only because of the extreme zealousness of its environmental police.

The setting of an Asian culture, the dystopian image of people crammed into a crumbling city, and the relationship between a cynical, jaded man and vulnerable, artificial woman inevitably recall Bladerunner; however, even if that story provided some inspiration, The Windup Girl doesn't feel derivative: Emiko is the leading protagonist, not a supporting character. And the book takes off from that point of comparison: it's not stuck there. Weaving in with the main plot are a number of sub narratives, the book drawing much of its momentum from this crisscrossing. Hock Seng, Lake's elderly Malaysian Chinese assistant, a refugee from bloody ethnic cleansing, plots his escape from the chaos he feels must ultimately engulf Bangkok. Fiery, ebullient environment police captain Jaidee Rojjanasukchai and his austere female lieutenant Kanya Chirathivat pursue genetic transgressions in an attempt to preserve what is left of Thailand's ravaged ecosystem. Meanwhile their Environment Ministry vies with the Ministry of Trade, which seeks to open up Thailand to resurgent Western business. Plot and counter plot wind the characters together into a climactic conflict sensed only dimly at the start of the book.

It is perhaps here where the book, not falls down, but stumbles. The complexity of the plot towards the end of the book becomes dense and – for me, on first reading – slowed the book's momentum. This complexity might, however, also be a strength. For the purposes of the review I came back to the book, which I had read some eight or nine months previously; it bears rereading, and the largely tight structure is rewarding, as is the plot development. The sense of place is very strong—the press of street markets, the stench and press of humanity in the crumbling high-rise apartment buildings, the tropical setting ("[the] night was black and sticky, a jungle filled with the squawks of night birds and the pulse and whir of insect life"), as is the sense of—literally—the daily grind, as men and animals wind the cranks that keep the city powered. And many of the ideas have the power to jolt: the "cheshires", cats with chameleon DNA that recall Lewis Carroll's fictional creation by changing color to melt into their surroundings, the better to exterminate already-threatened bird populations; the Dung Lord, a mafia don who controls the trade in human waste, a vital part of the city's economy. While not all the characters remain with you afterwards, fittingly, Emiko, the lonely and conflicted protagonist does. Interestingly, hers is also the character for whom the greatest leap of imagination is required—the genetically altered outsider, who makes a journey from abject slavery to a realization of her potential.

Science fiction often suffers because while much attention may have been paid to the technological aspects, the author fails to capture the complexities of the new society or convincingly grasp the characters. Bacigalupi – largely – succeeds because he recognizes that human nature doesn't change over time: elites are only too willing to exercise control with force; the outsiders and those are who different are always vulnerable; human culture, in all its strangeness and mundanity, continues. A key strength of the book is that the subjective portrayal of the characters' inner lives and thoughts means that we feel them to be inhabiting their own present, exactly as we are. They look back of course, as do we. In their case, wonderingly to a time known as "The Expansion", when Thailand was allegedly the "Land of smiles", quite unlike the misery that has become the lot of its average citizen.

If you'd like to sample Bacigalupi's writing, some of his short stories are available on his Pump Six website.

Aidan McKeown is an editor and writer living in the Netherlands. He can be contacted at aidanmckeown@gmail.com.

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

An anonymous reader writes "'Some people remember Sealab as being a classified program, but it was trying not to be,' says Ben Hellwarth, author of the new book Sealab: America's Forgotten Quest to Live and Work on the Ocean Floor, which aims to 'bring some long overdue attention to the marine version of the space program.' In the 1960s, the media largely ignored the efforts of America's aquanauts, who revolutionized deep-sea diving and paved the way for the underwater construction work being done today on offshore oil platforms. It didn't help that the public didn't understand the challenges of saturation diving; in a comical exchange a telephone operator initially refuses to connect a call between President Johnson and Aquanaut Scott Carpenter, (who sounded like a cartoon character, thanks to the helium atmosphere in his pressurized living quarters). But in spite of being remembered as a failure, the final incarnation of Sealab did provide cover for a very successful Cold War spy program."

A few weeks back, you asked gaming-world academic and game designer Ian Bogost questions from the business, philosophical, and aesthetic sides of gaming; below, find his responses. Thanks, Ian! Is it all just absurd?
by Anonymous Coward

You satirize the meaninglessness of compulsive-click based games, but what would you say is your larger point in doing so? Do you think that "big" video games (for instance, ones with complex plots and characters, cooperation among players, etc) are all that much better, or would much of the same critique apply?

(Sure, they're not quite as mindless, but they still mean that people are spending time and money to withdraw from reality to some extent, and substituting made-up, arbitrary goals for interacting with other people. Is it purely happenstance and convenience that means you've made a certain point with social games, rather than, say, remade Catch-22 as a FPS?)

Ian Bogost: In my original essay about Cow Clicker, written when the game launched in the summer of 2010, I made a similar observation about "big" videogames: they seem to destroy time. (My exact words were, "Many of today's console games exert a time crush. They demand tens or even hundreds of hours of attention to complete, some or most of which often feels empty"). As I see it, one difference between "traditional" games and social games is that the former don't try to infect the time we spend away from them as well as the time we spend with them. Surely there is something compulsive about console games too, but at least the end. The service-oriented component of social games, along with the fact that companies like Zynga require regularly renewed attention to make money, these are important differences that may not seem fundamental at first.

Still, some cultural trends are more like cracks in a wall than like monuments. It's likely that Cow Clicker is more akin to picking away the plaster to find the veins of a complex structural issue than it is like uncovering a simple fact about its foundation. I don't think that structural issue is limited to games. Whether we noticed or not, we've created a media environment driven by compulsion. Email and instant messaging are examples unbound to specific companies, but Facebook, Twitter, Google+, Pinterest, Instagram — all of these services and many more build value by monetizing our repeated and regular attention, and now we have so many different ways to ask, "Is something new? Am I missing something?" that it's possible never to stop asking those questions, all day long.



Procedural Rhetoric in morally-gray big name games?
by siphonophore

What do you think of AAA studios exploring more moral grey areas (e.g. hostage shooting airport level in COD:MW2 ) as a form of procedural rhetoric? Do you think players' natural tendencies of (in this case) non-violence toward innocents is solidified or shaken by simulating such acts?

IB: For those who don't know the reference, "procedural rhetoric" is a concept I developed in my 2007 book Persuasive Games . We have verbal and written rhetoric, which uses speech and writing to make arguments or express ideas, and we have visual rhetoric, which deals with the way images do so. I suggest procedural rhetoric as a way to describe the use of systems and models to make arguments. Videogames (and software in general) are media that are built largely out of processes, and so we can use this framework to design or evaluate how games make arguments.

Of course, the commercial games industry hasn't been very interested in making arguments with games, in taking strong positions on topics of any sort, let alone controversial ones like politics. We have begun to see some efforts to push harder at this boundary COD:MW2 is one example, but so are Deus Ex, Homefront, Farcry 2, Bioshock. I'm glad to see this progress, but of course I'd like to see more. In particular, we only seem to get the very faintest sense of an argument or position in these games. It's almost like it's just there for the publicity, but not too much publicity, because that might turn some players off.

In fact, that's the usual explanation for why we don't have AAA games with strong positions. They're expensive to make and the publishers are said to be conservative. It's true, of course. I was recently talking to some of the team responsible for securing the publishing deal for Bioshock, and they told me that even they had trouble, and that's for a game that's really just another sci-fi shooter with a very thin layer of contra-Ayn Rand dystopianism wrapped in gorgeous art deco environments.

But to believe that "the market" is the reason we don't see more of these games doesn't tell the full story. The truth is, the AAA game industry doesn't really have much to say about politics or social issues. Not only is traditional sci-fi and fantasy entertainment in books and movies far more political than the average game, even children's animated films are more political than the average game. I mean, there's more political commentary in Wall-E than in the last decade of AAA games. I'm generalizing, but game developers and executives are technolibertarians rather than artists. For them, what's good for the world is what people vote for with their wallets. And once we get enough of that position fed to us over and over again, it's no wonder that AAA shooters risk becoming just the empty power fantasies they are sometimes accused of being.



Skinner Boxes
by Catiline

I have long described both MMO gaming and Facebook social games as being a "well-padded Skinner box" for their staggered/random reward system. Do you see any possibility for anything else to eventually replace this model?

IB: I don't know. Certainly the gold rush associated with a very bare version of these mechanics isn't helping. If anything, the Skinner boxes seem to be finding their way into other genres. I haven't played Diablo III yet, but someone who tried the beta opined that it's "Farmville for hardcore gamers." Then again, I suppose we might have said the same thing about World of Warcraft half a decade ago. These features have always been in games, but there's no question that we've begun refining them in the way one refines oil, making them more pure and useful to drive the engines of commerce rather than experience.

We can't just will ourselves out of this situation. It's not simply a matter of developing a new design philosophy that will replace the old one through pure unfettered rationalism. Since the games industry responds only to economic incentives, perhaps what we need is an implosion. Just as the housing bubble was burst by the revelation of inviable lending and the related artifice of constantly-inflating property values, so perhaps something similar needs to happen to the behaviorist bubble. It may already be starting, thanks to the apparently disappointing performance of Zynga's IPO. Still, it's worth remembering that the founders and executives of today's big tech companies have been enjoying the privilege of making liquid parts of their equity on secondary markets, so the tech investment community may not have the same deterrent to bubblethink that the market in general does.

In any case, this trend should remind us that the whole media ecosystem has been built on this promise of high-leverage value derived from the aggregated behaviors of a very large base of patrons who are actually the product of these services rather than their customers. Google and Facebook are the obvious examples, but Zynga derives all of its revenue from 2.2% of its players. The remainder are there as viral marketing infrastructure. Is it even possible to opt out of this situation? Not if you also want to live productively in contemporary society.



Interesting Mechanics?
by spektre1

Hi Ian! Can you comment about game mechanics that you wish designers explored in more depth?

IB: Certainly I have my own tastes. I've said a bit about them here, such as my interest in games that offer political opinion or commentary. And I tend to prefer "systemy" games to narrative games. But at some point, all of that is just a matter of taste. And as the aphorism goes, there's no accounting for taste.

So instead of specific mechanics or styles or genres, what I'd most like to see is more earnestness and more personality in games. I'd like to see more of the creators expressed in the works, not because I want to "receive" the "messages" they are sending, but so that I can feel like the work is not being stamped out by a machine in a factory. Part of that process would have to include more conversation about and framing of games. If you compare games to other forms of creativity, there's just far less deliberate, public discussion of games than there is of painting or novels or films or even sports. Filmmakers go on talk shows, novelists give interviews in magazines. What do game makers do? They send their lowest-common-denominator PR agencies out to put words in the mouths of the enthusiast press.

I'm often more engaged by games with styles I don't particularly like, for example the games of That Game Company or Tale of Tales, because those creators make an effort to frame and personalize the work, to give players a sense of how they might approach them, an invitation to care about the logic of their weird, tiny world. There was a time when Activision shipped their videogames with photos and notes from their creators. True, that was a time when the equivalent of "AAA" games were created by individuals, but the point stands. Indie games have a greater capacity for this sort of thing, thanks to their smaller and more compact teams, but that doesn't make independent games automatically more inviting than AAA games, either (a lot of indie games are starting get that stamped out in the factory feel, too). In the AAA scene, I think Naughty Dog, Valve, PopCap, and Blizzard offer examples of culturing a style and a design sensibility.



Persuasive game elements
by Anonymous Coward

My question revolves around trends in the "gamification" of tasks as used by government, corporations and others. I am curious what you feel about the persuasive elements that may or may not be used in these endeavors. I've noticed this holiday season to some sites seem to have attempted to use some gaming elements in very persuasive ways. I haven't really looked to closely into government sites lately, but I'm sure governments around the world are already starting to adopt them. Understanding the power of this is kind of disturbing, particularly when you see how governments, etc. can abuse this. So my question is what, if any recommendations would you give to social activists looking to develop counter-gaming or ways to identify and inform others about these elements? Given the subtle nature of some of these elements, how difficult a task is it to identify these elements in games?

IB: I've been a pretty vocal critic of gamification, which I think is bullshit, and which I've suggested we reframe as exploitationware. In both of those articles about the trend, I point out that the thing governments and corporations and other organizations like best about gamification is its facility, how rapidly and undisruptively it can be integrated into their current practices. Whereas, when I write about persuasive games and procedural rhetoric and the like, I'm interested in the idea that games might be particularly useful frames for complex issues, precisely because good games make complexity and ambiguity and trade-offs central, embracing them rather than rejecting them. Systems rather than soundbites.

The problem is, most governments and even most social activists don't really want to concede that point—that hard problems are hard, that simple answers are usually wrong, and that solutions are less likely than messy, stochastic progress. Instead, they are more concerned with reproducing the conditions of their own existence. For example, I've written before about the White House's "Apps for Healthy Kids" contest. On first blush, this effort looks like an earnest attempt to create games and software about an issue of great concern and great complexity—health and nutrition. But the results are trite and meaningless, just more bad kids software about choosing the carrot instead of the candy bar. They contain no admission of the entrenched, intractable issues at the heart of healthy eating, like food subsidies, industrial farming, population growth and density, socioeconomics, and so forth. And that's because the White House didn't really launch the contest to solve anything. They launched it to make themselves appear contemporary, engaged with the current "app economy," able to make websites with big form fields.

So, the most important lesson for governments or activists or anyone else is that the subtlety is very rarely there, in fact. So either we have to show the reasons why explanations are insufficient and not just "earnest attempts" at a reasonable solution, or we have to create the subtlety in our own media, be they games or books or blog posts. We have to do that in the games themselves, but also in relation to the medium of games, which we ought to position as a medium against simplicity in the first place.



Places where 'gamification' is good?
by oneiros27

At the closing plenary for the 2011 IA Summit, Cennydd Bowles called out the whole 'UX' (User Experience) community as a whole, in that the role that most of them play is in trying to get people to spend more time on websites and buy more stuff, rather than doing stuff that really improves the world. You've taken a similar stance on 'gamification', but there's at least two groups (Zooniverse [zooniverse.org] and FoldIt [fold.it]) using it for good as they're helping to advance science. Can you think of any other situations where we could use video games to improve the world at a grand scale, and not just simple 'edutainment'?

IB: Sometimes general explanations are helpful, and other times more specific ones are required. So despite everything I just said about the games as windows into complex systems, there are other ways to think about the usefulness of games. In my most recent book, How to Do Things with Videogames , I try to make this case, showing a couple dozen or so different applications of games, from art to tools.

Zooniverse and FoldIt are what you might call "games for work." They are games deployed in the pursuit of specific outcomes in the case of both of those titles, the outcomes are identification and analysis in very large scientific data sets, for which automated (computational) analysis is unlikely to be successful. Some people have used the name "human computation" to describe this process, and Louis von Ahn at Carnegie Mellon is probably the best known proponent of it. Others use the term "playbor," and they usually mean it derogatorily.

That mind, here's a question: does human computation in games really improve the world? I know what you're thinking: how could scientific progress not be good? Well, projects like FoldIt and Zooniverse are also massive distributed outsourcing efforts, offering free labor to the research establishment. Sure, you could make a utilitarian argument for why such work is progressive and not exploitative. And it may seem reactionary and dystopian even to intimate that collaborative work might lead to a nightmarish prison state in which tiny doses of satisfaction replace both gainful employment and crafted distraction. Or it may not.

This leads me to my answer, which may disappoint: the world gets improved in fits and starts, in small ways more than in large ones, and thanks to the unseen, unthought infrastructures that undergird it more than the civic or scientific or artistic victories we celebrate in the streets or in the theaters.



Start with a 'Facebook' game or a regular website?
by Anonymous Coward

I lead an enthusiastic clan of RuneScape players, and they tend to have a pretty broad interest in gaming and game development. As the lead programmer/IT guy for the clan, I'm frequently asked about programming and how to go about doing it.

I'm considering setting up a fairly basic Mafia wars type of game for them to expand and update, coded in python/html5 and running on google app engine for simplicity's sake. Python has a huge amount of self learning resources out there, and putting a python project on GAE is my go-to method for getting a project up and running quickly.

Should I encourage them to move into building a Facebook app, or should I encourage them to keep it a standalone website?

On the one hand Facebook gives better potential for expanding their user base, but on the other there's the 30% fee for using Facebook credits and their horrible API documentation. While I want to keep things as straightforward as possible for them, I would like to see their game accumulate a decent number of players so they can show it off.

IB: A pragmatic question! For those of you who haven't developed on the Facebook platform, let me tell you: it is a fucking train wreck. Badly documented (really, the worst documentation I can imagine), works in fits and starts, infrastructure changes constantly, updates roll out weekly, features constantly deprecated and removed, support non-existent, opaque bug and issue reporting. It's a nightmare. It's the Great War of software development, with tangled barbed wire and constant cross fire.

But, in exchange for tolerating that terror, you get access to some 800 million people and the promise that the small fraction of those you can reach will bring their friends. The 30% take for Facebook Credits is a lot compared to a credit card transaction fee, but the entire system is automated and works without any need for special merchant accounts or fears of PayPal retribution. Facebook is a piece of infrastructure, and the benefits it offers as infrastructure are undeniable even if the platform's viral free-for-all days are over.

Which to choose? It sounds to me like you can get your project working without Facebook, and then consider strapping in the social and payment features as you need them. That makes you less reliant on the platform, but also allows you to explore its benefits for your situation, if indeed there are any. In any case, I think being reliant on Facebook is a terrible situation for anybody to be in, whether they are a large company or independent creator.



Tabletop Gaming?
by Anonymous Coward

Is there a bridge between tabletop gaming and video gaming?

I design tabletop games and RPGs, and sometimes when I'm designing something I realize it would all work better as a video game. Do you feel the same way sometimes when you're designing real time games to want to make them turn based or tabletop games? Is there a link between the two industries in a professional way? Can workers from either industry cross over?

IB: There are a few different ways to think about videogames. One situates them in the long history of games, from folk games through wargames through tabletop games on to videogames, and to find similarities in design, use, and application. Another places them in the history of computing, asking how videogames relate to other kinds of software and hardware media for productivity and expression. Another compares them to creative media like literature, film, art, theater, opera, puppetry, and so forth, finding opportunities for adaptation across material form, or obstacles to such adaptation. Another asks how videogames participate in cultural traditions of play, like festival, conflict, sport, and ritual. These are just some of the possible vantage points from which one could seek to understand or design games. And of course, they are not mutually exclusive.

There is a fairly strong tradition of inspiration between tabletop games and computer games. The relationship between Dungeons & Dragons and certain genres of videogames, especially adventure, RPG, and MMOs is well-known. But tabletop wargames (like those published by SPI and Avalon Hill) also inspired many computer game designers, as did the type of strategy games sometimes called German-style board games. Games like Carcassonne and Puerto Rico used to be unheard of among the general public, but thanks to the success of Settlers of Catan, thoughtful tabletop games are becoming increasingly popular, even in this age of computerization.

All of which is just to say that there are a number of successful game designers who take the tabletop-to-computer spectrum as their primary creative axis. Rainer Knizia has created many successful tabletop games as well as videogames (many of which were adaptations of his board game designs). Designers like Greg Costikyan, Brenda Brathwaite, Eric Zimmerman, Nick Fortugno, and Frank Lantz are also frequent players and designers of other types of games — not just tabletop but in some cases large-scale "big games" played in urban spaces, and installation games played in museums or galleries. And many other developers in the videogame industry also play and make non-digital games in their spare time.

There's also a technique called paper prototyping advocated by designers like Raph Koster and Stone Librande, which draws a strong material connection between tabletop and computer game design. Designer and USC professor Tracy Fullerton's book Game Design Workshop is based on this method, and a game design workshop is held every year at the Game Developers Conference that uses non-digital materials exclusively. So, in short, there is a lot of cross-over, even if that crossover isn't always expressed through published tabletop games.



What do you think of James Franco?
Anonymous Coward

I understand you may be working on some sort of joint project with him in the academic world. Is he the rockstar that he appears to be?

IB: Perhaps one day I will be fortunate enough to have James Franco nap in my classes. Until then, I'll have to be satisfied to click on his likeness in the post-cowpocalypse version of Cow Clicker.



Re:Yo, Ian!
by Hatta

I actually read your book Racing the Beam. Fantastic book. The only thing I really want to know is when we can expect the NES, SNES, and Sega Genesis to get the same treatment.

IB: Thanks for reading! For those who haven't yet, Racing the Beam is a book I wrote with Nick Montfort about the ways the hardware design of the Atari Video Computer System (VCS, aka the Atari 2600) influenced game design. The book was the first in a series Nick and I edit called Platform Studies [http://platformstudies.com]. Books in the series discuss the relationship between the hardware and software design of computer platforms and the creative works produced on those systems. These books are meant to be technically detailed but in an explanatory and accessible way, one that doesn't require any particular background to read.

We have a number of new books lined up in the series. Two books will be published this spring: Codename Revolution: The Nintendo Wii Platform by Steven E. Jones and George K. Thiruvathukal, and The Future Was Here: The Commodore Amiga, by Jimmy Maher. Other books at various stages of progress do include the NES, SNES, Flash, and a number of other more esoteric platforms. We're actively looking for more books and authors, so if any readers here have projects that match our vision for the series, please get in touch. Keep in mind that we're interested in computer platforms of all kinds, not just videogame systems.

A few weeks back, you asked gaming-world academic and game designer Ian Bogost questions from the business, philosophical, and aesthetic sides of gaming; below, find his responses. Thanks, Ian! Is it all just absurd?
by Anonymous Coward

You satirize the meaninglessness of compulsive-click based games, but what would you say is your larger point in doing so? Do you think that "big" video games (for instance, ones with complex plots and characters, cooperation among players, etc) are all that much better, or would much of the same critique apply?

(Sure, they're not quite as mindless, but they still mean that people are spending time and money to withdraw from reality to some extent, and substituting made-up, arbitrary goals for interacting with other people. Is it purely happenstance and convenience that means you've made a certain point with social games, rather than, say, remade Catch-22 as a FPS?)

Ian Bogost: In my original essay about Cow Clicker, written when the game launched in the summer of 2010, I made a similar observation about "big" videogames: they seem to destroy time. (My exact words were, "Many of today's console games exert a time crush. They demand tens or even hundreds of hours of attention to complete, some or most of which often feels empty"). As I see it, one difference between "traditional" games and social games is that the former don't try to infect the time we spend away from them as well as the time we spend with them. Surely there is something compulsive about console games too, but at least the end. The service-oriented component of social games, along with the fact that companies like Zynga require regularly renewed attention to make money, these are important differences that may not seem fundamental at first.

Still, some cultural trends are more like cracks in a wall than like monuments. It's likely that Cow Clicker is more akin to picking away the plaster to find the veins of a complex structural issue than it is like uncovering a simple fact about its foundation. I don't think that structural issue is limited to games. Whether we noticed or not, we've created a media environment driven by compulsion. Email and instant messaging are examples unbound to specific companies, but Facebook, Twitter, Google+, Pinterest, Instagram — all of these services and many more build value by monetizing our repeated and regular attention, and now we have so many different ways to ask, "Is something new? Am I missing something?" that it's possible never to stop asking those questions, all day long.



Procedural Rhetoric in morally-gray big name games?
by siphonophore

What do you think of AAA studios exploring more moral grey areas (e.g. hostage shooting airport level in COD:MW2 ) as a form of procedural rhetoric? Do you think players' natural tendencies of (in this case) non-violence toward innocents is solidified or shaken by simulating such acts?

IB: For those who don't know the reference, "procedural rhetoric" is a concept I developed in my 2007 book Persuasive Games . We have verbal and written rhetoric, which uses speech and writing to make arguments or express ideas, and we have visual rhetoric, which deals with the way images do so. I suggest procedural rhetoric as a way to describe the use of systems and models to make arguments. Videogames (and software in general) are media that are built largely out of processes, and so we can use this framework to design or evaluate how games make arguments.

Of course, the commercial games industry hasn't been very interested in making arguments with games, in taking strong positions on topics of any sort, let alone controversial ones like politics. We have begun to see some efforts to push harder at this boundary COD:MW2 is one example, but so are Deus Ex, Homefront, Farcry 2, Bioshock. I'm glad to see this progress, but of course I'd like to see more. In particular, we only seem to get the very faintest sense of an argument or position in these games. It's almost like it's just there for the publicity, but not too much publicity, because that might turn some players off.

In fact, that's the usual explanation for why we don't have AAA games with strong positions. They're expensive to make and the publishers are said to be conservative. It's true, of course. I was recently talking to some of the team responsible for securing the publishing deal for Bioshock, and they told me that even they had trouble, and that's for a game that's really just another sci-fi shooter with a very thin layer of contra-Ayn Rand dystopianism wrapped in gorgeous art deco environments.

But to believe that "the market" is the reason we don't see more of these games doesn't tell the full story. The truth is, the AAA game industry doesn't really have much to say about politics or social issues. Not only is traditional sci-fi and fantasy entertainment in books and movies far more political than the average game, even children's animated films are more political than the average game. I mean, there's more political commentary in Wall-E than in the last decade of AAA games. I'm generalizing, but game developers and executives are technolibertarians rather than artists. For them, what's good for the world is what people vote for with their wallets. And once we get enough of that position fed to us over and over again, it's no wonder that AAA shooters risk becoming just the empty power fantasies they are sometimes accused of being.



Skinner Boxes
by Catiline

I have long described both MMO gaming and Facebook social games as being a "well-padded Skinner box" for their staggered/random reward system. Do you see any possibility for anything else to eventually replace this model?

IB: I don't know. Certainly the gold rush associated with a very bare version of these mechanics isn't helping. If anything, the Skinner boxes seem to be finding their way into other genres. I haven't played Diablo III yet, but someone who tried the beta opined that it's "Farmville for hardcore gamers." Then again, I suppose we might have said the same thing about World of Warcraft half a decade ago. These features have always been in games, but there's no question that we've begun refining them in the way one refines oil, making them more pure and useful to drive the engines of commerce rather than experience.

We can't just will ourselves out of this situation. It's not simply a matter of developing a new design philosophy that will replace the old one through pure unfettered rationalism. Since the games industry responds only to economic incentives, perhaps what we need is an implosion. Just as the housing bubble was burst by the revelation of inviable lending and the related artifice of constantly-inflating property values, so perhaps something similar needs to happen to the behaviorist bubble. It may already be starting, thanks to the apparently disappointing performance of Zynga's IPO. Still, it's worth remembering that the founders and executives of today's big tech companies have been enjoying the privilege of making liquid parts of their equity on secondary markets, so the tech investment community may not have the same deterrent to bubblethink that the market in general does.

In any case, this trend should remind us that the whole media ecosystem has been built on this promise of high-leverage value derived from the aggregated behaviors of a very large base of patrons who are actually the product of these services rather than their customers. Google and Facebook are the obvious examples, but Zynga derives all of its revenue from 2.2% of its players. The remainder are there as viral marketing infrastructure. Is it even possible to opt out of this situation? Not if you also want to live productively in contemporary society.



Interesting Mechanics?
by spektre1

Hi Ian! Can you comment about game mechanics that you wish designers explored in more depth?

IB: Certainly I have my own tastes. I've said a bit about them here, such as my interest in games that offer political opinion or commentary. And I tend to prefer "systemy" games to narrative games. But at some point, all of that is just a matter of taste. And as the aphorism goes, there's no accounting for taste.

So instead of specific mechanics or styles or genres, what I'd most like to see is more earnestness and more personality in games. I'd like to see more of the creators expressed in the works, not because I want to "receive" the "messages" they are sending, but so that I can feel like the work is not being stamped out by a machine in a factory. Part of that process would have to include more conversation about and framing of games. If you compare games to other forms of creativity, there's just far less deliberate, public discussion of games than there is of painting or novels or films or even sports. Filmmakers go on talk shows, novelists give interviews in magazines. What do game makers do? They send their lowest-common-denominator PR agencies out to put words in the mouths of the enthusiast press.

I'm often more engaged by games with styles I don't particularly like, for example the games of That Game Company or Tale of Tales, because those creators make an effort to frame and personalize the work, to give players a sense of how they might approach them, an invitation to care about the logic of their weird, tiny world. There was a time when Activision shipped their videogames with photos and notes from their creators. True, that was a time when the equivalent of "AAA" games were created by individuals, but the point stands. Indie games have a greater capacity for this sort of thing, thanks to their smaller and more compact teams, but that doesn't make independent games automatically more inviting than AAA games, either (a lot of indie games are starting get that stamped out in the factory feel, too). In the AAA scene, I think Naughty Dog, Valve, PopCap, and Blizzard offer examples of culturing a style and a design sensibility.



Persuasive game elements
by Anonymous Coward

My question revolves around trends in the "gamification" of tasks as used by government, corporations and others. I am curious what you feel about the persuasive elements that may or may not be used in these endeavors. I've noticed this holiday season to some sites seem to have attempted to use some gaming elements in very persuasive ways. I haven't really looked to closely into government sites lately, but I'm sure governments around the world are already starting to adopt them. Understanding the power of this is kind of disturbing, particularly when you see how governments, etc. can abuse this. So my question is what, if any recommendations would you give to social activists looking to develop counter-gaming or ways to identify and inform others about these elements? Given the subtle nature of some of these elements, how difficult a task is it to identify these elements in games?

IB: I've been a pretty vocal critic of gamification, which I think is bullshit, and which I've suggested we reframe as exploitationware. In both of those articles about the trend, I point out that the thing governments and corporations and other organizations like best about gamification is its facility, how rapidly and undisruptively it can be integrated into their current practices. Whereas, when I write about persuasive games and procedural rhetoric and the like, I'm interested in the idea that games might be particularly useful frames for complex issues, precisely because good games make complexity and ambiguity and trade-offs central, embracing them rather than rejecting them. Systems rather than soundbites.

The problem is, most governments and even most social activists don't really want to concede that point—that hard problems are hard, that simple answers are usually wrong, and that solutions are less likely than messy, stochastic progress. Instead, they are more concerned with reproducing the conditions of their own existence. For example, I've written before about the White House's "Apps for Healthy Kids" contest. On first blush, this effort looks like an earnest attempt to create games and software about an issue of great concern and great complexity—health and nutrition. But the results are trite and meaningless, just more bad kids software about choosing the carrot instead of the candy bar. They contain no admission of the entrenched, intractable issues at the heart of healthy eating, like food subsidies, industrial farming, population growth and density, socioeconomics, and so forth. And that's because the White House didn't really launch the contest to solve anything. They launched it to make themselves appear contemporary, engaged with the current "app economy," able to make websites with big form fields.

So, the most important lesson for governments or activists or anyone else is that the subtlety is very rarely there, in fact. So either we have to show the reasons why explanations are insufficient and not just "earnest attempts" at a reasonable solution, or we have to create the subtlety in our own media, be they games or books or blog posts. We have to do that in the games themselves, but also in relation to the medium of games, which we ought to position as a medium against simplicity in the first place.



Places where 'gamification' is good?
by oneiros27

At the closing plenary for the 2011 IA Summit, Cennydd Bowles called out the whole 'UX' (User Experience) community as a whole, in that the role that most of them play is in trying to get people to spend more time on websites and buy more stuff, rather than doing stuff that really improves the world. You've taken a similar stance on 'gamification', but there's at least two groups (Zooniverse [zooniverse.org] and FoldIt [fold.it]) using it for good as they're helping to advance science. Can you think of any other situations where we could use video games to improve the world at a grand scale, and not just simple 'edutainment'?

IB: Sometimes general explanations are helpful, and other times more specific ones are required. So despite everything I just said about the games as windows into complex systems, there are other ways to think about the usefulness of games. In my most recent book, How to Do Things with Videogames , I try to make this case, showing a couple dozen or so different applications of games, from art to tools.

Zooniverse and FoldIt are what you might call "games for work." They are games deployed in the pursuit of specific outcomes in the case of both of those titles, the outcomes are identification and analysis in very large scientific data sets, for which automated (computational) analysis is unlikely to be successful. Some people have used the name "human computation" to describe this process, and Louis von Ahn at Carnegie Mellon is probably the best known proponent of it. Others use the term "playbor," and they usually mean it derogatorily.

That mind, here's a question: does human computation in games really improve the world? I know what you're thinking: how could scientific progress not be good? Well, projects like FoldIt and Zooniverse are also massive distributed outsourcing efforts, offering free labor to the research establishment. Sure, you could make a utilitarian argument for why such work is progressive and not exploitative. And it may seem reactionary and dystopian even to intimate that collaborative work might lead to a nightmarish prison state in which tiny doses of satisfaction replace both gainful employment and crafted distraction. Or it may not.

This leads me to my answer, which may disappoint: the world gets improved in fits and starts, in small ways more than in large ones, and thanks to the unseen, unthought infrastructures that undergird it more than the civic or scientific or artistic victories we celebrate in the streets or in the theaters.



Start with a 'Facebook' game or a regular website?
by Anonymous Coward

I lead an enthusiastic clan of RuneScape players, and they tend to have a pretty broad interest in gaming and game development. As the lead programmer/IT guy for the clan, I'm frequently asked about programming and how to go about doing it.

I'm considering setting up a fairly basic Mafia wars type of game for them to expand and update, coded in python/html5 and running on google app engine for simplicity's sake. Python has a huge amount of self learning resources out there, and putting a python project on GAE is my go-to method for getting a project up and running quickly.

Should I encourage them to move into building a Facebook app, or should I encourage them to keep it a standalone website?

On the one hand Facebook gives better potential for expanding their user base, but on the other there's the 30% fee for using Facebook credits and their horrible API documentation. While I want to keep things as straightforward as possible for them, I would like to see their game accumulate a decent number of players so they can show it off.

IB: A pragmatic question! For those of you who haven't developed on the Facebook platform, let me tell you: it is a fucking train wreck. Badly documented (really, the worst documentation I can imagine), works in fits and starts, infrastructure changes constantly, updates roll out weekly, features constantly deprecated and removed, support non-existent, opaque bug and issue reporting. It's a nightmare. It's the Great War of software development, with tangled barbed wire and constant cross fire.

But, in exchange for tolerating that terror, you get access to some 800 million people and the promise that the small fraction of those you can reach will bring their friends. The 30% take for Facebook Credits is a lot compared to a credit card transaction fee, but the entire system is automated and works without any need for special merchant accounts or fears of PayPal retribution. Facebook is a piece of infrastructure, and the benefits it offers as infrastructure are undeniable even if the platform's viral free-for-all days are over.

Which to choose? It sounds to me like you can get your project working without Facebook, and then consider strapping in the social and payment features as you need them. That makes you less reliant on the platform, but also allows you to explore its benefits for your situation, if indeed there are any. In any case, I think being reliant on Facebook is a terrible situation for anybody to be in, whether they are a large company or independent creator.



Tabletop Gaming?
by Anonymous Coward

Is there a bridge between tabletop gaming and video gaming?

I design tabletop games and RPGs, and sometimes when I'm designing something I realize it would all work better as a video game. Do you feel the same way sometimes when you're designing real time games to want to make them turn based or tabletop games? Is there a link between the two industries in a professional way? Can workers from either industry cross over?

IB: There are a few different ways to think about videogames. One situates them in the long history of games, from folk games through wargames through tabletop games on to videogames, and to find similarities in design, use, and application. Another places them in the history of computing, asking how videogames relate to other kinds of software and hardware media for productivity and expression. Another compares them to creative media like literature, film, art, theater, opera, puppetry, and so forth, finding opportunities for adaptation across material form, or obstacles to such adaptation. Another asks how videogames participate in cultural traditions of play, like festival, conflict, sport, and ritual. These are just some of the possible vantage points from which one could seek to understand or design games. And of course, they are not mutually exclusive.

There is a fairly strong tradition of inspiration between tabletop games and computer games. The relationship between Dungeons & Dragons and certain genres of videogames, especially adventure, RPG, and MMOs is well-known. But tabletop wargames (like those published by SPI and Avalon Hill) also inspired many computer game designers, as did the type of strategy games sometimes called German-style board games. Games like Carcassonne and Puerto Rico used to be unheard of among the general public, but thanks to the success of Settlers of Catan, thoughtful tabletop games are becoming increasingly popular, even in this age of computerization.

All of which is just to say that there are a number of successful game designers who take the tabletop-to-computer spectrum as their primary creative axis. Rainer Knizia has created many successful tabletop games as well as videogames (many of which were adaptations of his board game designs). Designers like Greg Costikyan, Brenda Brathwaite, Eric Zimmerman, Nick Fortugno, and Frank Lantz are also frequent players and designers of other types of games — not just tabletop but in some cases large-scale "big games" played in urban spaces, and installation games played in museums or galleries. And many other developers in the videogame industry also play and make non-digital games in their spare time.

There's also a technique called paper prototyping advocated by designers like Raph Koster and Stone Librande, which draws a strong material connection between tabletop and computer game design. Designer and USC professor Tracy Fullerton's book Game Design Workshop is based on this method, and a game design workshop is held every year at the Game Developers Conference that uses non-digital materials exclusively. So, in short, there is a lot of cross-over, even if that crossover isn't always expressed through published tabletop games.



What do you think of James Franco?
Anonymous Coward

I understand you may be working on some sort of joint project with him in the academic world. Is he the rockstar that he appears to be?

IB: Perhaps one day I will be fortunate enough to have James Franco nap in my classes. Until then, I'll have to be satisfied to click on his likeness in the post-cowpocalypse version of Cow Clicker.



Re:Yo, Ian!
by Hatta

I actually read your book Racing the Beam. Fantastic book. The only thing I really want to know is when we can expect the NES, SNES, and Sega Genesis to get the same treatment.

IB: Thanks for reading! For those who haven't yet, Racing the Beam is a book I wrote with Nick Montfort about the ways the hardware design of the Atari Video Computer System (VCS, aka the Atari 2600) influenced game design. The book was the first in a series Nick and I edit called Platform Studies [http://platformstudies.com]. Books in the series discuss the relationship between the hardware and software design of computer platforms and the creative works produced on those systems. These books are meant to be technically detailed but in an explanatory and accessible way, one that doesn't require any particular background to read.

We have a number of new books lined up in the series. Two books will be published this spring: Codename Revolution: The Nintendo Wii Platform by Steven E. Jones and George K. Thiruvathukal, and The Future Was Here: The Commodore Amiga, by Jimmy Maher. Other books at various stages of progress do include the NES, SNES, Flash, and a number of other more esoteric platforms. We're actively looking for more books and authors, so if any readers here have projects that match our vision for the series, please get in touch. Keep in mind that we're interested in computer platforms of all kinds, not just videogame systems.