When debugging hardware drivers, I often have a scope on the interrupt request pin of the hardware under test. This is a strictly hands on deal. What about the placing of your fingers on the chassis to feel for hard disk seeking to see if the system has crashed. I think being a microsoft developer writing hardware drivers and testing remotely would be hell on earth and worth quitting immediately and loudly. I can't believe any sane manager would even consider this for a moment. I actually made it through all these posts, and I am a little nauseous thinking about all the extra time money distraction and effort wasted by moving development servers off site. Being a network communications developer, I cannot imagine trying to administer a network test environment remotely and being subject to multiple cascaded latencies that are confusable with problematic software or hardware delays. It is madness.

Who tested their sites? geeks? Apple's sites overall design suck: one flagrant example of piss-poor design: CSS pages, used to control display in https secure pages, are themselves stored in non-secure areas. So every https request - on the Apple Developer site for example - leads to an end user warning: "This webpage contains content that will not be delivered using a secure HTTPS connection, which could compromise the security of the entire webpage. Display non-secure content?" I spoke to a typical Apple developer whose reply was simply: "yeah, that's not important, it can be safely ignored..." As ever, poor design leads to users have lower performance expectations, hence such shortcuts - a common vector for security breaches.

I voluntarily work 14 hours a day; it doesn't mean I expect anyone else to do the same. Are you suggesting that people should not take breaks, and instead focus on the corporate mission for the entirety of their workday?