🤖 AI Summary
Prior research lacks systematic empirical analysis of the real difficulties faced by Ruby developers. Method: Integrating over 498,000 Stack Overflow questions with 154 developer surveys, this study employs BERTopic-based topic modeling, manual coding, and mixed-method validation to construct a taxonomy of Ruby development challenges—comprising six high-level categories and 35 fine-grained topics. Contribution/Results: It reveals, for the first time, a systematic misalignment between declining Stack Overflow activity and developers’ subjective difficulty perceptions. Web development emerges as the most prevalent domain, while Gem configuration and security/quality concerns are identified as the most salient challenges—endorsed by over 40% of experienced developers. The study’s core contribution is twofold: (1) advocating a redefinition of objective metrics for assessing developer difficulty, and (2) establishing the first empirically grounded, multi-source evidence framework for Ruby development challenges.
📝 Abstract
Ruby is a widely used open-source programming language, valued for its simplicity, especially in web development. Despite its popularity, with over one million users on GitHub, little is known about the issues faced by Ruby developers. This study aims to investigate the key topics, trends, and difficulties faced by Ruby developers by analyzing over 498,000 Ruby-related questions on Stack Overflow (SO), followed by a survey of 154 Ruby developers. We employed BERTopic modeling and manual analysis to develop a taxonomy of 35 topics, grouped into six main categories. Our findings reveal that Web Application Development is the most commonly discussed category, while Ruby Gem Installation and Configuration Issues emerged as the most challenging topic. Analysis of trends on SO showed a steady decline. A survey of 154 Ruby developers demonstrated that 31.6% of the participants find the Core Ruby Concepts category particularly difficult, while Application Quality and Security is found to be difficult for over 40% of experienced developers. Notably, a comparison between survey responses and SO metrics highlights a misalignment, suggesting that perceived difficulty and objective indicators from SO differ; emphasizing the need for improved metrics to better capture developer challenges. Our study provides insights about the challenges Ruby developers face and strong implications for researchers.