this post was submitted on 19 Oct 2023
1707 points (98.8% liked)
Programmer Humor
32464 readers
428 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The phrase "SQL programmers" is so fucking weird. SQL isn't a programming language. It's a query language. You don't "program" things with SQL. You utilize SQL as a component of programs for data insertion and lookup, but the actual logic of execution is done in a programming language. Unless you're doing Oracle PL/SQL, in which case why are you giving money to Oracle?
Edit: Damn, this comment made people mad.
Your knowledge of data engineering may be limited. SQL is predominant in data processing nowadays. FOSS tools such as DBT allows to write efficient data processing pipelines with SQL and some YAML config without the need for a general purpose coding language.
Why would anyone want that? Because SQL has the interesting property of describing the result you want rather than describing how to compute it. So you can put inside the database, a query engine with decades of optimizations, that will make a much better job at finding the best execution plan than the average developer.
It also means it's easier to train people for data processing nowadays.
Learning DBT was pretty easy for me as a data analyst. Now I’m contributing to my company’s data warehouse instead of just pulling existing data.
Most database engines support stored procedures. You don't need to give money to oracle, you can give it to Microsoft instead.
Or not at all? Postgres? MariaDB? I think I missed the /s. I'm slow hah
Yes, those work :-) giving money to MS was more of a joke.
T-SQL is turing complete. While the MS SQL server has limitations on OS level operations, if you allow yourself some leeway with CLR wrappers for the win32 API, there's no reason I can think of you wouldn't be able to get the database engine to be a webserver reacting to incoming requests on port 80, or drawing GUIs based off of table state.
It's be slow and terrible, but doable.
It's doable. Personal experience
I'm a markdown programmer and i disagree with this statement
LaTeX being called "programming" I can see, but I've never heard someone try to justify Markdown as programming. It's just formalizing things people were already doing to format text in plain text files into approximately half of a standard.
This doesn't make sense to me. SPs and functions are in every major database. If I wrote a bash script that runs like a program, and sounds like a program, did I program it? Script it?
And lots of systems have nested logic in the DB, optimization often leads to that to reduce overhead. Unless you're being lazy with an ORM like prisma that can't even join properly.
Getting high performing queries is just as difficult as any other programming language, and should be treated as such. Even Lemmy's huge performance increases to .18ish came from big PG optimizations.
It seems to be about yelling at others that "you're not a real programmer!!!" mixed with being so "technically correct" my eyes can no longer roll the same way they used to.
It's mostly ignorance. People tend to underestimate or dismiss things they don't completely understand.
Admittedly, this discussion is more one of semantics than anything. It's pretty clear I'm arguing that SQL is not a "General Purpose Language," and that proficiency in that domain is what constitutes programming. Which, yeah, is arguably somewhat arbitrary. But my point is that, colloquially, someone who only works with SQL isn't a programmer. Data Engineer, sure. DBA. Also, sure. Depends on what you do. Programmer? Not really. Not unless you (as in the person, not "it's theoretically possible") can use raw SQL to read in video data from a linux system device file and then encode it to mp4 and just nobody's told me.
Do that in Javascript. Or HTML. Or CSS. Or by that logic is a web developer not a programmer? What about microcontroller programmers?
I could easily write a full logic program in SQL where the API just feeds it data, which is the inverse of how you treat SQL. Admittedly that's not as common, but it happens pretty frequently in areas of big data, like medical.
I've hired Senior Software Engineers that were DBAs, and others that weren't. They were a development team, all programmers in their own right.
SQL is turing complete
So is PowerPoint
So is Magic: The Gathering
I'm a magic the gathering programmer
So is Tex. And, yet, I still don't put it under the "programming languages I know" section on my resume. Probably because it's not a programming language.
Try it. Maybe you won't need a resume anymore.
It's important to keep an up to date resume, even if you're employed. That's a little life pro tip for you kids out there, with your iphones and your tik toks and your Fortnite dances and your existential malaise brought about by encroaching climate disaster and advanced technoindustrial capitalism.
What section would you put it under? It isn't clear to me where it would fit
Where you put it is not my problem.
The general census is that latex actually is an example of programming languages sharing semantics with non programming languages and not being intend as a programming language.
since you linked to wikipedia:
Programming language
Sometimes even non Turing complete languages are considered a programming language but Turing completeness usually is the criteria agreed upon:
Why not? It sounds like you haven't written any OLAP queries :)
I've written ETL data pipelines using a system similar to Apache Airflow, where most of the logic is in SQL (either Presto or Apache Spark) with small pieces of Python to glue things together. Queries that are thousands of lines long that take ~30 minutes to run and do all sorts of transformations to the data. They run once per day, overnight. I'd definitely call that programming.
Most database systems support stored procedures, which are just like functions - you give them some input and they give you some output and/or perform some side effects.
Oh yea!!! Well I have 76 lines of code that takes up to 18 hours to run for 1 client!!!!!
/s
Haha I only mentioned the run time to provide some context, since a lot of people have only ran OLTP queries that take less than a few seconds to run.
stored procedures
MS SQL Server has this thing called Replication. It's a feature to keep tables in sync between databases, and even database servers. There's merge replication (two way), snapshot replication (one way scheduled publishing), and transaction replication (one way live-ish publishing).
And the logic is all implemented in T-SQL stored procedures.
I fucking hate it.
Me losing my mind in 3000 lines of Oracle PL/SQL processing scripts in a Bank some time ago agrees with your last statement.
This comment has a concerning amount of replies. Its just semantic BS.
Bahahahhahahahhahahahhahahaa. No.