bosatsu / codecademy_sql_capstone Goto Github PK

https://github.com/bosatsu/sql-scratch-capstone-turn-in/blob/111b8428778b6b2c39c071e4cef384b488072eb6/CodeAcademy%20SQL%20Capstone/code.sql#L30-L33

For cleaner code, this could all be defined as a separate table to be called upon when determining first touch counts.

Otherwise, very good use of code 👍

Without opening the presentation file, it is hard to tell which capstone project you worked on. Consider including the name of the capstone in the filename or as a /* comment in the coding.

Rubric Score: 14/16

Criteria 1: Report: Are conclusions clear and supported by evidence in all eight answers?

• _Score Level: 2
• _Comment(s): There were some fine detail questions that were missing answers in the presentation. From the code, it is clear that you were able to get these results, so it's important to include even the smallest detail. You are missing information on the total number of purchases that were made and what the typical user journey was [whether predicted or extrapolated from the data]. It might help to include a slide at the beginning of the questions you aim to answer so you can use it as a checklist of what needs to be included in the slides.

Criteria 2: Query Accuracy: Do queries do what they were supposed to do?

• _Score Level: 4
• _Comment(s): The code was accurate and you were able to retrieve the right answers from the data.

Criteria 3: Query Formatting

• _Score Level: 4
• _Comment(s): Your code followed the style guide for how to write clear SQL code.

Criteria 4: Understanding the underlying concepts and terminology

• _Score Level: 4
• _Comment(s): The presentation was absolutely beautiful! It was clear you understood the data and how to express your findings. There were parts you could have elaborated on, like which utm_source paired with which utm_campaign was the most effective, but that's me being nitpicky.

Overall Score: 14/16

NICE JOB! Your presentation was one of the best I've seen so far, and it's clear you understood data manipulation. I encourage you to play around with the data more to see if you discover anything new, and maybe even work on graphical visualization of the data [pie charts, bar graphs, etc] if you happen to know how to do that.

https://github.com/bosatsu/sql-scratch-capstone-turn-in/blob/111b8428778b6b2c39c071e4cef384b488072eb6/CodeAcademy%20SQL%20Capstone/code.sql#L46-L49

Same as #2

https://github.com/bosatsu/sql-scratch-capstone-turn-in/blob/111b8428778b6b2c39c071e4cef384b488072eb6/CodeAcademy%20SQL%20Capstone/code.sql#L55

Just being nitpicky, you could also include the page_name column for analysis to double check your result.