?

Log in

Recent Entries Friends Archive Profile Tags
 
 
 
 
 
 
Cool! I made the Stack Exchange Year in Review. :-)

If you enjoy analyzing data about the Stack Exchange network, 2016 was your year. Community member Monica Cellio wrote a tutorial about our data explorer, which is maintained by another community member, Tim Stone. A resident data scientist, David Robinson, released StackLite, a lightweight version of community data. To see it in action, consider scripting language trends on Stack Overflow. In December, we connected our data to Google's BigQuery. People are already finding interesting results. Our data team has been posting analysis on the blog, if you crave more.
(There are other links in that paragraph that I didn't recreate in this post. You'll need to go to their blog post to get those.)

The link in the quote is to the blog post where they announced the tutorial (in June):

Have you ever wanted to get a statistic about your favorite Stack Exchange site, but been baffled by exactly how to do that? The Stack Exchange Data Explorer (SEDE) may be just what you're looking for. SEDE was created to make it easy to query and browse the public data that we release periodically for all Stack Exchange sites, but a lack of familiarity with SQL has been a barrier to many of you who would otherwise benefit from it. Now, thanks to friend of the company and moderator extraordinare Monica Cellio, you have a tutorial to guide you in using it!

[...] But even though SEDE is nicer to work with than a raw data dump, it can still be pretty intimidating to new users, especially those who aren't trained database engineers. Up until now, the Data Explorer's own help docs have been a little thin, and mostly covered very specialized, advanced features. We've wanted to expand the guidance there for a while, but never quite got around to it. Then Monica rewarded our procrastination by helpfully volunteering to take on the writing.

Originally posted at http://cellio.dreamwidth.org/1995955.html. comment count unavailable comments there. Reply there (preferred) or here.
 
 
 
 
 
 
Congrats and well done!