Abigail Johnson Quotes

Technical problems are like gremlins. They come and go.

One of the most feared expressions in modern times is 'The computer is down.'

There are programs that don't work.

The data stream has been corrupted, return to first principles.

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.

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'.

When you say 'I wrote a program that crashed Windows,' people just stare at you blankly and say 'Hey, I got those with the system, for free.'

As a rule, software systems do not work well until they have been used, and have failed repeatedly, in real applications.

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

I'm not a programmer myself, but I am a very, very picky end user of technology. I like my machines to work they way they're supposed to, all the time.

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

Everyone has technical issues - you have them until you die - but you have to be aware of them in a certain way.

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

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.

A long time ago, we had to build interfaces to connect with other companies, and I thought that was a great idea. The company had to pay a lot of money to build it and basically launched it, but our whole operating system almost broke. So, we couldn't continue it. In the end, I had to go on the train to Paris to explain that I had spent millions.

In programming, as in everything else, to be in error is to be reborn.

From then on, when anything went wrong with a computer, we said it had bugs in it.

My computer must be broken: whenever I ask a wrong question, it gives a wrong answer.

If in physics there's something you don't understand, you can always hide behind the uncharted depths of nature. You can always blame God. You didn't make it so complex yourself. But if your program doesn't work, there is no one to hide behind. You cannot hide behind an obstinate nature. If it doesn't work, you've messed up.

If there is a bug in your code than you have to drop everything you're doing and go fix it.

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

Database: the information you lose when your memory crashes.

Divide by cucumber error. Please reinstall universe and reboot.