This link recently saved by jm on February 10, 2011
This is the future of code review. Commit directly from your git checkout to the Gerrit code-review system; change is immediately web-visible and enters the review workflow; at the same time, Jenkins checks out the proposed change and runs the test suite; once it's approved, it automatically gets checked in. Brilliant!
This link recently saved by jm on January 16, 2011
some amazing details of Stuxnet's apparent background. 'By the accounts of a number of computer scientists, nuclear enrichment experts and former officials, the covert race to create Stuxnet was a joint project between the Americans and the Israelis, with some help, knowing or unknowing, from the Germans and the British.'
This link recently saved by jm on December 02, 2010
huh. Test-driven development is slower than traditional write-first-test-at-the-end development, but it results in less bugs. Grokcode theorise that its big win is amortising the cost of testing throughout the product iteration, hence reducing the temptation to skip testing when the crunch phase happens
This link recently saved by jm on November 16, 2010
This link recently saved by jm on March 01, 2010
This link recently saved by jm on November 25, 2009
This link recently saved by jm on May 18, 2009
James Hamilton, now at Amazon, then at MSN, gives a canonical list of best practices for large-scale operations-friendly server deployments, 'accumulated over many years in scaling some of the largest services at MSN and Windows Live.' a lot of good advice here (via Tony Finch)
This link recently saved by jm on May 09, 2009