A discussion with with Kiran Prasad, Kelly Norton, and Terry Coatta
A discussion with Jeremiah Grossman, Ben Livshits, Rebecca Bace,
and George Neville-Neil
Unless you've taken very particular precautions, assume every Web site you visit knows exactly who you are.
Risk is a necessary consequence of dependence.
A discussion with Jesse Robbins, Kripa Krishnan, John Allspaw, and Tom Limoncelli
Making the case for resilience testing
Failures happen, and resilience drills help organizations prepare for them.
Embracing Failure to Improve Resilience and Maximize Availability
Network Congestion Management
A discussion with Vint Cerf, Van Jacobson, Nick Weaver, and Jim Gettys
A modern AQM is just one piece of the solution to bufferbloat.
Networks without effective AQM may again be vulnerable to congestion collapse.
Under common loads, your real Internet "speed" can easily drop by a factor of ten due to bufferbloat.
File Systems and Storage
A discussion between Kirk McKusick and Sean Quinlan about the origin and evolution of the Google File System
Astronomers are collecting more data than ever. What practices can keep them ahead of the flood?
As storage systems grow larger and larger, protecting their data for long-term storage is becoming more and more challenging.
A Discussion with Nico Kicillof, Wolfgang Grieskamp and Bob Binder
SAGE has had a remarkable impact at Microsoft.
Seeking a middle ground
A user experience designer and a software engineer from SAP discuss the challenges of collaborating on a business-intelligence query tool.
Automated usability tests can be valuable companions to in-person tests.
Clem Cole and Russell Williams discuss Photoshop's long history with parallelism, and what they now see as the main challenge.
Contention for Caches, Memory Controllers, and Interconnects Can Be Alleviated by Contention-Aware Scheduling Algorithms.
What a software-as-a-service provider learned from using an AJAX framework for RIA development
Instead of simply imagining what your users want or need, it's always a good idea to first get their input.
The Google Web Toolkit is an end-run around Web development obstacles.
Lacking proper browser support, what steps can we take to debug production AJAX code?