Paul W. S. Anderson Quotes

Every time I learn a new thing to do on my computer, I have to write it down so that I can remember it.

Macintosh felt like a system. As I learned more, I felt like I was able to guess how new things would work. I felt like the bugs in my programs were more my bugs and not things I misunderstood.

I had to actually purchase a book to learn the API and write the client. It was pretty frustrating trying to learn the API and develop a product quickly.

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

There has never been an unexpectedly short debugging period in the history of computers.

I'm very impatient, and if I get a new piece of technology, no matter what it is - I recently got the iPhone, which is very exciting - I can't be doing with reading manuals. I want it to work immediately and to do what I want it to do.

Gee, I am a complete Luddite when it comes to computers, I can barely log on!

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

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

To master a new technology, you have to play with it.

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

When we were kicking around the idea for Netflix in 1997, proving out an idea was expensive and labor-intensive. There was no Squarespace, no cloud. If you wanted a website, you had to build it from scratch. If you wanted an online store, you had to completely design it yourself.

One of the hard truths about the new digital world is that we have to be prepared to acknowledge when an experiment is not going to work, and to take action.

It doesn't take a cell phone to make a person rude. There are rude people all over the place. But people are learning. I have never heard a cell phone ring in the movies. We are going to learn how to live with the advantages of new technology.

I enjoy evangelizing Java. In my heart of hearts, I'm an engineer, and what makes me happy is building something that works and having someone use it. That's cool.

That gets me upset- you're jamming along, checking out the crowd and having a good time, and then your equipment goes down. You can't just stop the show and say, 'Oh, Jeff's got a guitar problem.'

On one level, we're on Matador, but our amps still might explode on stage, or they'll be an echo in the mic. It's like climbing a ladder. I like to climb it really slowly. I could probably get really professional right away, but I like to take baby steps and find my own 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.

Depending on the kind of code you write, depending on the kind of ideas you have, you can be creative in problem-solving and you can really make things work in a very gratifying way.

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

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.

Programming is a pretty tricky thing to start learning. You need to combine it with comedy to get a wider audience.

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

I'm not really good with technology.

Building the machine for 'Speed' was fun, as was working on the 'Spitfire' programme. They are programmes I enjoyed being on, but they are not my job.