Arthur Bloch Quotes

It took us about a day and a half to find out what had gone wrong.

If you are unable to understand the cause of a problem it is impossible to solve it.

Finding out exactly what went wrong is key toward preventing future debacles.

It's the people who have an incentive to find the problem who usually find the problem.

Instead of seeking to pinpoint blame, seek to understand cause.

You cannot solve a problem unless you diagnose the problem.

You can't solve a problem? Well, get down and investigate the present facts and [the problem's] past history! When you have investigated the problem thoroughly, you will know how to solve it.

I learned quickly, as I tell my graduate students now, there are no answers in the back of the book when the equipment doesn't work or the measurements look strange.

I do as much debugging as possible on the Mac, but I occasionally must debug problems in the PC world, which is significantly slower.

Troubleshooting a wiring problem is a soul-killing experience.

Technical problems are like gremlins. They come and go.

To me, error analysis is the sweet spot for improvement.

I'm very good at deconstructing. I'm a very good troubleshooter for why something is unlikely to work. And most everything is unlikely to work.

The notion of getting under the hood and explaining how something works, that's fairly familiar territory to me.

If you don’t understand how problems came to be, how are you going to know how to fix them?

When I want to understand a problem, I want to understand it from the ground level.

Problems are cured by facing their cause.

Usually, you can figure out where a person's mistakes came from if you ask them the genesis of their thought process: 'Why did you do it this way?' As opposed to telling them they did it the wrong way. Understanding their thought process will ultimately help you be able to communicate with them and navigate around them.

'Debug' is '2001' from Hal's perspective.

Generally, you cannot solve a problem without defining the problem completely.

I like to give myself time to deal with an issue. I get to the root of the matter and learn from it. I don't like to repeat mistakes.

If I see something that seems out of sync with what's already known, the first thing I do is try to find out what's wrong with the data. Once you've done that, and it still seems wrong, that's when things get interesting. It means you've found something new to understand.

I'm a common sense person who tries to analyze and I have to look at all sides of the issue because you don't want software that only does something but doesn't fix the other errors.

Error is always talkative.

Unless you understand the history of a situation, you can't ever hope to solve problems.