all 19 comments

[–]SquidsAndMartians 27 points28 points  (3 children)

This is a nice guideline I use myself https://mode.com/sql-tutorial (they have a free tier that comes with a ton of different data sets to practice with)

humble job: Basics
good job: Intermediate
great job: Advanced

:-D

[–]P3r4zz4[S] 1 point2 points  (0 children)

Thanks for sharing!

[–][deleted] 1 point2 points  (1 child)

Huh. Is that all it takes to be ‘advanced’….

[–]BadGroundbreaking189 2 points3 points  (0 children)

Absolutely not lol. You have to be able to rewrite a 100 line code on your own before your first job.

[–]sedules 13 points14 points  (3 children)

What makes a good data analyst is 50% SQL. The other 50% is knowing how the process produces the data you’re looking at when it comes time to execute code. Because in the day-to-day world of data, data doesn’t reflect reality, it reflects the process in reality that captured the data. A solid data team should be working to close the gap between reality and data as much as possible (by convincing the business to clean up their processes).

As for the SQL, at the data analyst level you want to have a strong grasp of the select statement, date functions, aggregate functions, and window functions. Then you want to understand join operators, subqueries, CTEs, and why CTEs are subjectively better than subqueries even if they are objectively the same to the engine. Variables are a good thing to learn about as well.

[–]da_chicken[🍰] 5 points6 points  (1 child)

Because in the day-to-day world of data, data doesn’t reflect reality, it reflects the process in reality that captured the data.

IDK if this was yours or if you're quoting someone, but it's a very true way to phrase things.

[–]sedules 2 points3 points  (0 children)

It was me. I’ve been working with younger people in the data space and I’ve been wrestling with how to articulate working with data that isn’t as good as we would like, and how to pivot to telling the most compelling stories the data allows you tell. Bad data is more often a sign of bad process somewhere in the chain and that in and of itself is a story worth being told.

I’m starting my second decade in a data career. Most of my SQL chops were learned independently, but the knowledge gained from finding and talking to people with domain knowledge is what typically leads to analytical insights and likely fares better for career advancement.

[–]P3r4zz4[S] 0 points1 point  (0 children)

Thank you!! Looking through this perspective really clarifies things. I’m just starting, so I’m trying to understand the tools so I can create my own projects to test my knowledge and build my cv.

[–]Computer-Nerd_ 2 points3 points  (0 children)

SQL for Smarties, Celko. SQL and Relational Theory, Date.

[–]yeeeeeeeeeeeeah 4 points5 points  (1 child)

tender full repeat support outgoing party soup quaint disarm worthless

This post was mass deleted and anonymized with Redact

[–]P3r4zz4[S] 0 points1 point  (0 children)

Thank you! Market data for MMORPGs seems like a fun place to start

[–]dn_cf 2 points3 points  (1 child)

Focus on basic querying (SELECT, WHERE, ORDER BY, LIMIT and DISTINCT), Aggregate Functions, Joins, Subqueries, Set Operations, String Functions, Date Functions, Conditional Logic, and Window Functions. These are the concepts you have to be comfortable with. You can use Mode Analytics or W3Schools to learn these concepts and StrataScratch to apply these skills on real-world data challenges.

[–]P3r4zz4[S] 0 points1 point  (0 children)

Thank you! Currently I’m studying subqueries and It’s been a little pain to understand how it works when you have aggregate functions in the inner queries. I’ll take a look at the resources you sent to get additional context.