Week 9 : SQL Gets Complicated…

This week was about learning that my discomfort is actually a good thing. It means I’m learning.

The beginning of the week felt easy. I breezed through Chapter 1 of SQL and felt like I had momentum. I was getting comfortable with the syntax and moving quickly.

Things got harder when I reached Chapter 3 and more complex queries. I started making more mistakes, and I felt like I wasn’t writing enough code to truly solidify what I was learning. The biggest challenge wasn’t just syntax — it was figuring out how to logically pull the right information from multiple tables and translate what a prompt was really asking into a working query.

After reflecting, I don’t think this week was a failure. Slowing down doesn’t mean I’m not making progress — it means the material is finally demanding a deeper level of understanding. I’m moving from memorizing patterns to thinking relationally: understanding how tables connect, what level the result should exist at, and how to build a query that matches that logic.

My plan to tackle this is to get more systematic:

• Start by identifying what the output should be (what the prompt is actually asking for).
• Decide the “level” the result should return at (student-level, section-level, etc.).
• Work backward from there to determine which tables and joins are required.
• Start with a small SELECT and run it often as I add pieces — one change at a time.
• Use grouping and aggregation only after the structure is correct.
• Remind myself: if the question is being asked, a solution exists — and I have the tools to find it.

This week didn’t increase my speed. It increased my depth. And I think that’s the kind of progress that actually matters.