AI Coding Tools Usage

Disclaimer

This isn't a formal survey, just a collection of insights from a Reddit discussion I started. The percentages and numbers throughout are rough approximations based on reading through comments, not scientific measurements. Think of this as organized anecdotes with some fun numbers thrown in, not peer-reviewed research. Take it all with a grain of salt!

Key Question: How Are Rails developers using Claude, ChatGPT, Copilot, or similar tools in daily work?

---

Summary of Findings

Overall Sentiment

• Strongly Positive: ~60% of respondents report significant productivity gains

• Cautiously Positive: ~30% use AI selectively for specific tasks

• Skeptical/Minimal Use: ~10% prefer traditional coding

Most Popular Tools

1. Claude Code - Most frequently mentioned, praised for Rails-specific work

2. GitHub Copilot - Popular for code completion and suggestions

3. Cursor - Used by some, though seen as "just a wrapper around Claude"

4. ChatGPT - Mainly for documentation and brainstorming

---

Key Themes & Insights

1. Dramatic Productivity Increases

Common Use Cases:

• Writing tests (most frequently cited)

• Generating boilerplate code

• Creating scaffold templates

• Writing views and basic CRUD operations

• Commit message generation

2. Role Transformation: From Coder to Architect

Emerging Pattern:

• Developers shifting from writing code to writing specifications

• AI positioned as "pilot" while developer is "navigator"

• Focus on reviewing AI-generated code rather than writing from scratch

3. The Importance of Context

Critical Success Factor: Providing proper context through:

• CLAUDE.md files explaining architecture

• Detailed context files (concurrency.md, etc.)

• Comprehensive instruction sets

• Custom rules files

• MCP (Model Context Protocol) integrations

4. Common Limitations & Frustrations

Where AI Falls Short:

• New/emerging Rails features (e.g., Turbo when it was new)

• Complex business logic

• Novel solutions requiring creativity

• Maintaining code quality and conventions

• Security vulnerabilities

Challenges:

• Code that's difficult to change and maintain

• "Over zealous" refactoring

• Sometimes faster to do it yourself

• Occasional "nonsense" for exotic solutions

5. Best Practices Emerging

Successful Workflows:

1. Iterative Approach: Break features into small phases

2. Test-Driven Development: Have AI write tests alongside code

3. Multiple Context Sources:

   • Use web browsing for documentation

   • Connect to bug tracking (BugSnap)

   • Integrate with GitHub for PRs

   • Link to ticketing systems

4. Rigorous Review: Never skip code review step

5. Separation of Concerns: Use web Claude for architecture, Claude Code for implementation

6. Specific Strengths by Task

---

Typical Workflows Described

Workflow 1: Solo Developer (Full AI Integration)

1. Receive high-level requirements

2. Discuss architecture with Claude web version

3. Create detailed requirements and implementation plan

4. Use Claude Code with CLAUDE.md instructions

5. Implement in phases with TDD

6. Review, test, and refine

7. Deploy and monitor

Workflow 2: Pair Programming Model

• AI as "pilot" (writes code)

• Developer as "navigator" (guides direction)

• Frequent reviews to maintain quality

• Break features into manageable chunks

Workflow 3: Selective Enhancement

• Use AI primarily as "glorified intellisense"

• Manual coding for complex logic

• AI for documentation summaries

• AI for testing edge cases

Workflow 4: Context-Heavy Approach

• Filesystem MCP for codebase access

• Ask specific questions about features

• Copy/paste with personal modifications

• Treat AI as colleague/pair programmer

---

Tools & Technologies Mentioned

IDEs

• VSCode (most common)

• RubyMine

• Cursor

AI Tools

• Claude Code (most praised)

• Claude Web (for planning)

• GitHub Copilot

• ChatGPT

Helper Tools/MCPs

• DeepWiki MCP (for gem documentation)

• ast-grep (pattern searching)

• Tidewave MCP (dev environment integration, $10/mo)

• BugSnap integration

• GitHub CLI integration

---

Notable Concerns & Pushback

Junior Developer Impact

Quote:

"I would not want to be breaking into software development today but if I were trying I would be learning how to use AI and reviewing the code it produces rigorously."

Team Dynamics

Concerning trend:

"It's a bit sad that each member of my team is now a one man team with AI assistants. We don't talk to each other much about the job anymore"

Skill Degradation Risk

• Some developers intentionally write code manually "to keep myself in shape"

• Concerns about losing deep understanding

Measurement Challenges

• Difficult to objectively measure productivity improvements

• Skepticism about actual performance gains for business logic

---

Recommendations for Rails Developers

1. Start with High-Context Tasks

• Test generation

• Scaffold customization

• Boilerplate reduction

2. Invest in Setup

• Create comprehensive CLAUDE.md files

• Document your conventions and anti-patterns

• Set up MCP integrations where relevant

3. Maintain Critical Thinking

• Always review generated code

• Understand foundational coding principles

• Don't blindly accept refactoring suggestions

4. Use Hybrid Approach

• AI for tedious/repetitive work

• Manual coding for novel/complex features

• AI for brainstorming and documentation

5. Stay Current

• AI tools are improving rapidly

• What didn't work 6 months ago may work now

• Keep experimenting with workflows

---

Conclusion

The Rails community has largely embraced AI coding assistants, particularly Claude Code, as a productivity multiplier. The most successful developers use AI as a sophisticated tool that handles repetitive tasks while they focus on architecture, requirements clarity, and code review.

Key Success Factors:

• Strong foundational knowledge to review AI output

• Detailed context files and instructions

• Iterative, phase-based development

• Rigorous testing and review processes

The Future: AI is becoming standard in the Rails toolbox, but human expertise remains essential for guidance, quality control, and complex problem-solving. The role is evolving from "coder" to "architect + reviewer," but deep technical knowledge is more important than ever.