cs

EPIGRAMS IN PROGRAMMING

Submitted by dv on Wed, 2008-02-06 16:59.

cs
lists

EPIGRAMS IN PROGRAMMING seem to be quite old (1982), but most are still relevant. Some that I found interesting:

7. It is easier to write an incorrect program than understand a correct one. When you see a working piece of code that you don’t like (for whatever reason), try to understand it first before deciding to rewrite it “The Right Way”
19. A language that doesn’t affect the way you think about programming, is not worth knowing. I better learn COBOL, ‘cause I hear it’s a whole other programming experience. Also, try saying that to someone who’s out of a job and has a family to feed. You learn whatever gets you to tomorrow in some situations.
21. Optimization hinders evolution. Highly-optimized code sometimes results in “You’re not expected to understand this”
26. There will always be things we wish to say in our programs that in all known languages can only be said poorly. I guess this is why new programming languages continue to be invented.
57. It is easier to change the specification to fit the program than vice versa.
64. Often it is the means that justify the ends: Goals advance technique and technique survives even when goal structures crumble.
94. Interfaces keep things tidy, but don’t accelerate growth: Functions do. But keeping things tidy is necessary to have growth or you end up wasting time figuring out what goes where. So, in a way, interfaces do accelerate growth.
117. It goes against the grain of modern education to teach children to program. What fun is there in making plans, acquiring discipline in organizing thoughts, devoting attention to detail and learning to be self-critical? “It goes against the grain of modern education to teach children to (important activity). What fun is there in (necessary skill), (good quality)*3?” I wonder if I’ll be hating on the modern education system when I’m 60.