quote by Linus Torvalds

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

— Linus Torvalds

Strong Data Structures quotations

Generally, the craft of programming is the factoring of a set of requirements into a a set of functions and data structures.


Data structures quote As long as the problems of the poor are not radically resolved by rejecting the
As long as the problems of the poor are not radically resolved by rejecting the absolute autonomy of markets and financial speculation and by attacking the structural causes of inequality, no solution will be found for the world's problems or, for that matter, to any problems.

Smart data structures and dumb code works a lot better than the other way around.

Data structures quote Companies such as Google and Facebook rely on capturing as much data as possible
Companies such as Google and Facebook rely on capturing as much data as possible to enhance their advertising targeting.
2

It is better to have 100 functions operate on one data structure than to have 10 functions operate on 10 data structures.

Data dominates. If you've chosen the right data structures and organized things well, the algorithms will almost always be self-evident. Data structures, not algorithms, are central to programming.

It's easy to make mistakes that only come out much later, after you've already implemented a lot of code. You'll realize Oh I should have used a different type of data structure. Start over from scratch.


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.

A data structure is just a stupid programming language.

Morphological information has provided the greatest single source of data in the formulation and development of the theory of evolution and that even now, when the preponderance of work is experimental, the basis for interpretation in many areas of study remains the form and relationships of structures.

I had some of the students in my finance class actually do some empirical work on capital structures, to see if we could find any obvious patterns in the data, but we couldn't see any.

It's always the balance between the individual's subjective experience and the social structural condition. As individuals we have access to more than we've ever had before. Giving up our data seems a small price to pay, especially if, as you say, we don't feel we have anything to hide.


The programmer's primary weapon in the never-ending battle against slow system is to change the intramodular structure. Our first response should be to reorganize the modules' data structures.

The term architecture is used here to describe the attributes of a system as seen by the programmer, i.e., the conceptual structure and functional behavior, as distinct from the organization of the data flow and controls, the logical design, and the physical implementation. i. Additional details concerning the architecture

With the old economics destroyed, organizational forms perfected for industrial production have to be replaced with structures optimized for digital data. It makes increasingly less sense even to talk about a publishing industry, because the core problem publishing solves — the incredible difficulty, complexity, and expense of making something available to the public — has stopped being a problem.

Thought, without the data on which to structure that thought, leads nowhere.

Facts and theories are different things, not rungs in a hierarchy of increasing certainty. Facts are the world's data. Theories are structures of ideas that explain and interpret facts. Facts do not go away while scientists debate rival theories for explaining them. Einstein's theory of gravitation replaced Newton's, but apples did not suspend themselves in mid-air pending the outcome.