I watched Dr. Hipp's keynote. Here's my summary for folks who don't want to sit through it. (This is hand written, not LLM-generated.)
Dr. Hipp suggests a definition of "AI" in which SQL planners are AI, defining AI as "any computing system that performs tasks typically associated with human reasoning, problem-solving, and decision-making." (He then explains briefly how SQL planners are runtime code generators. If you're not familiar with how SQL planners work, the keynote is pretty short and worth a watch.)
He then makes a recommendation to developers who are afraid that AI will take their jobs. He points out that SQL planners kinda take away part of the job of a developer, but really just changed the nature of the job.
He makes his point with a slide:
> Q: How can you avoid being replaced by AI?
> A: Solve more problems than you create.
He concludes with a recommendation against having LLMs generate your SQL entirely. He recommends writing it yourself in order to understand it better and engage both the part of your brain that process human language and the part of your brain that processes formal languages like SQL. (He gives an example of trying to ask a coworker for help, but solving the problem by explaining it to the coworker, and how valuable that experience is.)
---
For my part, I'm not sure I agree with calling a SQL planner "AI" in 2026 (I think that obscures more than it reveals), but the advice to solve more problems than you create will always be wise.
I watched Dr. Hipp's keynote. Here's my summary for folks who don't want to sit through it. (This is hand written, not LLM-generated.)
Dr. Hipp suggests a definition of "AI" in which SQL planners are AI, defining AI as "any computing system that performs tasks typically associated with human reasoning, problem-solving, and decision-making." (He then explains briefly how SQL planners are runtime code generators. If you're not familiar with how SQL planners work, the keynote is pretty short and worth a watch.)
He then makes a recommendation to developers who are afraid that AI will take their jobs. He points out that SQL planners kinda take away part of the job of a developer, but really just changed the nature of the job.
He makes his point with a slide:
> Q: How can you avoid being replaced by AI?
> A: Solve more problems than you create.
He concludes with a recommendation against having LLMs generate your SQL entirely. He recommends writing it yourself in order to understand it better and engage both the part of your brain that process human language and the part of your brain that processes formal languages like SQL. (He gives an example of trying to ask a coworker for help, but solving the problem by explaining it to the coworker, and how valuable that experience is.)
---
For my part, I'm not sure I agree with calling a SQL planner "AI" in 2026 (I think that obscures more than it reveals), but the advice to solve more problems than you create will always be wise.
D. Richard Hipp's 20 minute keynote is here: https://youtu.be/R57nUGzo7CA?is=fDMxVTH_AOvPlKR- (starts 1m45s)