I don’t think SQL is dying,I think it’s just moving backstage. For most business users, that’s probably a good thing. Nobody wants to spend half their day debugging joins when they just need a clear answer.
But someone still has to make sure the logic underneath is solid. If the semantic layer is off, the whole natural language setup becomes a guessing game. So we’re not removing SQL, we’re just shifting who interacts with it.
It kind of feels like the difference between driving a car and building one. Most people just want to drive, but you still need engineers under the hood making sure nothing catches fire.
Thanks, Mark. Totally agree,semantic layers are doing a lot of heavy lifting now, but they also bring their own challenges. I'm curious how teams are handling version control and testing with autogenerated SQL. If the logic shifts invisibly, it feels harder to debug than raw code.
I don’t think SQL is dying,I think it’s just moving backstage. For most business users, that’s probably a good thing. Nobody wants to spend half their day debugging joins when they just need a clear answer.
But someone still has to make sure the logic underneath is solid. If the semantic layer is off, the whole natural language setup becomes a guessing game. So we’re not removing SQL, we’re just shifting who interacts with it.
It kind of feels like the difference between driving a car and building one. Most people just want to drive, but you still need engineers under the hood making sure nothing catches fire.
Really well said! Yes, who creates the sql is changing. More code gen, less hand crafting. Semantic layers are a big piece of the puzzle!
Thanks, Mark. Totally agree,semantic layers are doing a lot of heavy lifting now, but they also bring their own challenges. I'm curious how teams are handling version control and testing with autogenerated SQL. If the logic shifts invisibly, it feels harder to debug than raw code.