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.
Many years ago in my former career I had to treat a guy who had been in a ditch comotose for so long he had maggots well established in every available cavity. Took a while that did.
Not, it has to be said, my fondest memory of that time. It ranks right up there with the odd fact that all tramps poo contains giant lentils.
I work in a hospital, and ER docs like to swap stories. The worst I've heard is of a woman who was kidnapped, beaten, repeatedly raped, and thrown into a ditch to die. She didn't die, but she did land on a fire ant mound, where she stayed until someone found her, which was not enough time for her to die. Tragedy happens, crime happens, but sometimes you just have to think "that's not fair." I always think of that story when I hear someone say "well, everything happens for a reason."
About 70% of the people who are released from death row after being exonerated by DNA evidence were convicted on eyewitness testimony. The death penalty is bad because witnesses lie or are mistaken, cops lie or are mistaken, cops torture/beat confessions out of people, jailhouse snitches are allowed to testify to reduce their own sentence, evidence is planted (or hidden, if exculpatory), and so on.
We think we have a god's-eye view and we just know that someone is guilty, but the case is stacked to look that way, and we don't really know, not definitively. Very seldom is there videotape of a crime like this--usually we have to rely on people whose careers are built on getting an arrest and a conviction. People will send you to death row just to help their own careers, even if they have to intimidate witnesses, supress contradictory testimony, or reduce someone else's sentence for their "testimony" about the night you confessed to them.
Is threefold: 1) Because Windows is so prevalent it gets hit with more attacks than anything else.
2) Along those lines, it always makes the news, at least tech news, when there's a Windows bug. If you read security focus or the like you discover there's really quite a bit discovered in all OSes, including MacOS, Linux, Solaris and so on. However it rarely hits tech news and almost never mainstream. No such luck for MS.
3) People like to blame all their problems on MS. You get hacked because your password was
2. Oceanographer: Oceanographers' jobs are "getting harder and harder every year," said Ward. Faced with the predictions that by 2048 seafood will no longer exist, coral reefs will vanish in the next decade and that an ever expanding mass of garbage the size of Texas in the North Pacific has caused irreparable damage to the world's water supply, these scientists are charged not only with protecting the health of the ocean, but also with turning the prognosis around.
"Oceanographers are really tasked with just analyzing sad facts on deoxygenating oceans, increased pollution, whole masses of garbage swirling in the middle of the ocean. What it really is, is a testament to how devoted and loyal a bunch of people they are.
"They're working extremely hard on a very difficult problem, but they also are very optimistic people. They believe that we can turn it around and the ocean is a very dynamic living environment and they feel that with the proper care, we can turn it around, but so far that has not been the case," said Ward.
That struck me as odd too...according to the article it's due to the amount of "bad news" that oceanographers have to deal with (overfishing, pollution, etc.):
With so much going on, there's plenty of work for oceangoing scientists--if they can stomach bad news.
That's a stretch in my book, *everybody* has to deal with that bad news, the oceanographers just deliver it - while cruising the world's oceans on state of the art research vessels...
Oceanographers are dedicated to the study and, ideally, salvation of numerous aquatic ecosystems that are in a rapid state of collapse. It's one thing to deal with "bad news" on a regular basis. It's quite another to watch the sea dying right before your eyes. Most of us have become comfortable with our oceans' plight by ignoring it; that is a comfort not easily afforded to oceanographers.
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.
OS's don't seem to be built this way, you have to randomly tweak stuff until the problem (hopefully) goes away.
I never just randomly tweak stuff until the problem goes away. I don't use Windows or OS X though so pretty much everything I use is open source and reasonably well documented. {Open,Free}BSD, Solaris and Linux is built much the way you describe. Important aspects of the OS (using the term loosely) are almost always broken down into relatively small, independent services that have established
The OS should be broken up into fairly independent services and the protocol of each service known, shown, and loggable.
Trouble is, that model's incompatible with Microsoft's business, and it's customers' requirements for DRM.
They need the OS to be black boxed and inscrutable to prevent people hacking things like WGA and product activation. They also need obfuscated protocols and formats to stop people like WINE from reverse engineering their APIs.
The clearer and easier to understand MS makes it's system, the worse it is for their business model. That's why there's no way they'll do as you suggest, despite being ordered to by the DOJ and the EU.
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 lik
Every now and then my harddrive will start whirring away, when it shouldn't be, and as far as I can tell there is no easy way to tell which process is the culprit in XP. Hell, you ever get one of those "this file is being used by another program" messages and have no idea what program is responsible? I've had to boot into safe mode just to delete a file. And it was an.avi not a system file or anything.
I've gotten that in Ubuntu Feisty though. "This disk cannot be unmounted because a file on it is in use." When the only stuff on it is media that's not open.
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 ______________ ".
I really like Unlocker [ccollomb.free.fr]. A little freeware explorer extension that shows you what processes have locked a file, and lets you choose what to do about it.
While it is true that there is no real way to "X-ray the pipes" here are the tools the Microsoft Technet guys use and I've found can be very good at hunting down the bugs.http://www.microsoft.com/technet/sysinternals /default.mspx [microsoft.com]
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?
Because more windows programmers are not engineers. They want to get it done as fast as possible with as little understanding as possible.
So when they can be bothered to log an error, it's usually done after the programmer looks for the word 'write' in the help system.
Every shop bigger then 20 people I ahve worked at is like this, very few of us actually study the OS. Of course, it is possible thatevery place I have been at is the exception.
Mostly Linux. For application logging, while the OS provides a logging facility through syslog, it's down to an application (such as Apache or OpenLDAP or Postfix or what have you) to actually use it - the OS doesn't force the issue. Thankfully, most Unix applications are actually pretty good at doing so therefore getting everything configured properly is seldom a big deal - you can just check what went wrong in the logs.
Windows has a logging facility as well, but it's remarkable how few things actually use
I'm starting to wonder if Mike Judge's 'Idiocracy' may have been a serious film. The articles that make it to the front page on this site have gotten progressively worse over the years.
I fully expect a 'Microsoft = Ass' article by 2010.
Am I the only one who thinks those jobs sound fairly interesting? The NASA 0g tester would be miserably boring but it pays great, over 120k for 21 days of work. All the other jobs seem pretty interesting and don't seem to be exceedingly dangerous. Considering this is their "worst" job list, I'd love to see their "best" job list.
Hmm, where did it say $120,000 for 21 days work? What I read said $6,000.
Even $120,000 might not be worth it. I can't imagine how difficult it would be to use a bedpan in a bed sloped 6 degrees toward my head, let alone while being observed by NASA engineers.
Plus, to most hackers, crippling Microsoft is the geek equivalent of taking down the Death Star
Umm... is there a NON-geek equivalent to "taking down the Death Star"? I would have thought that particular analogy wouldn't transfer into non-geek realms...
"'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?'""
Quite a lot if your standing near a naked flame when one of them big boys "Breach" 0.o
Seems to me, with the depth of exploits coming in, you could learn so much from working that job, after a few years you could write your ticket to a good job in security at another company.
Not sure Id call a hardworking job like that a bad job, digging in a whale or crap would be allot worse....
why would you need to? i know people who have worked for MS and they all say it's a brillant place to work. highly paid as well. i don't by that MS security is a bad place to work, in fact a lot of these are crap examples of a bad job. ones i will pay are hazmat diving for the danger factor and 0g tester for sounding like some kind of middle eastern torture method.
You have to realize that Slashdot is filled to the brim with users that follow stereotypes. There are no leaders here. Only followers. They don't know about the concept of thinking for themselves.
Microsoft on your resume, yes, that would be one of the best possible things you could ever have on an IT resume as previous job experience. Anyone in IT with common sense would kill for that job, if only to have it on his or her resume.
If anyone doesn't agree with that, they lose all credibility.
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.
I was also wondering since when solving your self-created problems had become science... Oh, wait, maybe they have a point;) In any case, I would call it engineering. Or just support. It's not easy work, I wouldn't say that, but science it is not. I think the difference lies in the point that science pursues the mostly detailed understanding of something with not so much a time pressure (just think about it: can you plan scientific progress in advance? On week 4 we will discover this-and-this?), whereas th
Maybe Mike Rowe of "Dirty Jobs" on the Discovery Channel can spend a day working at MS. It might top the time he had to wade through 3 feet of bat shit. I understand Ballmer goes bat shit all the time over there at MS. Of course, they might not let a fellow named Mike Rowe into their facilities after someone pulled this cute little trick. [cnn.com]
Plus, to most hackers, crippling Microsoft is the geek equivalent of taking down the Death Star,
Really? I'd think it's more like kicking an evil, rabid puppy. I mean, sure, it is an evil little bastard and probably deserves to be kicked...but it's still kicking a puppy, and it's still not something to be especially proud of.
Odd... (Score:5, Interesting)
Re:Odd... (Score:5, Funny)
Dissect a bloated carcass.
No, sorry. That was the whale guys, wasn't it?
Parent
close... (Score:5, Funny)
No, that was the biology lab preparers.
The Microsoft guys deal with shit, and are in over their heads.
Oh, wait. THAT was the whale guys!
Parent
Re:Odd... (Score:5, Funny)
Parent
Re:Odd... (Score:5, Funny)
Parent
Re:Odd... (Score:4, Funny)
- Sell fresh exploits on the open market.
- Resign and start their own bulk-email service companies.
Parent
I call whaleshit (Score:5, Informative)
For giggles, here's the list:
Re: (Score:2, Insightful)
Re:I call whaleshit (Score:5, Funny)
They're the ones who work for the TSA who allow you to get on a plane, right?.
Parent
Forensic Entomologist I can relate to, sorta (Score:5, Interesting)
Not, it has to be said, my fondest memory of that time. It ranks right up there with the odd fact that all tramps poo contains giant lentils.
Parent
Re:Forensic Entomologist I can relate to, sorta (Score:5, Interesting)
Parent
Re:Forensic Entomologist I can relate to, sorta (Score:5, Interesting)
We think we have a god's-eye view and we just know that someone is guilty, but the case is stacked to look that way, and we don't really know, not definitively. Very seldom is there videotape of a crime like this--usually we have to rely on people whose careers are built on getting an arrest and a conviction. People will send you to death row just to help their own careers, even if they have to intimidate witnesses, supress contradictory testimony, or reduce someone else's sentence for their "testimony" about the night you confessed to them.
Parent
The reason I'd say it is worse (Score:3, Insightful)
1) Because Windows is so prevalent it gets hit with more attacks than anything else.
2) Along those lines, it always makes the news, at least tech news, when there's a Windows bug. If you read security focus or the like you discover there's really quite a bit discovered in all OSes, including MacOS, Linux, Solaris and so on. However it rarely hits tech news and almost never mainstream. No such luck for MS.
3) People like to blame all their problems on MS. You get hacked because your password was
Re:I call whaleshit (Score:5, Interesting)
2. Oceanographer: Oceanographers' jobs are "getting harder and harder every year," said Ward. Faced with the predictions that by 2048 seafood will no longer exist, coral reefs will vanish in the next decade and that an ever expanding mass of garbage the size of Texas in the North Pacific has caused irreparable damage to the world's water supply, these scientists are charged not only with protecting the health of the ocean, but also with turning the prognosis around.
"Oceanographers are really tasked with just analyzing sad facts on deoxygenating oceans, increased pollution, whole masses of garbage swirling in the middle of the ocean. What it really is, is a testament to how devoted and loyal a bunch of people they are.
"They're working extremely hard on a very difficult problem, but they also are very optimistic people. They believe that we can turn it around and the ocean is a very dynamic living environment and they feel that with the proper care, we can turn it around, but so far that has not been the case," said Ward.
Parent
Re: (Score:2, Insightful)
Re: (Score:3, Insightful)
Some people put their hearts into their jobs.
Re:I call whaleshit (Score:5, Interesting)
Parent
link to the article on popsci (Score:2)
http://www.popsci.com/popsci/science/0203101256a23 110vgnvcm1000004eecbccdrcrd.html [popsci.com]
Time to rethink OS's (Score:5, Insightful)
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: (Score:2)
I never just randomly tweak stuff until the problem goes away. I don't use Windows or OS X though so pretty much everything I use is open source and reasonably well documented. {Open,Free}BSD, Solaris and Linux is built much the way you describe. Important aspects of the OS (using the term loosely) are almost always broken down into relatively small, independent services that have established
Re:Time to rethink OS's (Score:5, Interesting)
Trouble is, that model's incompatible with Microsoft's business, and it's customers' requirements for DRM.
They need the OS to be black boxed and inscrutable to prevent people hacking things like WGA and product activation. They also need obfuscated protocols and formats to stop people like WINE from reverse engineering their APIs.
The clearer and easier to understand MS makes it's system, the worse it is for their business model. That's why there's no way they'll do as you suggest, despite being ordered to by the DOJ and the EU.
Parent
Re: (Score:2)
Re:Time to rethink OS's (Score:4, Interesting)
Parent
Re: (Score:3)
Re:Time to rethink OS's (Score:5, Informative)
man lsof
hth
Parent
Re:Time to rethink OS's (Score:5, Insightful)
Parent
Re:Time to rethink OS's (Score:5, Informative)
It also has an option to replace TaskManager, which is very handy...
Parent
Unlocker (Score:3, Informative)
I really like Unlocker [ccollomb.free.fr]. A little freeware explorer extension that shows you what processes have locked a file, and lets you choose what to do about it.
Re: (Score:2)
Unfortunately it's practically impossible to make that 100% and still hold down a job in IT, but it's quite possible to get to the 80-90% point.
Re: (Score:3, Informative)
Re:Time to rethink OS's (Score:5, Insightful)
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?
Parent
Re:Time to rethink OS's (Score:4, Insightful)
So when they can be bothered to log an error, it's usually done after the programmer looks for the word 'write' in the help system.
Every shop bigger then 20 people I ahve worked at is like this, very few of us actually study the OS. Of course, it is possible thatevery place I have been at is the exception.
Parent
Re: (Score:3, Insightful)
For application logging, while the OS provides a logging facility through syslog, it's down to an application (such as Apache or OpenLDAP or Postfix or what have you) to actually use it - the OS doesn't force the issue. Thankfully, most Unix applications are actually pretty good at doing so therefore getting everything configured properly is seldom a big deal - you can just check what went wrong in the logs.
Windows has a logging facility as well, but it's remarkable how few things actually use
Popular Science and Popular Mechanics (Score:3, Informative)
Juvenile and unfunny (Score:2, Insightful)
I fully expect a 'Microsoft = Ass' article by 2010.
Re: (Score:3, Interesting)
After reading this, I fully expect one by lunchtime tomorrow.
They don't sound so bad... (Score:3, Interesting)
Re: (Score:2, Informative)
Even $120,000 might not be worth it. I can't imagine how difficult it would be to use a bedpan in a bed sloped 6 degrees toward my head, let alone while being observed by NASA engineers.
Umm... wait a minute... (Score:2, Funny)
Uh.... (Score:4, Insightful)
So why on earth would anyone be sterilizing an endangered species? How to make a situation worse, or what?
Re:Uh.... (Score:5, Funny)
I just wanted them to get some practice before they did mine.
Parent
Re: (Score:2, Funny)
i also love how that page is titled "dicks"
What could go wrong? (Score:2)
Quite a lot if your standing near a naked flame when one of them big boys "Breach" 0.o
Humm. (Score:2)
Not sure Id call a hardworking job like that a bad job, digging in a whale or crap would be allot worse....
Re:Humm. (Score:4, Interesting)
Parent
Re: (Score:3, Insightful)
Microsoft on your resume, yes, that would be one of the best possible things you could ever have on an IT resume as previous job experience. Anyone in IT with common sense would kill for that job, if only to have it on his or her resume.
If anyone doesn't agree with that, they lose all credibility.
Misnomer (Score:5, Insightful)
Re: (Score:3, Interesting)
Mike Rowe (Score:5, Funny)
Taking Down The Death Star? (Score:4, Funny)