I'm a senior dev that up until recently managed to avoid having SQL in my knowledge stack as we've always used no-sql databases. I knew the basics but I took a

I'm a senior dev that up until recently managed to avoid having SQL in my knowledge stack as we've always used no-sql databases. I knew the basics but I took a weekend to catch up on some more advance use cases and I can really resonate with this article. Unsurprisingly I came down to a conclusion that SQL is just a bad language, no matter how you look at it. It throws away every code flow standard in favor of their own nonsensical flavor. Where normal synchronous programs go top-to-bottom SQL is a complete spaghetti of flow and logic. Just take a look at the most basic syntax: `SELECT person.name FROM person` The variable is defined at the end of the program which is just absolutely silly, what if the program is 100 lines long; do I need to start reading from the bottom? SQL must be the reason mouse scroll wheels were invented. As an alternative take a look at view based systems: `for person in people: yield person.name` — isn't it infinitely more understandable and readable? Unfortunately it seems SQL is here to stay as most people would rather work with this mess rather than invest some time to adopt something better.