Code Organization Quotes

Bad programmers worry about the code. Good programmers worry about data structures and their relationships.

If you want to go somewhere, goto is the best way to get there.

Inside every large program is a small program struggling to get out.

All the PHP code I've seen in that experience has been messy, unmaintainable crap. Spaghetti SQL wrapped in spaghetti PHP wrapped in spaghetti HTML, replicated in slightly-varying form in dozens of places.

I used to be enamored of object-oriented programming. I'm now finding myself leaning toward believing that it is a plot designed to destroy joy.

Good visual layout shows the logical structure of a program.

When there is no type hierarchy you don't have to manage the type hierarchy.

If you have a procedure with 10 parameters, you probably missed some.

Even if you aren't in doubt, consider the mental welfare of the person who has to maintain the code after you, and who will probably put parens in the wrong place.

A powerful programming language is more than just a means for instructing a computer to perform tasks. The language also serves as a framework within which we organize our ideas about processes.

We've broken the code base into logical chunks, called modules, and the foundation staff delegate authority for the modules to people with the most expertise.

Adding functionality is not just a matter of adding code.

I didn't want my script to get too out of control like that. So I actually made it a point not to do stuff like that, to pretty - to keep it more sparse than it's been in the last few years, or the last decade.

The art of programming is the art of organizing complexity.

Computer programming is really a lot like writing a recipe. If you've read a recipe, you know what the structure of a recipe is, it's got some things up at the top that are your ingredients, and below that, the directions for how to deal with those ingredients.

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.