Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Learn SQL Interactively on Khan Academy

cs-blog.khanacademy.org

Post reply on HN
Print view View original

11–20 of 89 posts

Re: Learn SQL Interactively on Khan Academy

#11

Post by kremlin »

I'm doing the course, as it's something I haven't learned in depth yet.

They mentioned pronunciation : 'S-Q-L' vs 'sequel'. I've always pronounced it S-Q-L. The lecturer implies there's no right answer, that 'sequel' is historical but 'S-Q-L' is preferred for international use.

The annoying thing, though, is that in writing a choice has to be made. If someone pronounces it 'S-Q-L' then to read 'a SQL query' is weird -- it should say 'an SQL query'. And vice versa for someone who pronounces it 'sequel'. 'an sequel query' isn't right.

So, in writing, what is correct? 'An sql query' or 'a sql query'?

Re: Learn SQL Interactively on Khan Academy

#12

Post by theoduino »

pcurve wrote: post #10
marktangotango wrote: post #6

Imo every developer should be comfortable with sql, upto joins at least. Basic data modelling is also invaluable.

Serious question...what kind of developer can you be without knowing SQL?

One who does lots of low-level C/Assembly programming. I know several people who do lots of low-level OS work, and don't use SQL.

Re: Learn SQL Interactively on Khan Academy

#13

Post by GuiA »

kremlin wrote: post #11

I'm doing the course, as it's something I haven't learned in depth yet. They mentioned pronunciation : 'S-Q-L' vs 'sequel'. I've always pronounced it S-Q-L. The lecturer implies there's no right answer, that 'sequel' is historical but 'S-Q-L' is preferred for international use. The annoying thing, though, is that in writing a choice has to be made. If someone pronounces it 'S-Q-L' then to read 'a SQL query' is weird…

Some languages, like French, have a group which can dictate what is and isn't correct in the language (as it turns out, the vast majority of French speaking people don't give a rat's butt about what the Académie Française thinks and still do as they please, but that's another story).

In English, however, there is no such authority. Whether you are writing a SQL query or an SQL query is all up to you. Aren't you happy you don't have an old wrinkly white French dude to chastise you about which one is correct?

Re: Learn SQL Interactively on Khan Academy

#14

Post by optimusclimb »

pcurve wrote: post #10
marktangotango wrote: post #6

Imo every developer should be comfortable with sql, upto joins at least. Basic data modelling is also invaluable.

Serious question...what kind of developer can you be without knowing SQL?

Not that I hadn't already done plenty of CRUD in SQL in jobs prior, but for 4 years I worked on streaming stock quote servers. All in all the system had 500+ servers deployed in a tiered setup. No data was persisted to disk (save for some config), and no SQL was ever involved. Ticker symbols (CUSIPs) did need to be looked up and those went through our network, but the actual lookups went out to a service, and results were cached.

That's just one example. I'm sure there are many.

Re: Learn SQL Interactively on Khan Academy

#15

Post by dragonwriter »

kremlin wrote: post #11

I'm doing the course, as it's something I haven't learned in depth yet. They mentioned pronunciation : 'S-Q-L' vs 'sequel'. I've always pronounced it S-Q-L. The lecturer implies there's no right answer, that 'sequel' is historical but 'S-Q-L' is preferred for international use. The annoying thing, though, is that in writing a choice has to be made. If someone pronounces it 'S-Q-L' then to read 'a SQL query' is weird…

A choice has to be made in speech, as well. And, as there is no one clear correct answer in speech, and the choice in writing is based on the choice in speech, there is no one clear correct answer in writing. Choose one, and use it consistently within a given work, and you should be fine.

Of course, if its a work on SQL, you can normally avoid "a(n) SQL query" and just say a "a query" (with SQL implicit from context) or, in the less-common situation where you need to distinguish it from a query in a different query language, "a query in SQL".

Re: Learn SQL Interactively on Khan Academy

#16

Post by strayptr »

kremlin wrote: post #11

