Slashdot Mirror

Arborists are cloning saplings from the stumps of the world's largest, strongest, and longest-lived trees -- felled for timber more than a century ago -- to create redwood "super groves" that can help fight climate change. "Using saplings made from the basal sprouts of these super trees to plant new groves in temperate countries around the world means the growths have a better chance than most to become giants themselves," reports Quartz. "Their ancestors grew up to 400 ft (122 m) tall and to 35 ft in diameter, after all, larger than the largest living redwood today, a giant sequoia in California's Sequoia National Park." From the report: Already, super saplings from the project are thriving in groves in Canada, England, Wales, France, New Zealand, and Australia. None of these locales are places where coastal redwoods grow naturally, but they all have cool temperatures and sufficient fog for the redwoods, which drink moisture from the air in summer rather than relying on rain. [David Milarch, founder of the Archangel Ancient Tree Archive, a U.S. nonprofit that propagates the world's largest trees] calls this "assisted migration." Last month, his organization planted another such grove in the Presidio in San Francisco, California. The park lies along the U.S. west's redwood corridor, which runs from Oregon to California, home to the stumps the saplings were cloned from. But 95% of giant growths there were cut long ago. Many of the redwoods along the corridor now are young trees. Milarch notes that as the local climate is getting hotter and less foggy, it's no longer as conducive to producing the mega growths of yore. Now, 75 saplings created from the basal sprouts of the most rugged and massive ancient tree stumps of the coastal region will grow in the Presidio. They may eventually become the hardiest and tallest trees around, if their ancestors are any indication.

An anonymous reader quotes a report from the University of California, Davis about the world's first microchip with 1,000 independent programmable processors: The 1,000 processors can execute 115 billion instructions per second while dissipating only 0.7 Watts, low enough to be powered by a single AA battery...more than 100 times more efficiently than a modern laptop processor... The energy-efficient "KiloCore" chip has a maximum computation rate of 1.78 trillion instructions per second and contains 621 million transistors.
Programs get split across many processors (each running independently as needed with an average maximum clock frequency of 1.78 gigahertz), "and they transfer data directly to each other rather than using a pooled memory area that can become a bottleneck for data." Imagine how many mind-boggling things will become possible if this much processing power ultimately finds its way into new consumer technologies.

schwit1 writes Rock soil droplets formed by heating most likely came from Stone Age house fires and not from a disastrous cosmic impact 12,900 years ago, according to new research from the University of California, Davis. The study, of soil from Syria, is the latest to discredit the controversial theory that a cosmic impact triggered the Younger Dryas cold period."

HughPickens.com writes: Discussions whether a given programming language is "the right tool for the job" inevitably lead to debate. While some of these debates may appear to be tinged with an almost religious fervor, most people would agree that a programming language can impact not only the coding process, but also the properties of the resulting product. Now computer scientists at the University of California — Davis have published a study of the effect of programming languages on software quality (PDF) using a very large data set from GitHub. They analyzed 729 projects with 80 million SLOC by 29,000 authors and 1.5 million commits in 17 languages. The large sample size allowed them to use a mixed-methods approach, combining multiple regression modeling with visualization and text analytics, to study the effect of language features such as static vs. dynamic typing, strong vs. weak typing on software quality. By triangulating findings from different methods, and controlling for confounding effects such as team size, project size, and project history, they report that language design does have a significant, but modest effect on software quality.

Quoting: "Most notably, it does appear that strong typing is modestly better than weak typing, and among functional languages, static typing is also somewhat better than dynamic typing. We also find that functional languages are somewhat better than procedural languages. It is worth noting that these modest effects arising from language design are overwhelmingly dominated by the process factors such as project size, team size, and commit size. However, we hasten to caution the reader that even these modest effects might quite possibly be due to other, intangible process factors, e.g., the preference of certain personality types for functional, static and strongly typed languages."

Hugh Pickens DOT Com (2995471) writes "There have been many explanations for the zebra's impressive stripes including Darwin who thought that the stripes help males and females make sensible choices about whom they mate with. Now Henry Nicholls reports at The Guardian that Tim Caro at the University of California, Davis, has taken a completely original approach, stepping back from one species of zebra and attempting to account for the differences in patterning across different species and subspecies of zebras, horses and asses to see if there is anything about the habitat or ecology of these different equids that hints at the function of stripes. To answer that question, Caro and his colleagues created a detailed map charting the ranges of striped vs. non-striped species and subspecies. Then they worked on a map for the bloodsuckers that targeted those species — specifically, abanid biting flies (horse flies) and tsetse flies.

