Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Analysing Dask user questions to better understand usage / user pain #288

Open
avriiil opened this issue Nov 10, 2022 · 2 comments
Open

Comments

@avriiil
Copy link

avriiil commented Nov 10, 2022

I'm starting to dig more deeply into Dask user experience. I'd like to experiment with a more data-driven approach based on the various places where we interact with Dask users, specifically StackOverflow, Discourse and Github.

As a first step in that direction I've been playing around with scraping all StackOverflow questions and running some basic analyses on that data. Pretty rudimentary still atm but thought I'd share here for visibility and feedback.

Some Interesting Findings

  1. Most popular questions (by views)

Interesting to see a mix of pandas-related questions (expected) as well as Parquet and Spark-related questions. A list like this could be used to inform Dask messaging and content creation on the blog or social channels. These are clearly the topics folks are interested in most.

image

  1. Most popular tags

These are the top 10 most popular "sub-tags". Assuming that all "pandas"-tagged questions are DataFrame questions, that would mean that almost half of the questions (48.7%) are related to Dask DataFrame.

image

Possible Next Steps

It would be interesting to:

  • Run topic modelling on the full questions to get more fine-grained understanding of what folks are running into
  • include timestamp data to see how questions/usage seems to change over time
  • Build out analyses for other platforms and compare -- I'd be curious to see if particular platforms see more activity around particular Dask Collections, for example.
  • ...much more to dig into, I'm sure...

I'm going to keep chugging ahead here but would welcome any feedback and further discussion. If anyone's interested in helping me build out analyses for Discourse and Github, I'd be very happy to join forces.

NOTEBOOK: https://github.com/rrpelgrim/dask-stackoverflow/blob/main/scrape-stackoverflow.ipynb

@avriiil avriiil changed the title Analysing Dask user questions to Analysing Dask user questions to better understand user pain Nov 10, 2022
@avriiil avriiil changed the title Analysing Dask user questions to better understand user pain Analysing Dask user questions to better understand usage / user pain Nov 10, 2022
@avriiil
Copy link
Author

avriiil commented Nov 10, 2022

For quick comparison, here's a screenshot of Discourse categories:

image

And highest-traffic Github issue labels:

image

Does anyone here have experience using the Github API to fetch and run analyses on repo data?

@mrocklin
Copy link
Member

Thanks for doing this @rrpelgrim . I'd like to also suggest that you read through a bunch of the top issues (maybe 100 or so?) to get a feel for them as well. I think that getting dirty with the actual questions is important to understand things. I welcome the quantitative analysis that you've done here. I'd like to also encourage you to get in and get qualitative as well. I suspect that it gives a different kind of knowledge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants