Skip to main content

How My Job Experience Shapes the Way I Learn SQL

As a college student working toward my Computer Science degree, I’ve been lucky to learn SQL both in the classroom and on the job. At work, I’ve used tools like Smartsheet and an LMS to track training data, and those experiences showed me the importance of being able to ask good questions of data. Now that I’m studying SQL more deeply, I see how powerful it is compared to just managing spreadsheets.

What I find most interesting is that SQL isn’t only about joining tables by IDs. Sometimes real-world logic is more complex. For example, I’ve seen training systems where eligibility isn’t just a key match, but based on conditions—like “employees can only register for courses if their years of experience exceed the course’s minimum requirement.” In SQL, I can capture that logic with a simple query:

SELECT e.employee_id, e.name, c.course_id, c.title FROM employees e
JOIN courses c ON e.years_experience > c.min_years_required;

This goes beyond what I could easily do in Smartsheet or Excel and shows how SQL can reflect actual business rules.

As I continue learning, I’m also diving into Power BI, which makes me appreciate SQL even more. SQL is the foundation that prepares data, while Power BI helps turn it into visuals and dashboards that people can act on. I find SQL fairly straightforward to learn, but the harder parts are translating English questions into precise code—especially when it involves grouping (GROUP BY/ HAVING), handling NULL values, or working with multi-table joins. That’s where I need to slow down and think critically.

Overall, combining what I’ve learned from my job with what I’m studying in school and in Power BI gives me a clearer picture of how data flows: from raw information in a database, to queries in SQL, to insights in dashboards. For me, it feels like I’m building the skill set to not just manage data, but to actually tell its story.

Comments

Popular posts from this blog

CST383: Learning Probability Distributions and Data Visualization in Python

This week, I learned more about probability distributions, density plots, histograms, and how to visualize data using Python libraries such as Pandas, Matplotlib, Seaborn, and SciPy. I practiced creating density plots, box plots, cumulative density plots, and histograms using real datasets. I also learned how changing things like bin width, bandwidth, transparency, and sample size can affect the appearance and interpretation of graphs. Another important topic was understanding skewness and how transformations such as log10 can help make heavily skewed data easier to analyze. One thing I found interesting was how probability density functions (PDFs) and histograms can represent the same data differently. Before this week, I thought graphs mostly showed the same information in different styles, but now I understand that each type of plot has a different purpose and can make patterns easier or harder to notice. I also learned that larger sample sizes tend to reflect the true distribution...

Choosing Between MongoDB and MySQL

This week I learned more about how MongoDB and MySQL are both powerful tools for managing data, but they serve different purposes. MySQL is a relational database that organizes data into tables with rows and columns. It uses SQL (Structured Query Language) to define and manage data, which makes it very structured and reliable. MongoDB, on the other hand, is a NoSQL database that stores data as documents in a flexible JSON-like format . It does not require a fixed schema, so it is easier to change or add new data types as needed. Both databases are similar because they can handle large amounts of data, support indexing for faster searches, and allow users to perform queries to get specific information. They are also widely used in modern applications and can be connected to programming languages like Java, Python, or C++. However, the key difference is how they store and organize data. MySQL is best when data has clear relationships, such as in school systems, banking, or employee ...

CST383 Week 1: Python for Data Science

This week, I learned the basics of Python for data science and how tools like NumPy are used. I already have programming experience from my computer science classes, but Python feels different from languages like Java or C++. It is easier to write and more flexible because it does not require strict data types. This makes coding faster, but I also need to be careful to avoid mistakes. We also learned about the Python data science ecosystem, such as NumPy, Pandas, and tools like Google Colab and Jupyter Notebook. I liked using Google Colab because it is simple and runs in the browser, so I don’t need to install anything. However, I am curious when it is better to use local tools like Spyder or Jupyter instead of Colab. The most important concept for me this week was NumPy. I learned that NumPy arrays are much faster than Python lists because they store data in a continuous block of memory and use the same data type. This connects to what I learned in my algorithms class, where performan...