Will Hurd Quotes

A lot of times, the internal R&D doesn't pan out. You go down one route, you find that it doesn't work the way you planned, and you have to switch and go down another one.

When you make content, you try things, and they don't always work. You learn from it and figure out what's next.

One experiments and has to choose always the best results.

More can be learned from what works than from what fails.

Oftentimes the shows that don't work help you get it right.

Successful engineering is all about understanding how things break or fail.

It is true I had been successful on a small scale in overcoming one of the main difficulties in the new process, but there was still much to invent, and much that at that period I necessarily knew nothing about.

Just because nobody complains doesn't mean all parachutes are perfect.

Often I'll try things that just won't happen the way I'd like them to, so hearing that they're not working saves me some wear and tear the next time around.

In the spirit of science, there really is no such thing as a 'failed experiment.' Any test that yields valid data is a valid test.

He who never made a mistake, never made a discovery.

I tried a dozen different modifications that were rejected. But they all served as a path to the final design.

Don't wallow in brainstorming. Time spent fiddling with a business plan or filling up whiteboards with ideas is time that you could spend actually launching your business and seeing if the idea floats. Launching gives you real, solid feedback, instead of the imaginary 'what if' scenarios dreamed up in a conference room.

Sometimes the best way to learn something is by doing it wrong and looking at what you did.

Most of the work performed by a development engineer results in failure.

No one would say, 'Hey, I think this medicine works, go ahead and use it.' We have testing, we go to the lab, we try it again, we have refinement. But you know what we do on the last mile? 'Oh, this is a good idea. People will like this. Let's put it out there.'

Research is so unpredictable. There are periods when nothing works and all your experiments are a disaster and all your hypotheses are wrong.

What is not a risk with a parts-per-billion test can always be exposed to a parts-per-trillion examination. If rats cope with .the heaviest dose of a chemical that can be soaked into their food and water, you can always gavage them. Or try mice or rabbits. Again, the only stopping rule is discovery of the sought-for effect, or exhaustion of the investigator (or his funds). Many of the risk assessment procedures used today are logically indistinguishable from those used by the Inquisition.

It's possible to fund companies for $100,000 and find out rather quickly whether or not the idea they are pursuing has merit. Scientists now work much faster.

For me, every one of our projects is a research-and-development project.

Back to Microsoft days, I'm always looking for, 'OK, that's great, but what can go wrong?'

Safety is always a paramount concern for us. We are always engaged with the studios and with what better structures can be done.

Failure is an amazing data point that tells you which direction not to go.

Celebrating failure is key. Half of what we do fails, at least.

In tech, you create the foundation; even sometimes if it doesn't work, you take that same developmental idea, and you use it to apply to a different area.