You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The current analysis in the repository only includes data up to 2020 and the analysis of 2021 and 2022 is currently being updated, while Stack Overflow surveyed in 2023. This creates a gap in the analysis timeline and hinders the ability to provide insights based on the latest data.
Describe the solution you'd like
I would like to address this issue by integrating the dataset for the Stack Overflow 2023 survey into the existing analysis. This involves obtaining the dataset, cleaning it to ensure consistency with previous years' data, merging it with the existing dataset, and updating visualizations to incorporate insights from the 2023 data.
Describe alternatives you've considered
An alternative solution could be to continue the analysis without the 2023 data, but this would result in incomplete insights and potentially misrepresent trends in the Stack Overflow community.
Additional context
The integration of the 2023 dataset will provide a comprehensive analysis spanning from 2018 to 2023, allowing for a more accurate understanding of trends and patterns over time.
What problem is this feature trying to solve?
This feature aims to address the gap in the analysis timeline by incorporating the dataset for the Stack Overflow 2023 survey, ensuring that the analysis reflects the most up-to-date information available.
How do we know when the feature is complete?
The feature will be considered complete when the dataset for the Stack Overflow 2023 survey has been obtained, cleaned, merged with the existing dataset, and visualizations have been updated to incorporate insights from the 2023 data.
Hi @deepti-50 i have assigned this issue to you. I wanted to integrate 2023 dataset.
I know this involves bit of coding and time so assigned the label3 which is 45 points towards leaderboard.
This issue has been automatically closed because it has been inactive for more than 30 days. If you believe this is still relevant, feel free to reopen it or create a new one. Thank you!
Is your feature request related to a problem? Please describe.
The current analysis in the repository only includes data up to 2020 and the analysis of 2021 and 2022 is currently being updated, while Stack Overflow surveyed in 2023. This creates a gap in the analysis timeline and hinders the ability to provide insights based on the latest data.
Describe the solution you'd like
I would like to address this issue by integrating the dataset for the Stack Overflow 2023 survey into the existing analysis. This involves obtaining the dataset, cleaning it to ensure consistency with previous years' data, merging it with the existing dataset, and updating visualizations to incorporate insights from the 2023 data.
Describe alternatives you've considered
An alternative solution could be to continue the analysis without the 2023 data, but this would result in incomplete insights and potentially misrepresent trends in the Stack Overflow community.
Additional context
The integration of the 2023 dataset will provide a comprehensive analysis spanning from 2018 to 2023, allowing for a more accurate understanding of trends and patterns over time.
What problem is this feature trying to solve?
This feature aims to address the gap in the analysis timeline by incorporating the dataset for the Stack Overflow 2023 survey, ensuring that the analysis reflects the most up-to-date information available.
How do we know when the feature is complete?
The feature will be considered complete when the dataset for the Stack Overflow 2023 survey has been obtained, cleaned, merged with the existing dataset, and visualizations have been updated to incorporate insights from the 2023 data.
Data source :- https://survey.stackoverflow.co/
Please assign this task to me.
The text was updated successfully, but these errors were encountered: