I love that this piece talks about the database. That is a problem I focus on. It’s API versioning all over again, and we never _actually_ solved that before we

I love that this piece talks about the database. That is a problem I focus on. It’s API versioning all over again, and we never _actually_ solved that before we moved forward. I see this being our reality anyway. In many cases; not all. You can’t ask the LLM, nor a hypothetical AGI, nor anything, to build the aqueducts. Especially if you don’t know you need them. And they won’t solve the problem if neither a human nor an AI know what the problems actually are. Let’s make em out of lead! And they definitely won’t waste tokens on a postgres rollback migration unless we make that essential in the acceptance criteria. An LLM is all of our ideas, in a search UI that dang nearly passes the turing test. (That says more about us than the state of AI technology.) We are pattern machines in many ways, and many things we code are even lovingly called Software Patterns. The promise is not that software engineering goes away, it’s that we’ll all be managers for a while. Low-code, to me, is different from “statistically generated solutions that pass the requirements.” Genetic programming was an idea for decades, but that is also different from stuff that combines yours and my most relevant github commits into a 90% best guess. Not random, hoping for the best, in this regime. Educated guess.