I symphatise with your last point! And I agree that great developers should understand how to build a sufficiently performant database for their app, even if th

I symphatise with your last point! And I agree that great developers should understand how to build a sufficiently performant database for their app, even if they won't build one. However, I think our applications are not slow due to database access, but one too many layers of indirection otherwise: eg even ORMs usually introduce a huge performance and complexity cost. Just like we are trying to come up with better and less error prone concurrency models in code (async/await, coroutines...), I get that you are trying to come up with better tooling support for data access, and we should. But we also need to be aware that some people simply want to solve a problem more efficiently, but not most efficiently (look at most ML code and you can barf at it — yet it still makes a huge progress in one area they care about).