The Worrying Side of Stack Overflow: A Personal Analysis With BigQuery's Public Data

Senior Data Engineer by profession. World explorer by curiosity. Music Producer by aspiration. Lazy potato by heart.
Search for a command to run...

Senior Data Engineer by profession. World explorer by curiosity. Music Producer by aspiration. Lazy potato by heart.
No comments yet. Be the first to comment.
I consider myself quite lazy, and I recommend every programmer embrace laziness as well. Not in the sense of staying in bed all day and binge-watching a full season of Frieren (though that's exactly what I did last weekend...), but in terms of follow...

Working with third-party or legacy databases can be a real headache. We've all been there - you're stuck dealing with a database you didn't design, and every change feels like a nightmare. Django's inspectdb helps create models from an existing schem...

Motivation In the constantly evolving landscape of software development, the tools and libraries we choose play a crucial role in the success and reliability of our projects. When it comes to selecting libraries as dependencies for software projects,...

Reason for research: Unfamous Lines of Code (LoC) LoC is one of the metrics that is used to measure programming productivity. One of the obvious disadvantages of this metric is a comparison of lines of code among developers using different programmin...

Stack Overflow is an invaluable resource for developers worldwide. It’s the go-to place to find answers, share knowledge, and contribute to the collective wisdom of the programming community. But, like any platform, it has its strengths and weaknesses.
My relationship with answering questions on Stack Overflow began unexpectedly.
I stumbled upon this question when I tried to find an answer to a problem I had.
The thing was, it had no answers...
Once I cracked the problem, I felt an urge to share my solution. Why? So that anyone who encounters this in the future doesn't have to start from scratch. And there it was, my first contribution to Stack Overflow.
No platform is without its flaws. The biggest recurrent criticism of Stack Overflow is the perceived toxicity within its community. While I've observed certain users who could certainly tone down and be more understanding towards new users, that's not the crux of my concern.
I've noticed an unsettling trend among users, especially those with low reputation (often indicative of newer accounts): a reluctance to upvote or accept answers.

To validate my observations, I dived into some quick data analysis, the results of which can be accessed in this Jupyter Notebook on Kaggle. In analysis, I've looked only into users created after 2019-01-01 who asked questions that had at least one answer.
The findings were intriguing though not surprising:
Users (created since 2019) with a reputation of 11 or below constitute the largest user group.

This group is the second most active in terms of asking questions.

However, they have the lowest average number of upvotes (0.03 upvotes per user) cast per user and the lowest percentage of accepted answers (28% of questions with accepted answers).


This trend is concerning. When answers aren't upvoted or accepted, it undermines the motivation to help. Answering questions, especially from newer users, becomes a gamble: Will my efforts be acknowledged?
While the act of helping should be altruistic, on platforms like Stack Overflow, upvotes, and accepted answers aren't just digital badges; they're affirmations. They convey gratitude, acknowledge effort, and, most importantly, guide other users to trustworthy answers. When these affirmations are missing, it creates an environment of hesitancy and undervaluation.