That's not from contaminated grain, that's possibly related to the use of leftover CORN (not barley) fed to PIGS (not cows) from ethanol producers. Meanwhile, it isn't a human health issue and they found a way to mitigate it. All without any input from the FDA.

Grain products cannot carry mad cow. That comes from feeding beef byproducts to cows. You won't find e-coli there either, if there had been any, it would be killed in the process of making the wort.

As for the fungal issue, that actually was a problem and it killed hundreds, you apparently know about it, yet you deny it was an issue?!?

So perhaps they should focus on something that is PROVEN to be a problem rather than something that has never been over several decades. They were free to inspect the compounding pharmacies at any time, they just didn't do it. NECC was already in violation of existing law, there was no need for ex post facto anything to punish them, just enforcement of existing law.

When you can show me how a few tons ton of contaminated grain not destined for human consumption can damage a large area of the U.S. beyond repair, I will reconsider.

*I* am? *MY* guy?

Obama was better than Romney mostly because if I'm on the road to hell, I'd like to go slowly. Unfortunately, he hasn't managed to accomplish what he was supposed to, but it's still better than if Romney had achieved what he was supposed to.

But as a whole, the Democrats are more a moderate right than they are left, and both parties are too high on the authoritarian axis for my tastes (and the R's BTW are more authoritarian than the Ds, just about different things).

In some cases, we need less regulation, in others more. Most of all we need better and more sensible regulation that wasn't bought by the regulated.

Feel free to queue up the DOD and NSA for curbing. DOJ and FBI just need paddling.

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.

Density is 100% genetic. Sativas will produce fluffy buds no matter how much light you throw at them.

http://imgur.com/5mhBwQh

Here's an autoflower - Think Different strain. from a 200w LED, that's an easy pound plus harvest right there.

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.

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.

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.