Eric Fellner Quotes

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

In computing, turning the obvious into the useful is a living definition of the word 'frustration'.

I spend almost as much time figuring out what's wrong with my computer as I do actually using it.

One of the headaches of high-tech test programmes is having to debug the test arrangements before you can start debugging the things you're trying to test.

I detest computers. If you had a device like that 30 years ago that froze up constantly, misbehaved constantly, lost your information and screwed up when you needed it the most, it would have been laughable.

We've had such thorough training, we've had an excellent team on the ground. With the minor glitches that have occurred, we've been able to take care of them. And the teams on the ground are getting tons of incredible data.

Troubleshooting a wiring problem is a soul-killing experience.

If your project doesn't work, look for the part that you didn't think was important.

I fix things now and then, more often tweak HTML and make scripts to do things.

When computer systems cause errors, you can end up with The Dreaded NIGO - the 'not in good order' transaction.

When you come to a hotel where everything is brand new, it's logical that not everything works.

When somebody is describing their job as fixing problems for someone, that usually does not suggest that they're dealing with their tax returns.

If you don’t know how to fix it, please, stop breaking it.

People get annoyed when you try to debug them.

Troubleshooters?" Michael asked. "When there's trouble," I told him, "they shoot it.

The biggest challenges are fixing the problems, to put all the puzzles together.

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

I still don't know how to jump-start a car, even though it's been told to me a million times. But I do love thinking about how creativity works.

One thing I like to do is visit technical forums and ask for help regarding an entirely fictitious problem I'm having with my software. When I receive help, I say, 'Nope. Didn't work.' If they guide me to a button to click, I say, 'Nope. Can't see it.' Sometimes I just reply with nothing but 'Nope,' and it drives them up the wall.

I'm starting to feel like I can actually figure out how stuff works. I can actually pick stuff apart and have a chance of fixing it.

Banking, as far as I can tell, seems to be almost as precise a science as using a slot machine. You either blindly hope for the best, delude yourself into thinking you've worked out a system, or open it up when no one's looking and rig the settings so it'll pay out illegally.

Problem-solving, inventing, hacking and coding is more of an adrenaline rush of endorphins rather than a feeling.

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.

There are programs that don't work.

Error is always talkative.