Making Databases Work: The Pragmatic Wisdom of Michael Stonebraker (2018)
dl.acm.org
dl.acm.org
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.
Stonebraker et al are very opinionated (especially about SQL and relational databases), but in a way I can accept because a lot of his thinking is based on first-principles. Stonebraker also has a string of database successes (Ingres, Postgres, Vertica etc.) which gives him enough street cred to prove he's not just spewing theory from an ivory tower. He's not necessarily correct in every opinion, but his opinions are interesting and worth considering. I enjoyed his talk on "Why Big Data is at least 4 different problems"
The second guy more or less taught me how to use Vim. And not just use it, but move buffers around and navigate the filesystem so fast that it seemed he was wired directly into the computer. Up to that point I had not worked with a very very experienced programmer who was still practicing. He would write very complex regexes directly in the vim prompt to find the right parts of log files.
The overall team had been acquired by HP 18 months before I arrived and you could tell that people were beginning to move along. However many of the folks there had worked with Stonebreaker at MIT and then at C store. There was a feeling that they all knew things about column store databases that were not widely known. In particular the engineering manager once walked us through the very first project he implemented at Vertica, which was backup and restore. He more or less derived the whole system from a few principles of when data should be saved over the course of 2 hours.
It was an extremely technical place to work with data sizes and problems I had never encountered. It gave me a sense of the the sheer scale that some companies operated at and what was possible by starting with C++ and building the system out bit by bit over years. Many of the approaches there actually mirrored architecture work I did later on a multi-camera tracking system.
I was fortunate enough to be in Stonebraker's undergrad database class. He had the laid back teaching style that made complex things seem easy. I was like this relational stuff was not that hard. What I learnt in that class are still relevant to current day.