The Windows Shutdown crapfest
Nov. 25th, 2006 07:39 pmThe Windows Shutdown crapfest has been making the rounds, so I thought I'd link to it here.
It's a blog entry by a developer who worked at Microsoft, talking about the insane layers of politics he had to deal with, the gigantic meetings, and the fact that it took him a year to write a few hundred lines of code. He also discussed some of the technical challenges, like how long it would take code to be moved around the repository.
The blogger also admits that not all departments are like this, his may have been an exception to the rule.
It's a blog entry by a developer who worked at Microsoft, talking about the insane layers of politics he had to deal with, the gigantic meetings, and the fact that it took him a year to write a few hundred lines of code. He also discussed some of the technical challenges, like how long it would take code to be moved around the repository.
The blogger also admits that not all departments are like this, his may have been an exception to the rule.
(no subject)
Date: 2006-11-26 01:17 am (UTC)(no subject)
Date: 2006-11-26 02:44 am (UTC)(no subject)
Date: 2006-11-26 06:04 am (UTC)The action taken when pressing that button? Sleep.
Sleeping Vista in a VM in Parallels is equivalent to a freeze requiring a reboot. There's no hardware, and no ACPI, to wake the kernel back up. Oops.
Needless to say, if you Google for the problem, there are already pages showing the unlikely place that the setting that changes the button to do what the pictogram says. Which begs the question: If it's easier to find out how to fix the problem (that shouldn't be there) using the web, isn't there something wrong with the design of the OS?
(no subject)
Date: 2006-11-26 01:28 pm (UTC)(no subject)
Date: 2006-11-26 06:25 pm (UTC)Of course, in Engineering, we just wait until they all go home, work late and get things done when the system isn't watching. :)