And this...
With a cost of 140 million dollars USD.
...is a sentence fragment.
It's all just one big.
That's how I talk you insensitive.
It's not as simple as that. If you've a shop with thousands of workstations deployed and you add another point of failure (simple bios setting in the TFA's example) on PCs that may be deployed for years, you've got yet ANOTHER thing that can go wrong if the bios settings get lost. I'd like to see $help_desk walk someone through changing the bios settings. That machine is going to need a visit from a $pendy tech. And, oh yeah -- update the SOP for new PC deployment and make sure everyone signs off and follows it.
In a SMALL shop, this isn't really a problem. It's not unlikely that there's as many different hardware flavors as there are total PCs. But in a LARGE shop, PC UNIFORMITY saves time and money.
It's enough to justify the groans from his co-workers...
Me thinks you don't understand mass deployments. The help desk would never have to walk someone though modifying the BIOS because the computer would never be deployed if it wasn't changed before hand. I've had to work in many multi-thousand PC shops and we had to modify some of the BIOS settings on computers as we deployed them using a standardized image. We just made sure to make the changes as we unboxed and prepped them. If you're deploy techs aren't thorough enough to check that the PC boot BEFORE they deploy it then you have bigger problems that making changes to the BIOS.
Because the Do Not Call list worked out so well
I'm curious, what are the penalties for the second violation and third violation of killing someone on the list? Are they as sever as the Do Not Call list penalties?
You don't think "defense contractors" means they only defend, do you?
The best defense is a good offense.
To do nothing is to be nothing.