Nearly 1,800 Rails developers across 80 countries reported on tools, workflows, teams, learning, and AI. Respondents skew toward experienced practitioners (only 7% are new to Rails) and formal education is common: 44% learned via a CS degree and 41% self-taught. Most apps remain monolithic (81%), with 47% serving mainly public consumers and 42% a mix of public and internal users. Team sizes are varied, half report similar headcount over the last two years, 30% grew, 19% shrunk. Common pain points for onboarding and maintenance include realistic local test data and authentication setup. Conferences and community engagement are modest: 28% attended a Rails/Ruby conference in the last year, and Rails World is the top event people plan to attend.
Tooling and upgrade behavior show clear patterns: rbenv (39%) and mise (38%) lead Ruby version management, with Docker and asdf also common. Most projects are reluctant to upgrade Ruby/Rails because of time, budget, and priority constraints rather than tooling gaps; AI helps automate mechanical upgrade tasks but doesn’t replace roadmap decisions. Monoliths dominate deployment choices; Solid Queue - now included by default - has meaningful uptake. Learning still values guides and hands-on materials, bootcamps are present (Le Wagon 16%), and maintainers emphasize adapting documentation and community outreach for an increasingly AI-assisted development landscape.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.