'I was amazed by our results,' says Caro. 'Again and again, there was greater striping on areas of the body in those parts of the world where there was more annoyance from biting flies.' Where there are tsetse flies, for instance, the equids tend to come in stripes. Where there aren't, they don't. Biologists who buy into the bug-repellent hypothesis say that, all other things being equal, striped animals would have an evolutionary advantage because they wouldn't suffer from the loss of blood, reduced weight gain and lowered milk production that's associated with bug bites. Tsetse flies are also associated with the transmission of diseases. 'There are a lot of them, such as sleeping sickness, equine anemia and equine influenza,' Caro says. Why would zebras evolve to have stripes whereas other hooved mammals did not? The study found that, unlike other African hooved mammals living in the same areas as zebras, zebra hair is shorter than the mouthpart length of biting flies, so zebras may be particularly susceptible to annoyance by biting flies. 'It's clear that the flies can get through that hair and get to the skin.'"

Hugh Pickens DOT Com writes "John Sutter writes at CNN that as Swiss citizens vote on November 24 to consider capping executive pay at 12 times what the lowest-paid worker at a company makes in a referendum. Some say the idea of tethering top executive pay to some sort of concrete metric might stop American execs from floating further into the stratosphere. 'Here in America, the land of unequal opportunity, the CEOs of top-500 companies make in a single day about what it takes an average "rank-and-file" worker a year to earn, according to the AFL-CIO, the federation of unions,' writes Sutter. 'Democracy starts to unravel if a few people become wildly, ethereally successful, while the rest of a country struggles.' A $1 million salary worked for American CEOs from the 1930s to 1980s, says Lynn Stout. But CEO pay, including options realized that year, jumped about 875%, to $14.1 million, from 1978 to 2012, according to the Economic Policy Institute. 'What we've got is basically an arms race,' Stout says, 'where the CEOs are competing on pay because they each want to have higher status than the others.' Peter Drucker, the father of business management, famously said the CEO-to-worker salary ratio should not exceed 20:1, which is what existed in the United States in 1965. Beyond that, managers will see an increase in 'resentment and falling morale,' said Drucker. Stout has suggested that the IRS make CEO pay a non-deductible business expense when it's higher than 100 times the minimum wage. 'Limiting CEO pay to 100 times the minimum wage would still allow top execs to be millionaires,' concludes Sutter. 'And here's the best part: If the fat cats wanted a pay increase, maybe the best way for them to get it would be to throw political weight behind a campaign to boost the minimum wage.'"

New submitter daleallan writes "Triclosan, which is widely used in consumer handsoaps, toothpaste, clothes, carpets and trash bags, impairs muscle function in animal studies, say researchers at UC Davis (abstract). It slows swimming in fish and reduces muscle strength in mice. It may even impair the ability of heart muscle cells to contract. The chemical is in everyone's home and pervasive in the environment, the lead researcher says. One million pounds of Triclosan is produced in the U.S. annually and it's found in waterways, fish, dolphins, human urine, blood and breast milk. The researchers say their findings 'Call for a dramatic reduction in use.' It's in my Colgate Total toothpaste, and in fact, preventing gingivitis is the only use that may be worthwhile, although this makes me think twice about continuing to brush with it." This isn't the first time Triclosan has been in the news over safety concerns.

Hugh Pickens writes "Alasdair Wilkins writes that when a squirrel encounters a rattlesnake in the wild, it does something very peculiar to survive its brush with the predator — something is so peculiar that scientists are building robotic squirrels just to try to understand the behavior. A live squirrel does two things when it sees a rattlesnake. It starts moving its tail in a flagging motion and actually heats up the temperature of its tail. Because rattlesnakes can see in the infrared wavelengths, they should be able to see both the tail move and heat up. The question is which of these two signals is important and just what message it's supposed to send to the rattlesnake. To that end, engineers at UC Davis have built robosquirrels, which allow the biologists to simulate the two squirrel behaviors one a time and the research so far suggests it's the heated tail, not the flagging motion, that the snake responds to, making it one of the first known examples of infrared communication between two distinct species. 'Snakes will rarely strike at a flagging adult squirrel — and if they do they almost always miss,' says Rulon Clark, assistant professor of biology at San Diego State University and an expert on snake behavior. 'In some cases, it seems the rattlesnakes just decide it's best to cut their losses after dealing with these confusing critters,' adds Wilkins, 'as sometimes the snakes just leave the area completely after encountering these flagging, tail-heating squirrels.'"

