A Quote by James Gosling

In C there are no data structures: there are pointers and pointer arithmetic. So you have a pointer into a data structure. — © James Gosling
In C there are no data structures: there are pointers and pointer arithmetic. So you have a pointer into a data structure.
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.
The key to a solid foundation in data structures and algorithms is not an exhaustive survey of every conceivable data structure and its subforms, with memorization of each's Big-O value and amortized cost.
You can either have software quality or you can have pointer arithmetic, but you cannot have both at the same time.
It's not about guys getting minutes or scoring 20 points or getting playing time. To me, it's about if you've got to make one 3-pointer to win that championship, we need you to make that one 3-pointer. Whatever it takes.
It is better to have 100 functions operate on one data structure than to have 10 functions operate on 10 data structures.
The biggest mistake is an over-reliance on data. Managers will say if there are no data they can take no action. However, data only exist about the past. By the time data become conclusive, it is too late to take actions based on those conclusions.
One of the myths about the Internet of Things is that companies have all the data they need, but their real challenge is making sense of it. In reality, the cost of collecting some kinds of data remains too high, the quality of the data isn't always good enough, and it remains difficult to integrate multiple data sources.
A data scientist is that unique blend of skills that can both unlock the insights of data and tell a fantastic story via the data.
Data!data!data!" he cried impatiently. "I can't make bricks without clay.
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.
Go out and collect data and, instead of having the answer, just look at the data and see if the data tells you anything. When we're allowed to do this with companies, it's almost magical.
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.
Biases and blind spots exist in big data as much as they do in individual perceptions and experiences. Yet there is a problematic belief that bigger data is always better data and that correlation is as good as causation.
Any time scientists disagree, it's because we have insufficient data. Then we can agree on what kind of data to get; we get the data; and the data solves the problem. Either I'm right, or you're right, or we're both wrong. And we move on. That kind of conflict resolution does not exist in politics or religion.
People think 'big data' avoids the problem of discrimination because you are dealing with big data sets, but, in fact, big data is being used for more and more precise forms of discrimination - a form of data redlining.
In my view, our approach to global warming exemplifies everything that is wrong with our approach to the environment. We are basing our decisions on speculation, not evidence. Proponents are pressing their views with more PR than scientific data. Indeed, we have allowed the whole issue to be politicized-red vs blue, Republican vs Democrat. This is in my view absurd. Data aren't political. Data are data. Politics leads you in the direction of a belief. Data, if you follow them, lead you to truth.
This site uses cookies to ensure you get the best experience. More info...
Got it!