Slashdot

I spent two years of my life post-graduate school working at DoD research laboratories, and can say with some experience why Geeks should not join DARPA (or any government research lab). It can be summed up in one word: "research."

Government labs no longer do the stuff for the most part. There are still some pockets left, but they are few and far between, and shrinking. I graduated with a MS in computer science, with a two-year focus on computer security. I was offered a job in a research team with with a DoD lab and eagerly took it. But it wasn't research. It was contract management. Essentially, I got to read research proposals from companies, and decide whether or not those companies would be funded for their ideas. My ability to influence the actual research of the companies was quite limited. I was able to come up with 'calls for proposals,' that is, statements of new topics that we'd like proposals on from companies. By the time these ideas were raped^Wvetted by the various program and contract managers, the descriptions were so incredibly vague that the proposals received in response to the call were completely off-topic. I got frustrated very early on and left.

In my exit interview, I asked my supervisor to define research. His definition was adequate. I then asked him if that's what we did. He stammered a bit, and ultimately conceded that we, "facilitated research." We had a very interesting discussion. Due to research project overruns throughout the 80s, particularly with software projects, as well as the end of the Cold War, the Congress changed the focus of DoD research programs. New funding rules dictate that research projects are placed under contract. In this way, if a company is paid to do research and development on a project, and it fails to deliver, the government has some recourse. If actual government employees received funding and failed, there would not be much that congress could do to them (Congress could slash the non-salary portions of the failed project's budget, but that's not very intimidating to the employees when you think about it).

The place where the 'cool' stuff happens these days is by the contractors. If you want to work on ARPA and DARPA quality work, start a small business and start winning on SBIR awards. I wouldn't recommend actually working for DARPA or a government research lab, though, unless you really want to be a contract manager and not be very hands-on with technology and ideas.

Shipwack writes "Tens of millions of internet users across the Middle East and Asia have been left without access to the web after a technical fault cut millions of connections. The outage, which is being blamed on a fault in a single undersea cable, has severely restricted internet access in countries including India, Egypt and Saudi Arabia and left huge numbers of people struggling to get online. Observers say that the digital blackout first struck yesterday morning, with Egypt's communications ministry suggesting it was caused by a cut in a major internet pipeline linking it to Europe."

jcatcw writes "Computerworld reports, "Network Appliance Inc. today announced that it has filed a patent infringement lawsuit against Sun Microsystems Inc. seeking unspecified compensatory damages and an injunction that would prohibit Sun from developing or distributing products based on its ZFS file system technology. The suit, filed in the U.S. District Court in Lufkin, Texas, charges that the Sun ZFS technology infringes on seven NetApp patents pertaining to data processing systems and related software.""

http://soundproofingwithdave.com/2007/06/soundproofing-exterior-door.html

Astronomers are surprised by a recent discovery of a space hole that is nearly a billion light years across. "Not only has no one ever found a void this big, but we never even expected to find one this size," said researcher Lawrence Rudnick of the University of Minnesota. Rudnick's colleague Liliya R. Williams also had not anticipated this finding. "What we've found is not normal, based on either observational studies or on computer simulations of the large-scale evolution of the universe," said Williams, also of the University of Minnesota."

munchola writes "The Software Freedom Law Center has declared that Microsoft's patent pledge to open source developers is 'worse than useless'. SFLC chief technology officer, Bradley Kuhn, has written to FOSS developers warning them that 'developers are no safer from Microsoft patents now than they were before'. According to Kuhn: 'The patent covenant only applies to software that you develop at home and keep for yourself; the promises don't extend to others when you distribute. You cannot pass the rights to your downstream recipients, even to the maintainers of larger projects on which your contribution is built.'"

Many readers wrote in to make sure we know that Microsoft execs have signed off on the code and Windows Vista has been and released to manufacturing. As APC put it, "It's good to go — or as good as it is going to be until the first round of patching begins." CNN has a good roundup of Vista's long development history.

An anonymous reader writes, "Novell has published additional details about its agreements with Microsoft concerning Windows and Linux interoperability and patents. It seems the company is receiving an up-front payment of $348 million from Microsoft, for SLES subscription certificates and for patent cross-licensing. Microsoft will make an upfront payment to Novell of $240 million for SLES subscription 'certificates' that Microsoft can use, resell, or distribute over the term of the agreement. Regarding the patent cooperation agreement, Microsoft will make an up-front net payment to Novell of $108 million, and Novell will make ongoing payments totaling at least $40 million over five years to Microsoft."

An anonymous reader writes "Microsoft has launched the sixth edition of their embedded OS Windows CE and this time has included the full source. From the article: 'Developers can now access shared source code for the Windows CE kernel -- as well as certain device drivers and application-level components -- directly from within the Windows Embedded CE 6.0 distribution package. To do this, they click on a function in the IDE that installs the shared source, and indicate their acceptance of the associated shared source license.'"