New submitter Required Snark writes "UC Davis researchers have found a mechanism where the sodium in sea water can cause uranium nano-particles to be released from nuclear reactor fuel rods. Normally the uranium oxide compounds composing the rods are very resistant to leaching into water. This could have serious consequences for the Fukushima disaster, since sea water was used for emergency cooling."

An anonymous reader writes "Research (Pdf) shows that the descendants of people who in 1858 had 'rich' surnames such as Mandeville, Percy and Darcy, indicating they were descended from the French nobility, are still substantially wealthier in 2011 than those with traditionally 'poor' or artisanal surnames."

walterbyrd writes "Dr. Norman Matloff of the University of California-Davis computer science department argues that US citizens are avoiding 'Science Technology Engineering Math' (STEM) careers, because US citizens see those fields as being ruined by massive offshoring and inshoring. 'Despite widely publicized claims that foreign tech workers and scientists represent exceptional ability and are thus vital to American innovation, Matloff called that argument merely "a good sound byte for lobbyists" supporting industry proposals for higher visa caps. The data (PDF), on the other hand, indicate that those admitted are no more able, productive, or innovative than America's homegrown talent, he said.'"

radioweather writes "The cryptic press release NASA made last week that set the blogosphere afire with conjecture, which announced: 'NASA will hold a news conference at 2 p.m. EST on Thursday, Dec. 2, to discuss an astrobiology finding that will impact the search for evidence of extraterrestrial life.' may be a case of 'go fever' science pushed too quickly by press release. A scathing article in Slate.com lists some very prominent microbiologists who say the NASA-backed study is seriously flawed and that the finding may be based on something as simple as poor sample washing to remove phosphate contamination. One of the scientists, Shelley Copley of the University of Colorado said 'This paper should not have been published,' while another, John Roth of UC-Davis says: 'I suspect that NASA may be so desperate for a positive story that they didn't look for any serious advice from DNA or even microbiology people,' The experience reminded some of another press conference NASA held in 1996. Scientists unveiled a meteorite from Mars in which they said there were microscopic fossils. A number of critics condemned the report (also published in Science) for making claims it couldn't back up."

jamie tips this mind-blowing data visualization concept from (naturally) data visualization researcher Michael Ogawa, who explains that it was inspired by "this XKCD comic. It represents characters as lines that converge in time as they share scenes. Could this technique be adapted for software developers who work on the same code?"

AlexMax2742 writes "Great news for those anxious gamers who have been waiting for a Linux and Mac version of Quake Live. Support for both is being implemented with next Tuesday's update, according to project lead Marty Stratton, who gave the release date during a press conference held at QuakeCon 2009. A video of the press conference is up at QuakeUnity." John Carmack revealed that they're working on a "premium" subscription service for Quake Live, which will allow players to configure and run their own private servers. Also at QuakeCon, a new trailer was released for id's upcoming shooter, Rage. Kotaku posted an extensive preview of Rage, saying, "I've seen no game that, in this realistic style, looks so good and has a landscape so rich with visual splendor." A detailed presentation on id Tech 5, the new game engine behind Rage, was given at SIGGRAPH 2009 last week.

johkir writes "As early as 1965, when Al Gore was a freshman in college, a panel of distinguished environmental scientists warned President Lyndon B. Johnson that CO2 emissions from fossil fuels might cause 'marked changes in climate' that 'could be deleterious.' Yet the scientists did not so much as mention the possibility of reducing emissions. Instead they considered one idea: 'spreading very small reflective particles' over about five million square miles of ocean, so as to bounce about 1 percent more sunlight back to space — 'a wacky geoengineering solution.' In the decades since, geoengineering ideas never died, but they did get pushed to the fringe — they were widely perceived by scientists and environmentalists alike as silly and even immoral attempts to avoid addressing the root of the problem of global warming. Three recent developments have brought them back into the mainstream." We've discussed some pretty strange ideas in the geoengineering line over the last few years.

Roland Piquepaille writes "Three years after the development of robots that act like rats, UC Davis engineers have designed a control system for robots allowing them to pick up on cues that the leader is about to turn, predict where it is going and follow it. This system mimics the human ability to capture signals — consciously or not — from drivers on the road or people walking in the streets to predict what they're about to do. As the team leader said, 'Robots that are better at following could be easier for people to work with.' With this system, a hospital robot could follow doctors during their rounds."

