SQL cohort kickoff
- A cohort-style SQL lesson began with a blank screen and a business problem, not queries or tables. - The exercise asked participants to design tables for Organisation, Subscription, Invoice and Payment to model billing flows. - The session and ERD examples were shared on X by iam_daniiell today. (x.com)
A SQL lesson shared Monday, April 20, opened with a billing problem and a blank canvas, not a list of commands. (x.com) Daniel Daniel, who uses the handle iam_daniiell, posted screenshots from the session on X and tied the exercise to four tables: Organisation, Subscription, Invoice, and Payment. His public profile describes him as an analytics engineer and SQL instructor running live data training. (x.com) (linktr.ee) The task started with a business flow most software companies recognize: an organisation signs up, gets a subscription, receives invoices, and makes payments over time. The point was to decide what each table should store and how the records should connect before writing queries. (x.com) (learn.microsoft.com) In a relational database, a table is a structured list of records, and a foreign key is the column that links one table to another. PostgreSQL and MySQL documentation both describe foreign keys as the mechanism that keeps related rows consistent across parent and child tables. (postgresql.org) (dev.mysql.com) That is why billing systems are often taught through schema design first. Microsoft’s database guidance describes normalization as organizing data into related tables to reduce duplication and inconsistent updates. (learn.microsoft.com) The four-table setup forces beginners to make concrete choices. One organisation can hold more than one subscription over time, a subscription can generate many invoices, and an invoice may map to one or more payments depending on whether a customer pays in full or in parts. (docs.aws.amazon.com) (docs.oracle.com) The screenshots Daniel shared included entity-relationship diagrams, or maps of tables and their links, rather than finished SQL answers. Database design guides describe those diagrams as a way to define entities, primary keys, and relationships before a system is built. (x.com) (solarwinds.com) That teaching style shifts the first question from “What query do I write?” to “What business event am I storing?” In this case, the events are signup, billing, invoicing, and payment, each with its own record and date trail. (x.com) (docs.aws.amazon.com) Daniel’s Linktree lists a paid “Data With Danny” cohort program priced at $80 and describes it as a four-month data analytics training track. The Monday post shows that at least one SQL session in that program began with data modeling instead of syntax drills. (linktr.ee) (x.com) The blank screen mattered because it made students define the business before the database. By the time queries arrive, the lesson suggests, the structure should already explain the story the data needs to tell. (x.com) (learn.microsoft.com)