ImmersiveAmbientModecolor: #d5adac (color 2)
Video Format : 22 (720p) openh264 ( https://github.com/cisco/openh264) mp4a.40.2 | 44100Hz
Audio Format: Opus - Normalized audio
PokeTubeEncryptID: e6af413bed6a778a54930cbefbf9e90058e9b5f1f4b2270a8f2d7e1a2b33093dee877d5c4e6448224ef8fbb072abde3f
Proxy : eu-proxy.poketube.fun - refresh the page to change the proxy location
Date : 1715890347625 - unknown on Apple WebKit
Mystery text : ejhMMjAyRmxtRDQgaSAgbG92ICB1IGV1LXByb3h5LnBva2V0dWJlLmZ1bg==
143 : true
181,579 Views β’ Apr 14, 2024 β’ Click to toggle off description
- The Asianometry Newsletter: www.asianometry.com/
- Patreon: www.patreon.com/Asianometry
- Threads: www.threads.net/@asianometry
- Twitter: twitter.com/asianometry
Views : 181,579
Genre: Education
Date of upload: Apr 14, 2024 ^^
Rating : 4.971 (61/8,475 LTDR)
RYD date created : 2024-05-16T20:05:51.65315Z
See in json
YouTube Comments - 526 Comments
Top Comments of this video!! :3
I once was interviewed for a senior development position with a major multinational bank with their database guru. He was the one man who knew how the bank managed all of its data. He revealed that they had just one database. It had 600 tables. There were no joins, no relationships, no structure; It was just a massive dumping ground. Trades, transactions, accounts, β¦ everything. The goal was to take this unholy mess and redo something better, while keeping all the existing business units running without interruption. It was an Oracle database.
168 |
βCodd, despite having a fishy name β π π
241 |
Study math, fly bombers, invent the dominant database structure. What a life!
272 |
As a pre-SQL programmer, SQL was a game changer. Using SQL gave me a logical, abstract view of the data structure, significantly reduced my design and coding time, and allowed changes to the database structure without having to break code or migrate data.
I used several systems on PCs like DBase and Firefox which had SQL database at their core.
Also need to remember that systems back then were so constrained by CPU performance, memory storage, and disk capacity that SQL would have been too large to run on some of the early computers.
Great video as always!
209 |
I'd argue that SQL is one of the most successful inventions of computer science, on the level of C or even more so.
Nothing better has come up despite decades of attempts, and pretty much all complex datastores eventually support SQL as they grow.
88 |
SQL is so useful. And you can learn 90% of what you need in two weeks. There's a reason it's so ubiquitous.
13 |
"Codd, despite having a fishy name, did not want this." ππππ
64 |
Database researcher and university professor here: Very good presentation as usual, though it of course ends with the state of things in the mid 1980s and a lot has happened since, not just in academia but also in industry. As early relational DMBS go, IBM's System R (which has been alluded to in the video but not named and whose DNA lives on to this day in IBM DB2) has had significantly higher impact and relevance than Ingres. Since you mentioned Boyce and Stonebraker, a number of others would have deserved mention at least as much, such as Jim Gray or Pat Selinger. Also, you added to my pain as an academic trying to attract young researchers into the field by making databases look real bland and boring (though important to business). Unfortunately, so many undergrad courses do the same. There is beautiful systems and theory research to be done, and there are interesting fundamental questions that arise here that are much cooler than anything mentioned in this video (though ultimately enabled by Codd).
98 |
As a newish developer, of all videos, this was the most exciting to see when I saw the thumbnail. SQL has become one the foundational blocks of software development and even today, when all the competing NoSQL paradigms (MongoDB, Firebase, Redis, etc) have claimed a space in database management, we are coming back to SQL with new ideas thanks to PostgreSQL and SQLite related projects like Turso and libSQL.
And I really like the image in 14:50 while distant in time is so relatable to my knowledge. A testament on how SQL stood the test of time and won.
Really thanks Jon for this video.
94 |
Moral of the story: Concepts are great for awards but actual working code/products can make you rich.
54 |
I had the privilege of digitising some Betamax tapes from the Australian Computer Society many years ago from the 10th Australian Computer Conference held in 1983. Chris Date, a relational database expert, gave a presentation on one of these tapes and made many claims about what the future would be for databases. "Like it or not, SQL is going to become a very important language. It might become an actual standard, and it almost certainly will become a de facto standard."
The full speech is here https://www.youtube.com/watch?v=VnNbddUMZQI
89 |
Being a DBA student, it's interesting to see where all modern concepts began.
46 |
There are literally billions of SQL databases in this world, yet very few people knew where or how it got started until now.
Thanks again, Jon.
94 |
I've been using SQL since September 1999. Database programmer has never been my formal title, but I have been one for 25 years this fall, in addition to my main programming job that's normally identified by the other programming language. It's been SQL the whole time, but the other language has gone from C to Perl to PHP to Java over the decades. What makes SQL different from other programming languages is that it's used by far more than just programmers. I've seen programmers write horrible SQL and non-programmers write terrific SQL. If you can wrap your mind around set calculus you'll become very good at SQL, and you don't need to be a programmer at all. Either way, practice helps. I was only what I would consider good at SQL after 15 years and I'm now fairly proficient at SQL such that I can jump right into any database get going.
7 |
Really enjoyed that, but then I do have a 35 year SQL career behind me. Furthermore, almost all of it was new to me despite my extended immersion.
I have to be honest, when I hear Codd's name, I usually switch off: it's usually in relation to Codd's Rules, academic rules of thumb that in practice are nothing more than common sense and second nature in this line of work. I watched a video on them that I happened to stumble across a few months ago, and yes, it is all common sense codified into a set of rules. So I congratulate you in managing to do a 20 minute video on SQL without ever referring to Codd's Rules!
33 |
I work in a social work/SUD treatment agency, and we somewhat recently began working with a company that helped us get backend data out of the cloud database. I haven't worked with SQL since college... The last few months have been a blast, and believe you me, I've been able to flex comp sci skills in a very not comp sci industry haha.
10 |
I have to profess my love of this channel and your content. I don't know how I was lured into this channel at first, I'm not Asian, and I'm just a mere MSP technician who grew up in the 80s and 90s. But you always seem to hit the right note, and Sunday nights haven't been the same since. You're doing it right, sir. π€© I eat these videos up, and wanted to say "thanks".
27 |
Your videos are so important. Documenting and popularising the foundational building blocks of our modern world.
34 |
I like how You dig out filthy details: "Deliverability, Redundancy and Consistency of Relations stored in Large Data Banks" with the exact date on it +++
10 |
@richchinnici6182
1 month ago
As a much younger software engineer, I still remember this phrase I was taught regarding relational database development. The key, the whole key, and nothing but the key. So help me Codd.
635 |