Ezer Weizman Quotes

I'm a perfectionist. And that's served me very well in my career. It allows me to handle these large, complex problems without letting things fall through the cracks... That is the mentality you have to have to attack these complex problems of chip design, for example, when you're overwhelmed with complexity.

I also know that I am not a great technician.

In the computer industry, you've got an interdisciplinary team of people who can come together, attack the problem, and work in a collaborative style. You knock down one problem after another, cobble things together, and then hopefully turn the crank at some point.

Doing the simple thing first doesn't mean your solution will work forever.

The mechanic, when a wheel refuses to turn, never thinks of dropping on his knees and asking the assistance of some divine power. He knows there is a reason. He knows that something is too large or too small; that there is something wrong with his machine; and he goes to work and he makes it larger or smaller, here or there, until the wheel will turn.

Faith moves mountains, but only knowledge moves them to the right place.

I fix things all the time. Every time I do a solo, I re-check it and correct things that don't hit the mark.

No matter how complicated a problem is, it usually can be reduced to a simple, comprehensible form which is often the best solution.

The easiest way to solve a problem is to pick an easy one.

When you're trying to solve a problem on a new product type, you become completely focused on problems that seem a number of steps removed from the main product. That problem solving can appear a little abstract, and it is easy to lose sight of the product.

But that's one of the nice things about doing a stage show, if something doesn't work out, you have the luxury of working on it over time.

Think small. Don't pretend you know the answers. Experiment; get feedback. These are all the premises of 'Think Like a Freak,' really.

I was more of a person that liked flying and operating high-performance machinery, and I liked that, the skill it took, the intelligence it took to do that.

Being a scientist/engineer by nature, I approach everything as a problem.

There's a great deal of poetry in working out how things work, cutting bits of metal, trying to mend stuff.

Science is the practice of failing repeatedly but learning as you go.

Coding, it's an endless process of trial and error, of trying to get the right command in the right place, with sometimes just a semicolon making the difference between success and failure. Code breaks and then it falls apart, and it often takes many, many tries until that magical moment when what you're trying to build comes to life.

I've always had good connections with cars and always knew how to fix them, so I didn't have trouble with breakdowns.

When things that normally work aren't working, you have to go to something else.

It's kind of an intuitive process. I wish that it were more systematic, but it just isn't.

Essentially, 'Z2' ended up feeling the way that it should, but it was through a considerable amount of trial and error that it took to get there.

I'm a great believer in the principle of try it and work it out. If a gadget is designed well, you can easily work out how to use it. But if you can't, it isn't shameful to read the instructions.

As an engineer, you learn there is a solution to every problem. It may take you a while, but eventually you're going to find it.

When you're first starting a show, any show, you learn what works and what doesn't work, and it's a kind of trial and error thing.