I have a question I'm going to throw out there for HN. How many of you bounce back and forth between SQL and Python, even though you could stick within SQL alone? For example, one question (Airbnb) was about year-over-year growth by looking at the count of hosts registered for each year. I might be inclined to go as far as getting the count through SQL, but then (maybe in a notebook) just write the rest in python.
I'm not asking how many people use SQL and Python together (my guess is almost everyone does), I mean how often do you use SQL just for the select, join, filtering and aggregation, but then go to python even though you know there's a way to do this without leaving SQL?
I recommend two modifications:
1) Disable Navigating Forwards/Backwards in the browser, like Jupyter Notebook
2) Make use of HTML5's localstorage / HTML Web Storage for each challenge.
"Find the search details made by people who searched for apartments designed for a single-person stay."[0] This could be interpreted to mean some refined version of the following:
select * from airbnb_search_details WHERE accommodates = 1 AND property_type LIKE 'Apartment';
However, the expected output includes non-apartments, for example Houses. The expected output matches the following query instead:
SELECT * FROM airbnb_search_details WHERE accommodates = 1 AND beds = 1;
What do you think users should take away from the experience of completing this question?
0: https://platform.stratascratch.com/edu-content-editor?id=961...
My implementation of having 1 solution isn't good enough. I plan on adding a discussion forum to discuss these exact topics.
But thank you for the kind words. I appreciate you taking the time to look at it.