Quote

Realize you won't master data structures until you are working on a real-world problem and discover that a hash is the solution to your performance woes.

Data is cost. It takes money to create data, store it, clean it, and throw resources at it to learn anything from it.

I think you can have a ridiculously enormous and complex data set, but if you have the right tools and methodology then it's not a problem.

Learn when and how to use different data structures and their algorithms in your own code. This is harder as a student, as the problem assignments you'll work through just won't impart this knowledge. That's fine.

Algorithms don't do a good job of detecting their own flaws.

I'm not for the mass collection of data. I go the other way.

To write a kernel without a data structure and have it be as consistent and graceful as UNIX would have been a much, much harder challenge.

I am completely opposed to the concept of big data.

The number of queries in a large dataset is exponential, and it's growing exponentially. No matter how fast you make your system, you're never going to be able to get all that information.

The fact is that data are worth a lot of money.