I'm doing the course, as it's something I haven't learned in depth yet. They mentioned pronunciation : 'S-Q-L' vs 'sequel'. I've always pronounced it S-Q-L. The lecturer implies there's no right answer, that 'sequel' is historical but 'S-Q-L' is preferred for international use. The annoying thing, though, is that in writing a choice has to be made. If someone pronounces it 'S-Q-L' then to read 'a SQL query' is weird…

I believe it's written "[Aa]n? (sql|SQL) query" but it depends on which standard library your native language is using.

Re: Learn SQL Interactively on Khan Academy

#17

Post by marpstar »

kremlin wrote: post #11

I'm doing the course, as it's something I haven't learned in depth yet. They mentioned pronunciation : 'S-Q-L' vs 'sequel'. I've always pronounced it S-Q-L. The lecturer implies there's no right answer, that 'sequel' is historical but 'S-Q-L' is preferred for international use. The annoying thing, though, is that in writing a choice has to be made. If someone pronounces it 'S-Q-L' then to read 'a SQL query' is weird…

I always pronounced it 'S-Q-L' until I got a job where everyone says "sequel". Now I just say "sequel" to fit in, and because it's fewer syllables. Even if a text said "an SQL query", I would read it "a sequel query" without even thinking about it.

Re: Learn SQL Interactively on Khan Academy

#18

Post by function_seven »

kremlin wrote: post #11

I'm doing the course, as it's something I haven't learned in depth yet. They mentioned pronunciation : 'S-Q-L' vs 'sequel'. I've always pronounced it S-Q-L. The lecturer implies there's no right answer, that 'sequel' is historical but 'S-Q-L' is preferred for international use. The annoying thing, though, is that in writing a choice has to be made. If someone pronounces it 'S-Q-L' then to read 'a SQL query' is weird…

Wow. I never realized it but the author's choice of a/an dictates how I read it in my head. Without even thinking about it, if I see "an SQL query" I read it as "an es-queue-ell query". If it's written as "a SQL query", then I read "a sequel query"

But that doesn't answer your question. I suppose it's the same as when saying it. Pick one and stick with it, whatever your choice.

Re: Learn SQL Interactively on Khan Academy

#19

Post by themartorana »

kremlin wrote: post #11

I'm doing the course, as it's something I haven't learned in depth yet. They mentioned pronunciation : 'S-Q-L' vs 'sequel'. I've always pronounced it S-Q-L. The lecturer implies there's no right answer, that 'sequel' is historical but 'S-Q-L' is preferred for international use. The annoying thing, though, is that in writing a choice has to be made. If someone pronounces it 'S-Q-L' then to read 'a SQL query' is weird…

This is a question for English.StackExchange.

http://english.stackexchange.com/questions/5265/an-sql-serve...

http://english.stackexchange.com/questions/1016/do-you-use-a...

That said... As a native English speaker, I can infer your pronunciation from which of the options of "a" and "an" you decide to use.

FWIW, "an" is appropriate for any word starting with a vowel sound (whether or not it actually starts with a vowel) and inappropriate for any word that doesn't. "An historic" drives me nuts, but I'm one of those jerks. (My mother was an English teacher - I never stood an chance!)

Re: Learn SQL Interactively on Khan Academy

#20

Post by derefr »

kremlin wrote: post #11

I'm doing the course, as it's something I haven't learned in depth yet. They mentioned pronunciation : 'S-Q-L' vs 'sequel'. I've always pronounced it S-Q-L. The lecturer implies there's no right answer, that 'sequel' is historical but 'S-Q-L' is preferred for international use. The annoying thing, though, is that in writing a choice has to be made. If someone pronounces it 'S-Q-L' then to read 'a SQL query' is weird…

Generally in English, I think that when it's unclear whether the majority considers an abbreviation to be an acronym or a plain initialism, it's proper to treat the abbreviation as an initialism.

Importantly, people who have only ever read the abbreviation, and not heard it spoken aloud, will assume it's a plain initialism. It's better, I would think, to write something that reads properly to these people—something "more accessible."

The people who are aware of the acronym pronunciation, meanwhile, will be able to adapt their reading either way, because they're also aware that a plain-initialism reading exists, so you're not unduly burdening them in parsing the sentence.

Post reply on HN