Mark Zuckerberg Quotes

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.

There are two methods in software design. One is to make the program so simple, there are obviously no errors. The other is to make it so complicated, there are no obvious errors.

Writing software is a very intense, very personal thing. You have to have time to work your way through it, to understand it. Then debug it.

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.

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.

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.

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

The process of debugging, going an correcting the program and then looking at the behavior, and then correcting it again, and finally iteratively getting it to a working program, is in fact, very close to learning about learning.

Learn when and how to use different data structures and their algorithms in your own code. This is harder as a student, as the problem assignments you'll work through just won't impart this knowledge. That's fine.

I am a programmer.

People who are more than casually interested in computers should have at least some idea of what the underlying hardware is like. Otherwise the programs they write will be pretty weird.

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

And, I think that is actually appropriate because I'm really not the world's best programmer, I think it's a good thing that I'm not touching the code.

It was used for decades to describe talented computer enthusiasts, people whose skill at using computers to solve technical problems and puzzles was - and is - respected and admired by others possessing similar technical skills.

The manuals we got from IBM would show examples of programs and I knew I could do a heck of a lot better than that. So I thought I might have some talent.

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

Eventually I found it had been working all along-but didn't show anything on screen until it had the first full page of text. I inserted 30 new lines, and suddenly my toy said 'hEllO woRlD'. An hour later I understood alphabet shifting rather better!

Hosting various versions of my countdown program has kept me extremely busy, and I loved every minute of it.

Writing software that's safe even in the presence of bugs makes the challenge even more interesting.

The three chief virtues of a programmer are: Laziness, Impatience and Hubris.

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

The mark of a mature programmer is willingness to throw out code you spent time on when you realize it's pointless.

I was a programmer.

It's something special being able to build a program up.

As software engineers trained to turn ambiguity into absolutes and fuzzy requirements into ones and zeros, we had a 'eureka' moment when we realized that our training had broader, real-world applications.