maemst writes "The project selection phase of the Google-sponsored 24-hour programming contest Hackontest ends in two days. Until today, almost a thousand persons voted for new features in 57 open source projects. Currently sK1, TYPO3 and OpenLieroX, phpMyAdmin and Inkscape are on the top list. However, only the developers of three of them may participate in the competition on September 24/25, 2008 in Zurich, Switzerland. code_swarm animations of the top five projects show how previous development has evolved so far."

An anonymous reader writes "A student at UC Davis has created some stunning visualizations of open source software contributions, including Eclipse, Python, Apache httpd and Postgres. From the website: 'This visualization, called code_swarm, shows the history of commits in a software project. A commit happens when a developer makes changes to the code or documents and transfers them into the central project repository. Both developers and files are represented as moving elements. When a developer commits a file, it lights up and flies towards that developer. Files are colored according to their purpose, such as whether they are source code or a document. If files or developers have not been active for a while, they will fade away. A histogram at the bottom keeps a reminder of what has come before.'"

Invisible Pink Unicorn writes "UC Davis researchers have dated the earliest step in the formation of the solar system — when microscopic interstellar dust coalesced into mountain-sized chunks of rock — to 4,568 million years ago, within a range of about 2,080,000 years. In the second stage, mountain-sized masses grew quickly into about 20 Mars-sized planets and, in the third and final stage, these small planets smashed into each other in a series of giant collisions that left the planets we know today. The dates of these intermediary stages are well established. The article abstract is available from Astrophysical Journal Letters."

theodp writes "A California appeals court has reinstated former Stanford prof Brian Reid's age-discrimination suit against Google, ruling that a lower Court erred in siding with Google and rejecting Mr. Reid's claims. From the Court Decision (PDF): 'We conclude that Reid produced sufficient evidence that Google's reasons for terminating him were untrue or pretextual, and that Google acted with discriminatory motive such that a factfinder would conclude Google engaged in age discrimination.' As side notes, helping Reid make his case is CS Prof Norman Matloff, while Google's actions are being defended by Wilson Sonsini Goodrich & Rosati of pretexting-was-not-generally-unlawful fame."

Roland Piquepaille writes "Researchers at UC Davis have used nanocrystals made of diamond-like cubic zirconia to develop cooler fuel cells. Even if hydrogen fuel cells have been touted as clean energy sources, current fuel cells have to run at high temperatures of up to 1,000 C. This new technology will allow fuel cells to run at much lower temperatures, between 50 and 100 C. Obviously, this could lead to a widespread use of fuel cells, which could become a realistic alternative power source for vehicles. The researchers have applied for a patent for their technology, but don't tell when fuel cells based on their work are about to appear."

An anonymous reader writes "California Secretary of State Debra Bowen just announced details about the previously discussed 'top-to-bottom review' of almost all voting and counting systems used in the state. The team features big names in e-voting security: David Wagner, Matt Bishop, Ed Felten, Matt Blaze, and Harri Hursti, among others. Vendors have time to submit their machines including documentation and source code until July 1st or face severe restrictions, including decertification, for the 2008 elections. Scheduled to start next week, the review will include a red-team attack and going through the source code."

Roland Piquepaille writes "If you live near the sea, chances are high that your home is built over sandy soil. And if an earthquake strikes, deep and sandy soils can turn to liquid with disastrous consequences for the buildings built above them. Now, US researchers have found a way to use bacteria to steady buildings against earthquakes by turning these sandy soils into rocks. 'Starting from a sand pile, you turn it back into sandstone,' the chief researcher explained. It is already possible to inject chemicals into the ground to reinforce it, but this technique can have toxic effects on soil and water. In contrast, the use of common bacteria to 'cement' sands has no harmful effects on the environment. So far this method is limited to labs and the researchers are working on scaling their technique. Here are more references and a picture showing how unstable ground can aggravate the consequences of an earthquake."

Roland Piquepaille writes "Chemists from Virginia and California have cooked a soup of fullerenes which produced an improbable buckyegg. The egg-shaped structure of their 'buckyballs' was a complete surprise for the researchers. In fact, they wanted to trap some atoms of terbium in a buckyball "to make compounds that could be both medically useful and well-tolerated in the body." And they obtained a buckyegg which both violates some chemistry laws and the FIFA soccer laws which were used until the last World Cup. Read more for additional references and a picture of this buckyegg carrying metal molecules."

