>> It's hard to imagine an innovative problem solver being unable to tackle Google's interview questions. You gave the example of optimizing an SQL query. That's a data structures problem itself.
Dude, is your definition of problem solving limited only to Algos and datastructs?
Because I can imagine sql optimization in the following ways:
1. Compiler modification to use different instructions
2. Hinting branch predictors
3. Modifying the database environment to use different operations under the hood
4. Use a different hardware
5. Use a different language
6. Allocate different memory configs
7. Use SSD
Do you even realize that CS is not algos and datastructs only?
>> The big optimization would be avoiding full table scans or full table joins. That would be at the query level.
An insight that can only come from experience and to someone who is actually interested in this.
I want to work with people like you, not with the person who can solve some stupid dynamic programming puzzle but can't do any real interesting stuff in the real world.
Dude, is your definition of problem solving limited only to Algos and datastructs?
Because I can imagine sql optimization in the following ways: 1. Compiler modification to use different instructions 2. Hinting branch predictors 3. Modifying the database environment to use different operations under the hood 4. Use a different hardware 5. Use a different language 6. Allocate different memory configs 7. Use SSD
Do you even realize that CS is not algos and datastructs only?