Live data from Hacker News

Learn SQL Once, Use It for 30 Years

fagnerbrack.com

231–240 of 243 posts

Re: Learn SQL Once, Use It for 30 Years

#231
post #230

Earlier quoted context omitted.

> I write exactly like this. You need to consider that people write in different ways, and the LLM is choosing from among the different styles. I'm skeptical. Give us an link to something you wrote prior to 2022.

https://news.ycombinator.com/item?id=25985705

I copied and pasted the comment verbatim into GPTZero.

GPTzero says there's a 0% chance of that being AI written.

So, no, people have not "always written like the way AI writes now".

Re: Learn SQL Once, Use It for 30 Years

#232
post #54

Earlier quoted context omitted.

I find SQL a very thick "wrapper masking low-level logic". Think of the query planning, the index-maintaining, the upholding of guarantees, the writing-to-disk and caching that you are all not doing by using a RDBMS! I'd say SQL is a very high level language. "SQL teaches you to reason and approach problems logically" -- I kind of agree here. It teaches relational data mgmt. I think it is better to attack most softwa…

> I'd say SQL is a very high level language. Yes indeed. When I learned SQL in college, the professor made a HUGE deal about how it was a "4th generation language" so it was so abstract you didn't have to think about how the computer would answer your query. Even at that time I thought that was massive overstatement of what using SQL was like. It didn't deliver on that promise very well. But it's very funny to see pl…

Yes it did, you don't need to worry about whether the sql execution engine is spark, or snowflake, or sqlite or what, you just reason about the top level logic

Re: Learn SQL Once, Use It for 30 Years

#233
I absolutely LOVED learning SQL on PostgreSQL, roughly 26-27 years ago (so, close to the 30 years cited there). I think I still retain at least 70-80% of all the knowledge I built back then, and it is the case probably because the way in which I learned was by DOING.

Re: Learn SQL Once, Use It for 30 Years

#234

>The Only Programming Language Built on Mathematics, Not Fashion As a modern array language D4M is the natural successor for SQL [1]. D4M is based on mathematics like SQL, specifically associative array algebra but not relational unlike SQL. It's more generic since can it caters to most modern data abstractions including spreadsheets, database tables, matrices, and graphs [2]. You can achieve 100M database inserts pe…

First impressions assuming the goal is to replace the incumbent SQL. Haven't seen the language yet. * D4M rolls off the tongue * Make me buy a book to see the language.

The source code is published [1] and there are MIT course videos available [2] (albeit 9 years old...).

The source code appear to be primarily in Matlab(!) though.

[1] https://github.com/Accla

[2] https://ocw.mit.edu/courses/res-ll-005-mathematics-of-big-da...

Re: Learn SQL Once, Use It for 30 Years

#235
post #230

Earlier quoted context omitted.

https://news.ycombinator.com/item?id=25985705

I copied and pasted the comment verbatim into GPTZero. GPTzero says there's a 0% chance of that being AI written. So, no, people have not "always written like the way AI writes now".

I am writing this for you as well as those who are likely to read this later as well.

From the quoted snippet from the original article, purportedly AI-generated:

> Not a tutorial. Not an ORM. Actual SQL

From my comment:

> Not stock options. Do not gamble, your life is passing you by.

> Not titles, unless you have a clear plan to leverage your title into a better paying job.

> Not "job safety" - it is never safe. You being in an in-demand area is your job safety.

Re: Learn SQL Once, Use It for 30 Years

#237
post #235

Earlier quoted context omitted.

I copied and pasted the comment verbatim into GPTZero. GPTzero says there's a 0% chance of that being AI written. So, no, people have not "always written like the way AI writes now".

I am writing this for you as well as those who are likely to read this later as well. From the quoted snippet from the original article, purportedly AI-generated: > Not a tutorial. Not an ORM. Actual SQL From my comment: > Not stock options. Do not gamble, your life is passing you by. > Not titles, unless you have a clear plan to leverage your title into a better paying job. > Not "job safety" - it is never safe. You…

You don't see a large difference between the two styles?

You can check for yourself on any of the GPT checkers - they're completely different (I saw the difference too)

Re: Learn SQL Once, Use It for 30 Years

#238
I love the idea of SQL but to this day after years of using it I still have a strong dislike for it.

The syntax never was intuitive and still isn't, I always mix it up, I found it syntax error always a pain to debug, the tooling is all over the place.

I do agree that it's a truly valuable skill and expect it to last more 30 years.

Re: Learn SQL Once, Use It for 30 Years

#239
post #4

- I recently read that most programmers SQL knowledge is outdated by 20 years and it’s true for me. There are quite a lot of features in most DBs that feel very "new" to me. - Comparing SQL to React weakens the argument. SQL is the language, React is a piece of software. You certainly can run 30 year old JS today in modern browsers.

Agreed on both point, I think you underlined pretty well what was bugging me with the article !

Re: Learn SQL Once, Use It for 30 Years

#240

I think the pretext of this articles is ridiculous. Yes, SQL is based around relational algebra, but all programming languages are built on a theoretical foundation. And SQL is very much a "fad" language - it just somehow managed to stick around. The goal was not some sort of mathematical purity, but rather to built a natural language data interface (sounds like something currently very hyped?) and it failed spectacu…

I think this is a tad too contrarian. I think SQL does (did?) a great job of giving common-language terms for fundamental data table operations, which in turn creates a shared mental model that everyone can use to describe what can and should be done to tables. I agree with you in terms of syntax, though, it leaves something to be desired. But learning SQL was a pretty fundamental step in my journey to becoming a dat…

I don't think so, I think SQL is unintuitive and hard to parse. Enough ppl disagree with me though judging by it's success it was clearly good enough
Post reply on HN