Rill Developer: SQL Flow State Demo

Hey folks, this is sung speaking here, and I'm going to give a demo of the open source real developer. So let's take it a step back to figure out what problem this is solving in the first place.

When it comes to any SQL development, even the best tooling doesn't give you flow state. What I mean by that is every time you want to explore data that you've seen for the first time, you're like, you're probably asking some basic questions of how fresh it is.

Like what is the basic profile? Are there NOLs in my columns? And that's like a dozen queries just to get started.

And then I have to press buttons to run that query. And I don't even know if my sequel syntax is right before it's, you know, before it's even submitted to the database in the first place.

And so all those problems, this is I think, heading in the right direction to solve that. At least for exploratory analysis, this is not covered DBT development.

And so what I mean by that is I start with, you know, a blink query. I have a profile of data, but even if I just do a simple select, I'm going to do this from flights where destination equals this, I get instant, hot reload feedback.

Something that software engineers have had for decades when they update, you know, front end code to see how a button changes colors on their website, I can even do, um, what's it called this from?

What's it called? Oh, I have to do group back. And so you notice here even shows me the errors in real time.

So I'm not wasting my time going, oh, I think this query is right wrong query. I'm getting this compiler here.

Nope. When it works, it shows me instant feedback of that. And if I want to copy to clipboard, I just click shift, click, and it copies the name of that column.

I can even see basic statistics around this. There I'll even remove this and then order by destination ascending. And Shizam I noticed, oh, there are a bunch of NOLs here.

Um, it shows me basic profiles of locations I should, uh, or destinations, I should say, I should, I should care about.

And I get instant feedback loops on this. And then I export this data, however I want. And so it's so powerful about this is you notice that this entire experience, I didn't have to click that many buttons to micromanage context switching.

I get instant feedback loops on the overall data and the subset of data based on my query results. And so context is maintained at all times from a zoomed out view to a zoomed in view.

And it's one of those things I didn't realize I wanted until I saw it and lived and breathed in this experience.

And I hope that more, you know, SQL developers or just people experiencing data, um, can feel this and see that this should be normal, not the exception.

All right. That's my spiel.