 |
VOOZH | about |
|
VOOZH | about |
We’re so glad you’re here. You can expect all the best TNS content to arrive Monday through Friday to keep you on top of the news and at the top of your game.
Check your inbox for a confirmation email where you can adjust your preferences and even join additional groups.
Follow TNS on your favorite social media networks.
Become a TNS follower on LinkedIn.
Check out the latest featured and trending stories while you wait for your first TNS newsletter.
Hello. You’re a JavaScript developer, right? Would I also be right in assuming that you don’t know SQL, and you don’t want to learn SQL?
In this article, I’d like to introduce you to Outerbase which, among other things, allows you to create, edit, visualize and explore the data in your database — all without having to write SQL. More on that in just a moment, but first, let’s address the elephant in the room (pun intended)
JavaScript developers are running out of excuses not to learn SQL.
Many JavaScript developers will do quite literally anything to avoid learning SQL, and after a little bit of research, I’ve boiled it down to three key reasons:
In a previous article: Automatically Generate Types for Your PostgreSQL Database, I addressed point 3, so now it’s time to circle back and tackle points 1, and 2.
I can’t, and won’t ever, understand why you don’t have time to invest in yourself, so let’s skip point 1.
Point 2, however, is something I’d like to address. The lines between frontend and backend are becoming more and more blurred in JavaScript land, and I think that’s actually pretty cool. Frontend devs can now do things that before would have required deep backend knowledge. However, that doesn’t mean you should skip the fundamentals.
SQL is the language of databases and if you’re a JavaScript developer using PostgreSQL, it’s beneficial to have at least a basic understanding of SQL, even if you do eventually end up using a JavaScript client to query your database.
The road to learning SQL can be a little rocky, but thankfully with the rise of AI and the developer tools companies using it, learning SQL might have just become a lot easier.
Go ahead and sign up, then connect Outerbase to your database. Once you’re connected, you can begin to write queries using natural language and Outerbase AI will convert your “conversation” into a SQL query.
I’ve connected Outerbase to my PostgreSQL database which I use to capture site visits and display them on the dashboard of my site. I store geolocation data from site visitors in a table named analytics. The table schema looks like this:
In the below “conversation” I’ve asked Outerbase to count the number of visits from each country in the analytics table.
And without any bother at all, Outerbase wrote the following SQL query, which I’ve run right there in the browser to see the results.
👁 Outerbase AI query and results
From here I could very easily copy and paste this query into my code, and et voilà, I’d have data to display any which way I like in my frontend.
By using Outerbase AI, you can describe the data you’d like to query using natural language, and Outerbase AI will write the SQL query for you. It feels like a nice middle ground for developers wishing to dip their toe in the PostgreSQL pool (again, pun intended), but without getting snagged up on unfamiliar syntax.
If you’re coming from JavaScript, SQL at first can appear to be like an Alien language, but it’s really not. For instance, can you read this?
I’d imagine you probably can, and that’s by design.
Take a look at this video of Don Chamberlin, one of the principal designers of SQL. In the video, Don explains the fundamental goals guiding the design of the SQL language. Goals 2, 3, and 4 are particularly pertinent.
I think you’ll agree that the simple SELECT statement above meets these requirements. Even just simply reading it in the context of an ordinary sentence makes sense. E.g. select name, country, and email from users.
Fun fact: SQL doesn’t have to be written in uppercase.
In JavaScript land, things are a little, well, weird. For instance, here’s the same query used above, but written in Supabase and Xata-specific JavaScript syntax.
It’s worth noting that both Supabase and Xata can be queried using “ordinary” SQL too, FYI!
Whilst there are advantages to using JavaScript syntax to query a database (type safety is not among them), I do still wonder why JavaScript developers are so reluctant to learn SQL.
In most cases, SQL expressed in JavaScript requires special knowledge and can’t be read like an ordinary sentence (in English). And more than that, learning what I’m calling SamQL-Jackson (provider-specific JavaScript syntax) is shortsighted. Why spend the time learning something that can only be used with one provider, when you could invest the same amount of time developing skills that are much more widely used and that will greatly improve both your understanding of the technology you’re using and probably your chances of getting hired.
However, there is one remaining point that I do think is a reasonable rationale for using SamQL-Jackson, and that’s autocomplete. For instance, if you were to type supabase. In your code editor, you’ll be presented with a list containing a number of options to choose from to construct your query.
👁 Supabase autocomplete example
Arguably though, if you already know SQL, you don’t need autocomplete. You could very easily write queries just as quickly, or take advantage of the ~40 years of internet history that will help you understand SQL; or, better still, something like ChatGPT which also has ~40 years of internet history to reference. If both of those fail, there’s now Outerbase AI, which will write SQL for you!
This might be a little spicy, but JavaScript developers are really running out of excuses not to learn SQL.
It might sound like I’ve got an axe to grind with JavaScript and SaaS PostgreSQL providers, but I don’t. I do, however, have a vested interest in developer education. The “best practices” noise you hear around “ship it culture” doesn’t apply to you when you’re learning. Speed doesn’t factor in when you’re investing in yourself. If it takes you a year to learn SQL, so be it. SQL is a foundational skill. Learning it, and even perhaps struggling with it, will eventually help you understand why abstractions exist. From there you can make your own decisions about whether or not they suit your requirements.
Starting with abstractions, however, means you miss out on the backstory. That would be like watching a movie and just skipping straight to the last five minutes, just so you can say you reached the end — or, “Look what I shipped”. Of course, it takes longer to watch the entire thing, but during that time you’ll understand the characters, the plotline, and (if the story is told well) you’ll be engaged throughout.
For me, learning is kind of the same thing. I don’t want to skip to the end, I want to experience the whole story. I don’t know if I’ll have changed your opinion about SQL, but I think by using Outerbase AI you might start to see it’s not as scary and verbose as you thought. Give it a go!
