3 ms·
I found his chapters "Where good ideas come from and how to exploit them" (https://dl.acm.org/doi/abs/10.1145/3226595.3226608 https://dl.acm.org/doi/abs/10.1145
by scott_s 6y ago
I found his chapters "Where good ideas come from and how to exploit them" (https://dl.acm.org/doi/abs/10.1145/3226595.3226608 https://dl.acm.org/doi/abs/10.1145/3226595.3226608) and "Where we have failed" (https://dl.acm.org/doi/abs/10.1145/3226595.3226609 https://dl.acm.org/doi/abs/10.1145/3226595.3226609) particularly insightful. A thread running through both is make sure you're working on problems that people actually have.
Much of the chapter on where we failed is about problems in the academic system itself. He has some proposed solutions, but I don't know how effective (or realistic) they are. I also don't have easily expressible solutions myself.
- ckuehne 6y agoI like this quote from the "Where We Have Failed" paper: "We are very uncritical of systems created by the large Internet vendors to that solve application-specific problems, which have been written, until recently, by development teams with little background in DBMSs. As such, they have tended to reinvent the wheel. I am especially amused by Google’s adoption and then rejection of MapReduce and eventual consistency."