A Quote by Bill Joy

There are a couple of people in the world who can really program in C or FØRTRAN. They write more code in less time than it takes for other programmers. Most programmers aren't that good. The problem is that those few programmers who crank out code aren't interested in maintaining it.
When the words are fuzzy, the programmers reflexively retreat to the most precise method of articulation available: source code. Although there is nothing more precise than code, there is also nothing more permanent or resistant to change. So the situation frequently crops up where nomenclature confusion drives programmers to begin coding prematurely, and that code becomes the de facto design, regardless of its appropriateness or correctness.
I will, in fact, claim that the difference between a bad programmer and a good one is whether he considers his code or his data structures more important. Bad programmers worry about the code. Good programmers worry about data structures and their relationships.
Bad programmers worry about the code. Good programmers worry about data structures and their relationships.
Any fool can write code that a computer can understand. Good programmers write code that humans can understand.
Programmers are very creative people. And animators are problem solvers, just as programmers are.
There's a subtle reason that programmers always want to throw away the code and start over. The reason is that they think the old code is a mess. [...] The reason that they think the old code is a mess is because of a cardinal, fundamental law of programming: It's harder to read code than to write it.
It is a mistake to think that programmers wares are programs. Programmers have to produce trustworthy solutions and present it in the form of cogent arguments. Programs source code is just the accompanying material to which these arguments are to be applied to.
Real programmers can write assembly code in any language.
Beyond basic mathematical aptitude, the difference between good programmers and great programmers is verbal ability.
With software products, it is usual to find that the software has major `bugs' and does not work reliably for some users... The lay public, familiar with only a few incidents of software failure, may regard them as exceptions caused by exceptionally inept programmers. Those of us who are software professionals know better; the most competent programmers in the world cannot avoid such problems.
Real programmers don't write in PL/I. PL/I is for programmers who can't decide whether to write in COBOL or FORTRAN.
GOTO, n.: A programming tool that exists to allow structured programmers to complain about unstructured programmers.
Real programmers don't comment their code. If it was hard to write, it should be hard to understand.
When are programmers happy? They're happy when they're not underutilized - when they're not bored - and also when they're not overburdened with inappropriate specifications or meaningless bureaucracies. In other words, programmers are happiest when they're working efficiently. This is a general preference in creative work.
Chefs work with food, artists with oil paint, programmers with code.
We were not out to win over the Lisp programmers; we were after the C++ programmers. We managed to drag a lot of them about halfway to Lisp.
This site uses cookies to ensure you get the best experience. More info...
Got it!