30 Days of SQL: JOINS

Joins were a battle hard won.

This is the point I quit the last time. The spot where everything came to a halt.
Not because I couldn’t do it. But because I believed I couldn’t.

This isn’t my first go at learning SQL. I tried it about a year ago. Everything was smooth until I hit:

• INNER JOIN

• OUTER JOIN

• LEFT JOIN

• RIGHT JOIN

And suddenly, it all felt like gibberish. Which was frustrating, because up to that point, SQL had made sense. But once JOINS came up, I froze. I walked away.

This time? It still wasn’t easy.

I remembered the terms. I couldn’t grasp the concept.
Not until I started working with it.

ChatGPT became my professor. He drilled me until I finally said,
“Take me back to 101.”

And from there, we rebuilt.

• LEFT JOIN = "Show me everything from the left, and try to match the right."

• RIGHT JOIN = "Show me everything from the right, and try to match the left."

• INNER JOIN = "Only show me where both sides agree."

• FULL JOIN = "Show me everything. Match what you can. Otherwise, NULL it."

Then I finally got the syntax right. I started to see SQL as a sentence:

SELECT what_you_need  
FROM first_table  
[JOIN TYPE] second_table  
ON first_table.id = second_table.id

Yes, it gets more complicated than that—but this was the win I needed.

The real win wasn’t just technical. It was mental.
It was breaking the old pattern of:
“I’m not going to get this. I suck. This is too hard.”

Instead, I found what worked for me:
📌 Doing the problems myself, not just watching videos
📌 Breaking it down with plain language
📌 Practicing, failing, and being guided back without judgment

Now I can move forward.

If you’ve hit a wall with joins, or with anything in SQL, remember:
You don’t have to be perfect. You just have to return.

☕ If you liked this and want to support the journey, you can buy me a coffee—every little boost helps keep the pawprints moving.