Baldrson writes "The NSF's report titled 'Graduate Enrollment in Science and Engineering Programs Up in 2003, But Declines for First-Time Foreign Students' (a pdf of the report released for the first time last month) is now available online. In an analysis of the report, Edwin S. Rubenstein of ESR Research states of these latest figures: '4.2 percent of science and engineering PhDs work outside their field of training, chiefly for financial reasons. This further weakens corporate America's claim of a shortage of high-tech workers.'" Interesting to see how things have changed since then.

theodp writes "In Johnny Can So Program, CS Prof Norm Matloff calls BS on CNET stories like Can Johnny Still Program? and Can the U.S. Still Compete?, saying it's a shame that CNET fails to cover the real threat to American technological competitiveness, the hidden agendas of Chicken Littles like Jim Foley of the Computing Research Association, David Patterson of the ACM and former Intel CEO Craig Barrett, all of whose organizations have a vested interest in playing the education card."

Tycoon Guy writes "It's official now: UPN has decided to cancel 'Enterprise.' The show's series finale, which may feature Jonathan Frakes (William T. Riker) and Marina Sirtis (Deanna Troi), will air on Friday the 13th of May. The show's fate was probably sealed when last Friday's episode reached only 2.5 million viewers - but even so, the people at EnterpriseFans.com are still trying to raise money for a fan campaign to save the show."

dwheeler writes "It's not often you find a classic, but I think I've found a new classic for software and computer hardware developers. It's David J. Agan's Debugging: The 9 Indispensable Rules for Finding Even the Most Elusive Software and Hardware Problems." Read on for the rest. Debugging: The 9 Indispensable Rules for Finding Even the Most Elusive Software and Hardware Problems author David J. Agans pages 192 publisher Amacom rating 9 reviewer David A. Wheeler ISBN 0814471684 summary A classic book on debugging principles

Debugging explains the fundamentals of finding and fixing bugs (once a bug has been detected), rather than any particular technology. It's best for developers who are novices or who are only moderately experienced, but even old pros will find helpful reminders of things they know they should do but forget in the rush of the moment. This book will help you fix those inevitable bugs, particularly if you're not a pro at debugging. It's hard to bottle experience; this book does a good job. This is a book I expect to find useful many, many, years from now.

The entire book revolves around the "nine rules." After the typical introduction and list of the rules, there's one chapter for each rule. Each of these chapters describes the rule, explains why it's a rule, and includes several "sub-rules" that explain how to apply the rule. Most importantly, there are lots of "war stories" that are both fun to read and good illustrations of how to put the rule into practice.

Since the whole book revolves around the nine rules, it might help to understand the book by skimming the rules and their sub-rules:

