Microsoft Security Makes "Worst Jobs" List

Stony Stevenson asks, rhetorically, "What do whale-feces researchers, hazmat divers, and employees of Microsoft's Security Response Center have in common? They all made Popular Science magazine's 2007 list of the absolute worst jobs in science." Quoting: "The MSRC ranked near the middle as the sixth-worst job in this year's list.. 'We did rate the Microsoft security researcher as less-bad than the people who prepare the carcasses for dissection in biology laboratories,' Moyer said. Moyer didn't have to think long when asked whether he'd rather have the number 10-ranked whale research job. 'Whale feces or working at Microsoft? I would probably be the whale feces researcher,' he said. 'Salt air and whale flatulence; what could go wrong?'" Here's the Popular Mechanics list all on one page.

Comments

Time to rethink OS's

[Tablizer]

When staff is short I am sometimes stuck with help-desk duties of late. I am appauled by the lack of transparency when trying to troubleshoot Windows. There is no easy way to "X-ray the pipes" to see what is going in and out and where it is getting stuck. Thus, one ends up having to play Sherlock Holmes to figure out the crime based on random clues scattered here and there. One cannot open the blackbox, but rather has to tweak the front knobs, trying a Cartesion Join of all possible combos, or at least a random sample as an approximation.

It does not have to be this way. The OS should be broken up into fairly independent services and the protocol of each service known, shown, and loggable. One could thus isolate oddities. If a peice of software I build constantly has problems (or confusion) with certain processes or steps, I make trace modes and special reports that can echo and document the process as it is taking place. OS's don't seem to be built this way, you have to randomly tweak stuff until the problem (hopefully) goes away. It is like banging the Mellenium Falcon when it stalls. In the digital age I am stuck with analog-like troubleshooting techniques.

Re:Time to rethink OS's

[jimicus]

So your solution to any random problem is "run it under a debugger"?

Would it really be so hard for the software writers to, oh, I don't know, USE THE LOGGING FACILITIES THAT ARE BUILT INTO THE OPERATING SYSTEM??. Windows has a perfectly good Event Viewer and APIs for writing to it, so how come hardly any software ever logs what it's doing?

Re:Time to rethink OS's

[Have Blue]

Because fucking around with the command line is so much easier and more intuitive than having the error message read "This disk cannot be unmounted because a file on it is in use by the program named ______________ ".

Misnomer

[DynaSoar]

I know science. I do science. Microsoft security response is not science. It's the intelligent design contingent of the IT world. It can call itself science all it wants but it can't act like science. Sooner or later they'll tell you that you just have to believe them, while they're busily cooking up the next, more complicated batch of the same old same old and collecting more people with impressive credentials to preach it at you.