Earlier quoted context omitted.
I love that I'm at a company that I haven't had to use SQL. I don't know if I could even find a relational database here. But in a classic meme sense: "It isn't you I hate SQL, it's what I have to think about when I use you." I don't want to spend my time thinking about database indexes, query plans, or other complicated bits. I just want to get my data out. Sometimes I struggle, and I'd give anything for a plain inn…
Hard to imagine how it's to live in a company that has no database. But I do take issue with that: > It isn't you I hate SQL, it's what I have to think about when I use you. Do you live at the fringe of performance like that? Nobody spends much time thinking about those things, and the few times that require thinking about them would require thinking about much more complicated things if you weren't using a database.
If I'm building a simple CRUD app, then I don't need the complexity that SQL provides. If I'm building something bigger, then I probably need to think about the query plans.
I would have loved a tool that I could hand a proposed schema, estimates of the data, and some SQL I want to run that would come back and tell me "That's stupid, because you're doing a join on computed data; add this index, denormalize this field, and remove this clause from your query." but I'm also realistic enough to know that such a tool isn't plausible.