A Quote by Larry Wall

Real programmers can write assembly code in any language. — © Larry Wall
Real programmers can write assembly code in any language.
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.
Any fool can write code that a computer can understand. Good programmers write code that humans can understand.
Real programmers don't comment their code. If it was hard to write, it should be hard to understand.
Real programmers don't work from 9 to 5. If any real programmers are around at 9am it's because they were up all night.
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.
Regardless of whether one is dealing with assembly language or compiler language, the number of debugged lines of source code per day is about the same!
Real programmers don't write in PL/I. PL/I is for programmers who can't decide whether to write in COBOL or FORTRAN.
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 started out with machine code and assembly language.
Programmers are always surrounded by complexity; we cannot avoid it.... If our basic tool, the language in which we design and code our programs, is also complicated, the language itself becomes part of the problem rather than part of its solution.
The C language combines all the power of assembly language with all the ease-of-use of assembly language.
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.
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.
C is not clean – the language has many gotchas and traps, and although its semantics are simple in some sense, it is not any cleaner than the assembly-language design it is based on.
Bad programmers worry about the code. Good programmers worry about data structures and their relationships.
Perhaps we could write code to optimize code, then run that code through the code optimizer?
This site uses cookies to ensure you get the best experience. More info...
Got it!