It sounds like the building was built in the spirit of it's owner.
What contamination? The grain is heated to 170F long enough to kill anything harmful in it. There has never been a case of this causing a single problem anywhere. Even the FDA admits it doesn't know of any incident that would have been prevented by this proposal. It's like mandatory testing for antimatter contamination in coffee. It never happens.
Perhaps the FDA should focus it's resources on things that have been a problem like fungal contamination in drugs.
Funny thing. I am very much to the left of where we are today, but I oppose the FDA implementing this proposal. The FDA in general needs to be curbed. They have made a pattern of expanding regulation without showing cause while at the same time neglecting and failing at their core mission.
One word: Afghanistan. Hundreds of casualties on his watch. About 2/3 of total Afghanistan casualties are owned by him.
Seems like your boy Obama is in the prosthetics business, too.
LeMessurier and his team worked with Citicorp to coordinate emergency repairs. With the help of the NYPD, they worked out an evacuation plan spanning a 10-block radius. They had 2,500 Red Cross volunteers on standby, and three different weather services employed 24/7 to keep an eye on potential windstorms. Work began immediately, and continued around the clock for three months. Welders worked all night and quit at daybreak, just as the building occupants returned to work. But all of this happened in secret, even as Hurricane Ella, the strongest hurricane on record in Canadian waters, was racing up the eastern seaboard. The hurricane became stationary for about 24 hours, and later turned to the northeast away from the coast. Hurricane Ella never made landfall. And so the public—including the building’s occupants—were never notified.
Until his death in 2007, LeMessurier talked about the summer of 1978 to his classes at Harvard. The tale, as he told it, is by turns painful, self-deprecating, and self-dramatizing--an engineer who did the right thing. But it also speaks to the larger question of how professional people should behave. "You have a social obligation," LeMessurier reminded his students. "In return for getting a license and being regarded with respect, you're supposed to be self-sacrificing and look beyond the interests of yourself and your client to society as a whole.""
I've long thought that it would be good if cargo ships were automated and/or remote controlled. Piloting cargo ships ought to be relatively easy compared to remote piloting drones in combat.
Many are. You set Iron Mike on a course and speed and he follows it. You still, however, need someone on watch to watch for and deal with the inevitable unexpected situation.
This is one of the most often repeated misunderstandings in aviation: the vast majority of crashes is caused by pilots, so we should replace them with automation since that's much more reliable. Errr... no, not by a long shot.
Many good examples snipped
It's certainly a good thing that Darpa is trying to make aircraft automation more reliable, but right now pilots are still by far the most important asset for the safety of an airplane.
You make a number of good points. Automation is great when everything is going well; the biggest problem then with automated systems is boredom or an unwillingness to use the system because they didn't chose that career to simply sit back and watch gauges. Automated systems, when everything is working as planned can often do better than a human imply because they can take many more inputs and respond to them than a human.
However, when sensors start sending conflicting information automated systems start having troubles. They can be designed to ignore signals based on rules but they cannot analyze the situation and decide what is the correct course of action; nor can they take unexpected actions that may correct the problem but were not considered by the system designer or that break the rules set by the designer. The problem then becomes the interface between the operator and the machine. How do you present information and train operators how to respond? Pilot error, or operator error in other industries is often the result of a poor interface coupled with inadequate training that leaves them with a system that cannot respond and unsure of what to do to correct things. Pilots and operators sometimes do boneheaded things that cause accidents; but more often they are lead down a path by systems that fail to provide information in ways that support, rather than hinder, decision making. Years ago when I worked on some control room designs I used some work form the aviation industry that was looking at the questions "Are we giving pilots to much information to help them make decisions in an emergency?" and "Is automation driving confusion in the cockpit?" Questions I found interesting, as both a pilot and industrial plant operator who was now involved in designing the next generation control room. The challenge there was to convince the designers we didn't need more information but better information. Having a thousand gauges, sometimes displaying conflicting information, in an all glass control room didn't help me in an emergency, it just added to the confusion at a time when I needed a half dozen parameters, that I knew were accurate, to decide what to do to deal with the emergency.
In the end "pilot (or operator) error often means "poorly designed system and inadequate training lead the poor person at the controls down the primrose path.
I bought my Focus 2001 keyboard some time in the early '90s because it was cheaper than the IBM but still had clicky keys and a solid feel. I'm using it right now with an AT->ps2 adapter plugged in to a ps2->USB adapter.
The events around Copenhagen - the disclosures of impropriety in merry old England - tend to work directly against your case. The IPCC is corrupt, the hockey stick was cooked up and no amount of propaganda will make that go away.
I have no idea about his ancestry but he's one shitty, vacillating Chief Executive. It's like reliving the Carter years.
I don't trust any device that insists on reporting to 'the cloud' rather than to a machine of my choosing. Even if it says it only reports to the machine of my choosing, I don't really trust that it doesn't also report to 'the cloud'.
The cloud has no legitimate need to know. That's why my 'smart tv' is a laptop loaded with Linux connected to a not so smart TV.
Of course, if someone did that to Apple nearly 20 years ago when the stock was in the toilet but they still had a pile of money they would've pretty seriously screwed themselves. Not saying it's never a right choice to do that but it's not always right either.
true, but they are not in it for the long run. They want to make as much as possible today and move on to the next target. It's not so much whether it is the right or worngthing but "can I make enough money doing this instead of something else?"
Except of course that individual current owners of Yahoo would see that the investors would get a 25% return and figure other people would sell at market and they could hang on to their shares for a while to get a chunk of the 25%. The investors would effectively have to pay a portion of the premium. They would also have to deal with the risk that they put the whole deal together and then someone jumps in and buys out Yahoo for a tiny bit more or that Yahoo directors tank the value through poison pills or other actions in response to their attempt.
Yea, theres a lot of risk in such a move. But an investor need nobly buy enough to force the issue with the board.If someone else pays a premium over what they'd get then they'd happy dump their shares. After all, the name of the game os making money not what is best for Yahoo.