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

2018 state of Haskell survey results #148

Merged
merged 12 commits into from Nov 18, 2018

Conversation

Projects
None yet
2 participants
@tfausak
Copy link
Owner

commented Nov 16, 2018

Still very much a work in progress. I'm hoping to get this published tomorrow, but we'll see about that.

@tfausak tfausak force-pushed the 2018-survey-results branch from 750703e to 91a55fc Nov 16, 2018

@tfausak tfausak force-pushed the 2018-survey-results branch from 91a55fc to 76b2c40 Nov 16, 2018

Fix typo
Co-Authored-By: tfausak <taylor@fausak.me>
@tfausak

This comment has been minimized.

Copy link
Owner Author

commented Nov 18, 2018

It seems that someone may have submitted a bunch of bogus results. Discussion is happening on the haskell-community mailing list: https://mail.haskell.org/pipermail/haskell-community/2018-November/000358.html

@tfausak

This comment has been minimized.

Copy link
Owner Author

commented Nov 18, 2018

I updated my script to ignore the bogus submissions. Of the 5,096 responses, 3,417 were ignored, leaving 1,679 legitimate responses. You can see the exact script that I used to prune the responses and produce the charts and tables here: https://gist.github.com/tfausak/cc381ddd0ddd8304cc3eae6250966f55/0dd7415b657c2f361bbbbf305b1db869803a2c40

I will not be providing a CSV with all 5,096 responses due to the likelihood of misuse. If someone is interested in the full data set, they can download it from the Git history here: https://github.com/tfausak/tfausak.github.io/blob/94b537aafe259ffb6093c239aeafb8e7a40dd22a/static/pages/2018-11-16-2018-state-of-haskell-survey-results.csv.zip

This announcement post will only include results from the 1,679 legitimate responses. If further problems are found with this limited data set, it is easy enough to re-run the script to produce new artifacts. In fact, I encourage others to do just that in order to verify that I have not misrepresented the results.

I need to re-write the introduction to account for these shenanigans, but otherwise this post is ready to go.

@tfausak

This comment has been minimized.

Copy link
Owner Author

commented Nov 18, 2018

Ok, the script has been updated again to remove even more bogus responses. Hopefully the third time's a charm here.

tfausak added some commits Nov 18, 2018

@tfausak tfausak merged commit 9fc6b91 into master Nov 18, 2018

2 checks passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
continuous-integration/travis-ci/push The Travis CI build passed
Details

@tfausak tfausak deleted the 2018-survey-results branch Nov 18, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.