If what they claim is true they'd be weighing the passengers (and charging by the ounce).
Consider what would happen if they did try to weight passengers.
On average men weight more than women. They would be sued for discriminating against men because they would be charged more.
On average obese people weight more than the non-obese. The obese would sue under the ADA.
I honestly don't know if different races happen to have different weights (though it appears that Asiatic races on average weight less than westerners) but think of the number of lawsuits that would ensue if the statistics showed that certain races were being charged more than others.
The lawsuits may not have any merit, but any cost savings they could get from charging based on passengers' weights would be offset by the attorney fees, let alone settlements. Even if weighing passengers would itself make sense in the end it would be foolish of them to try.
So the upshot was that the company's strict security policy resulted in all their classified source code being put onto what was a lot less secure box.
No, the user deciding that he was too important to follow the rules resulted in all their classified source code being put onto what was a lot less secure box. Maybe the app process approval was Byzantine, but if you don't like the rules you find another internship.
Assuming we are talking about the defense contractor SAIC it is possible that the application approval process was insisted upon by the government. This may not have been the company's policy per se.
As many posters have mentioned security is a matter of economics, i.e., risk/benefit ratios. Releasing of classified materials can have great risks. It is not surprising that stricter security measures are insisted upon.
Anyway, my worst development job was actually my first development job. I was the IT department at a small company that had a dog breeding colony for research purposes. They were using a Wang VS 15 to run the colony. As some of you may know, it was a Cobol machine, and wasn't y2k compatible. In fact, because of hardware limitations, it could not accept dates after December 31, 1999 at all (unless you were to manage to put in a version of *nix, but even then, there was no battery powered internal clock, so you would have to set the time anew every bootup, but I digress).
After Y2K, the company kept using the machine anyway, but also used paper since the mainframe couldn't handle any new records. In 2001, I was given the task of writing a new program, using whatever resources I could scrounge up. They didn't want to pay a real developer to do this (they got a quote for US$70,000, but that was too much for them).
I got some help from an outside developer, but had to do the majority of this myself. Did I mention that I had no education or experience in these matters? Did I forget to mention that the fate if the entire company was put onto my shoulders?
After a year and a half on this, I found out that I was going to be laid off. However, they wouldn't tell me exactly when. I continued to plod along doing this program, until the summer semester started at a local community college. By that time, I had gotten an alpha version ready, as was put to use. Unfortunatly, the people who needed to use it couldn't follow instructions, and I spent alot of time manually fixing the data.
Two weeks after I left, they called me because their backup system wasn't working and they wanted me to come in. I asked them what they were going to pay me. They replied that they weren't going to pay me as I had a moral obligation to fix things that should have stayed fixed after I left.
They still owe me money for vacation pay (which the employee manaul says I'm entitled to, as I gave sufficient notice), and for expenses I foolishly paid for, after being given the assurance that the company would take care of them.
Slashdot Mirror
If what they claim is true they'd be weighing the passengers (and charging by the ounce).
Consider what would happen if they did try to weight passengers. On average men weight more than women. They would be sued for discriminating against men because they would be charged more. On average obese people weight more than the non-obese. The obese would sue under the ADA. I honestly don't know if different races happen to have different weights (though it appears that Asiatic races on average weight less than westerners) but think of the number of lawsuits that would ensue if the statistics showed that certain races were being charged more than others. The lawsuits may not have any merit, but any cost savings they could get from charging based on passengers' weights would be offset by the attorney fees, let alone settlements. Even if weighing passengers would itself make sense in the end it would be foolish of them to try.
So the upshot was that the company's strict security policy resulted in all their classified source code being put onto what was a lot less secure box.
No, the user deciding that he was too important to follow the rules resulted in all their classified source code being put onto what was a lot less secure box. Maybe the app process approval was Byzantine, but if you don't like the rules you find another internship.
Assuming we are talking about the defense contractor SAIC it is possible that the application approval process was insisted upon by the government. This may not have been the company's policy per se.
As many posters have mentioned security is a matter of economics, i.e., risk/benefit ratios. Releasing of classified materials can have great risks. It is not surprising that stricter security measures are insisted upon.
We all know that terrorists are such dedicated family people that they would never use their kids to hide stuff.
Wee! My first /. post!
Anyway, my worst development job was actually my first development job. I was the IT department at a small company that had a dog breeding colony for research purposes. They were using a Wang VS 15 to run the colony. As some of you may know, it was a Cobol machine, and wasn't y2k compatible. In fact, because of hardware limitations, it could not accept dates after December 31, 1999 at all (unless you were to manage to put in a version of *nix, but even then, there was no battery powered internal clock, so you would have to set the time anew every bootup, but I digress).
After Y2K, the company kept using the machine anyway, but also used paper since the mainframe couldn't handle any new records. In 2001, I was given the task of writing a new program, using whatever resources I could scrounge up. They didn't want to pay a real developer to do this (they got a quote for US$70,000, but that was too much for them).
I got some help from an outside developer, but had to do the majority of this myself. Did I mention that I had no education or experience in these matters? Did I forget to mention that the fate if the entire company was put onto my shoulders?
After a year and a half on this, I found out that I was going to be laid off. However, they wouldn't tell me exactly when. I continued to plod along doing this program, until the summer semester started at a local community college. By that time, I had gotten an alpha version ready, as was put to use. Unfortunatly, the people who needed to use it couldn't follow instructions, and I spent alot of time manually fixing the data.
Two weeks after I left, they called me because their backup system wasn't working and they wanted me to come in. I asked them what they were going to pay me. They replied that they weren't going to pay me as I had a moral obligation to fix things that should have stayed fixed after I left.
They still owe me money for vacation pay (which the employee manaul says I'm entitled to, as I gave sufficient notice), and for expenses I foolishly paid for, after being given the assurance that the company would take care of them.