Stack Overflow survey data pivot service #3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
download survey files on start fix eq filter, more survey columns
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is still work in progress but you can already use it to do basic queries against 2016 survey data.
Unfortunately, SO survey files have different format through years, so I will have to parse each year separately.
Also, what is your opinion on enumerated values?
E.g. SO survey has list of techs user can choose from.
As a result, we have a field storing all user preferred techs like "C#; Dart; Java; JavaScript; etc."
Returning this in a single field does not provide much value as you cannot do filtering/grouping on it.
I guess I could split this into separate fields like C#=true;Dart=true;Java=false etc.
Or maybe we could implement "contains" filter?