1. Understand the system: Read the manual, read everything in depth, know the fundamentals, know the road map, understand your tools, and look up the details.
2. Make it fail: Do it again, start at the beginning, stimulate the failure, don't simulate the failure, find the uncontrolled condition that makes it intermittent, record everything and find the signature of intermittent bugs, don't trust statistics too much, know that "that" can happen, and never throw away a debugging tool.
3. Quit thinking and look (get data first, don't just do complicated repairs based on guessing): See the failure, see the details, build instrumentation in, add instrumentation on, don't be afraid to dive in, watch out for Heisenberg, and guess only to focus the search.
4. Divide and conquer: Narrow the search with successive approximation, get the range, determine which side of the bug you're on, use easy-to-spot test patterns, start with the bad, fix the bugs you know about, and fix the noise first.
5. Change one thing at a time: Isolate the key factor, grab the brass bar with both hands (understand what's wrong before fixing), change one test at a time, compare it with a good one, and determine what you changed since the last time it worked.
6. Keep an audit trail: Write down what you did in what order and what happened as a result, understand that any detail could be the important one, correlate events, understand that audit trails for design are also good for testing, and write it down!
7. Check the plug: Question your assumptions, start at the beginning, and test the tool.
8. Get a fresh view: Ask for fresh insights, tap expertise, listen to the voice of experience, know that help is all around you, don't be proud, report symptoms (not theories), and realize that you don't have to be sure.
9. If you didn't fix it, it ain't fixed: Check that it's really fixed, check that it's really your fix that fixed it, know that it never just goes away by itself, fix the cause, and fix the process.

This list by itself looks dry, but the detailed explanations and war stories make the entire book come alive. Many of the war stories jump deeply into technical details; some might find the details overwhelming, but I found that they were excellent in helping the principles come alive in a practical way. Many war stories were about obsolete technology, but since the principle is the point that isn't a problem. Not all the war stories are about computing; there's a funny story involving house wiring, for example. But if you don't know anything about computer hardware and software, you won't be able to follow many of the examples.

After detailed explanations of the rules, the rest of the book has a single story showing all the rules in action, a set of "easy exercises for the reader," tips for help desks, and closing remarks.

There are lots of good points here. One that particularly stands out is "quit thinking and look." Too many try to "fix" things based on a guess instead of gathering and observing data to prove or disprove a hypothesis. Another principle that stands out is "if you didn't fix it, it ain't fixed;" there are several vendors I'd like to give that advice to. The whole "stimulate the failure, don't simulate the failure" discussion is not as clearly explained as most of the book, but it's a valid point worth understanding.

I particularly appreciated Agans' discussions on intermittent problems (particularly in "Make it Fail"). Intermittent problems are usually the hardest to deal with, and the author gives straightforward advice on how to deal with them. One odd thing is that although he mentions Heisenberg, he never mentions the term "Heisenbug," a common jargon term in software development (a Heisenbug is a bug that disappears or alters its behavior when one attempts to probe or isolate it). At least a note would've been appropriate.

The back cover includes a number of endorsements, including one from somebody named Rob Malda. But don't worry, the book's good anyway :-).

It's important to note that this is a book on fundamentals, and different than most other books related to debugging. There are many other books on debugging, such as Richard Stallman et al's Debugging with GDB: The GNU Source-Level Debugger. But these other texts usually concentrate primarily on a specific technology and/or on explaining tool commands. A few (like Norman Matloff's guide to faster, less-frustrating debugging ) have a few more general suggestions on debugging, but are nothing like Agans' book. There are many books on testing, like Boris Beizer's Software Testing Techniques, but they tend to emphasize how to create tests to detect bugs, and less on how to fix a bug once it's been detected. Agans' book concentrates on the big picture on debugging; these other books are complementary to it.

Debugging has an accompanying website at debuggingrules.com, where you can find various little extras and links to related information. In particular, the website has an amusing poster of the nine rules you can download and print.

No book's perfect, so here are my gripes and wishes:

1. The sub-rules are really important for understanding the rules, but there's no "master list" in the book or website that shows all the rules and sub-rules on one page. The end of the chapter about a given rule summarizes the sub-rules for that one rule, but it'd sure be easier to have them all in one place. So, print out the list of sub-rules above after you've read the book.
2. The book left me wishing for more detailed suggestions about specific common technology. This is probably unfair, since the author is trying to give timeless advice rather than a "how to use tool X" tutorial. But it'd be very useful to give good general advice, specific suggestions, and examples of what approaches to take for common types of tools (like symbolic debuggers, digital logic probes, etc.), specific widely-used tools (like ddd on gdb), and common problems. Even after the specific tools are gone, such advice can help you use later ones. A little of this is hinted at in the "know your tools" section, but I'd like to have seen much more of it. Vendors often crow about what their tools can do, but rarely explain their weaknesses or how to apply them in a broader context.
3. There's probably a need for another book that takes the same rules, but broadens them to solving arbitrary problems. Frankly, the rules apply to many situations beyond computing, but the war stories are far too technical for the non-computer person to understand.

But as you can tell, I think this is a great book. In some sense, what it says is "obvious," but it's only obvious as all fundamentals are obvious. Many sports teams know the fundamentals, but fail to consistently apply them - and fail because of it. Novices need to learn the fundamentals, and pros need occasional reminders of them; this book is a good way to learn or be reminded of them. Get this book.

If you like this review, feel free to see Wheeler's home page, including his book on developing secure programs and his paper on quantitative analysis of open source software / Free Software. You can purchase Debugging: The 9 Indispensable Rules for Finding Even the Most Elusive Software and Hardware Problems from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

MissMarvel writes "A company claims to have a safer way to dispose of cows infected with Mad Cow Disease. It says that by using the kinds of chemicals that go into a drain-clearing product such as Drano, they can safely break down the suspected disease-causing proteins, known as prions. The bodies of infected dead cattle are usually burned to destroy proteins these brain-wasting compounds."

Dan writes "Adam Getchell has published instructions on installing Tomcat on OpenBSD in the form of install logs. The config is setup as non-root so that anyone can start/stop Tomcat. He has not tried loading any EJB's and is playing with Cocoon to make the setup work with XML publishing framework. Adam is looking for feedback relating to his setup."

I am Jack's username writes "The New York times has an article (no registration required) about an increase in profound autism in California of 273% between 1987 and 1998. Between 1999 and 2001 more than 6 500 cases were reported, similar to the number reported between 1970 to 1995. The increase cannot be accounted for by misdiagnosis, increased awareness, childhood immunizations, emigration, birth injuries, and genetics. Some autism experts think the actual cases to be dramatically more than reported in the UC study. See also previous discussions about high-function geek rich areas like silicon valley."

Gabe writes "Looks like the NWN linux client page has been updated with screenshots!. Finally, some decent proof that Bioware is coming through for us linux folks. Maybe it's time to open my copy soon :)" My replacement CPU fan is here, so I theoretically can now play NWN. Can't wait for the good modules to start being developed. In the meantime, we should use it as the prettiest IRC server ever... where you can kill your friends instead of just kickbanning them :)

Octothorp writes: "Though not as complicated as the underwater vehicles. There is an annual competition sponsored by National Semiconductors to build an autonomous race car. They move along pretty well too, at almost 9 ft/s. More technical information on how they are built is available on a Berkeley page, and there's a video of the winning run for 2002."

RukhWunder asks: "I have two computers and one USB printer. Is there a USB splitter or something around so I can connect them both to the printer? Networking the computers is out of the question because they are on the university network already." There was an earlier question about USB on KVM switches that was done last year, however I too would be curious to note if there are switches for just USB devices.

madlinguist writes: "Researchers connected with Stanford's Applied Crypto Group have developed a new method of identity-based encryption from spending too much time with ellipses. Named after two of the researchers, the Boneh-Franklin project was presented at Crypto 2001, where these researchers encouraged the crypto community to crack their open-source system. Best of all, the project's homepage allows you to try it on your own email address."

Robber Baron writes "While searching with Copernic for the old Indian-head test pattern, I chanced upon this article (funny how search engines work, isn't it?). It seems (surprise, suprise) that this whole IT labour shortage crisis was a myth generated by large IT companies to justify importing boatloads of foreign IT workers willing to work for low wages in substandard conditions. Anyone have any experience with this?"

Sergio Lucero writes "The Proceedings of the National Academy of Science (PNAS) just published an article on the use of 3D microfluid networks as computers for the solution of very hard (NP) mathematical problems. So far it looks like they've solved a specific case of the maximum clique problem, but of course this also means they can do other stuff."

dwalker asks: " I found a disturbing manifesto while I was investigating the H-1B situation. Dr. Norman Matloff is a computer science teacher at UC Davis and he makes some radical claims about the tech industry including , 'Rampant age discrimination...at age 35', H-1B workers as cheap labor and 'Indentured Servants' , and he claims that there is no labor shortage. His testimony was presented to the U.S House Subcommittee on Immigration in 1998 right before the last H-1B visa increase. Plus he has quotes and documentation to back up his claims, everything from personal e-mail to articles in the Washington Post. I'm not in the workforce yet but if this guy is right my CS Degree isn't gonna mean much. I'm curious what the tech community at large thinks of this guy and his claims, especially now after 2 years?"

JeffL sent us a link to Builder.com where you can read Dan Schafer's latest revelation about Linux:It doesn't have GUI web tools. I don't see it as a huge problem (see Slashdot? I use vim5, and vim5 alone :) but it is definately a problem for newbies. NS Composer just doesn't cut it most of the time, and there aren't any other real options.

Ron Lal writes "Wired news is reporting ("Too Experienced to Get a Job?" Link) that the software industry is "not friendly to older" programmers. UC Davis professor interviewed in 'There is No Desperate Labor Shortage' (link). He claims ("Debunking the Myth of a Desperate Software Labor Shortage" link) that programmers not fluent in the latest programming flavor of the month are having trouble finding jobs. I would like to know how slashdor.org readers feel about this issues and if any readers had an recent experience looking for jobs."

Joe Vigneau and Bill Broadley sent us info about Cobalt Microserver's brand new workgroup server. It's a 133mhz RISC box that runs Linux, has all the normal servers (www, email etc), and costs under $1000. And it supposedly fits in a 7" cube!