r/rubyonrails

▲ 7 r/rubyonrails+1 crossposts

Why I stopped aiming for 100% test coverage as a solo developer (and a book announcement)

Hey everyone,

I’ll be honest: For the longest time, I hated testing.

In the early stages of my career, testing felt like a "corporate tax." I was following the standard advice: test every method, aim for 100% coverage, and use complex factories. As a solo developer, this killed my momentum. I spent more time fixing broken tests than shipping features.

Everything changed when I moved back to Minitest and Fixtures. I realized that the testing strategies used by teams of 50 people are actually harmful to a solo indie hacker.

I’ve spent the last year refining a philosophy I call "Wise Testing." It’s about getting 90% confidence with only 10% of the effort - focusing heavily on System Tests for the "Golden Path" and only using unit tests for complex business logic (POROs).

I decided to put all these patterns, workflows, and speed optimizations into a book: Wise Testing: The Solo Founder's Guide to Rails Quality.

The goal isn't to reach a coverage metric; it's to build a "safety net" that allows you to refactor and ship on a Friday afternoon without a panic attack.

I’m looking for some feedback from the community.
If you are a solo dev or indie hacker struggling with your testing suite, I’d love to send over some review copies in exchange for some honest feedback or a testimonial if you find it helpful.

If you’re interested in a review copy, please send me a DM or comment below!

You can also read the "manifesto" post that inspired the book here: https://norvilis.com/wise-testing-what-to-test-and-ignore-as-a-solo-rails-developer/

reddit.com
u/zilton7000 — 5 days ago
▲ 17 r/rubyonrails+1 crossposts

We're putting the final touches on the 9th Rails Developer Survey since 2009 — what question should we be asking?

Before I hit the button to open submissions on this year's Rails Developer Survey, it felt like I should do a quick pulse check first. Yes, a survey before a survey. How meta.

The team at Planet Argon has been running this biennial survey since 2009, and we have several technical topics already lined up. But before we lock things in, I want to make sure we're not overlooking something important. The goal is to surface meaningful insights for the teams responsible for Ruby on Rails apps as we head into 2027 and beyond.

What are the technical challenges, decisions, or trends your team is working through right now? Is there a topic you think the Rails community needs better data on?

Drop your suggestions below. We want this survey to actually be useful to you. 👇

reddit.com
u/robbyrussell — 5 days ago

long-term/part-time software developer ($30-$60/hr)

Requirements:

- English C2

- 1-3yrs software development experience

- Stable internet connection

Bonus Skills:

- EST time work + Quickly reply during work time

- Experience with modern software frameworks- AI-related skills

Payment:

- Paid via PayPal or cryptocurrency

- Weekly payments available depending on the situation

When you message me, just include your country and your English.

reddit.com
u/Hero_Telephone3070 — 3 days ago

Docsmith: Gem to version your document.

Shipped my first Ruby gem this weekend Docsmith: https://rubygems.org/gems/docsmith

It adds snapshot versioning, format-aware diffs, and inline comments to any ActiveRecord model. Zero system dependencies.

But here's the honest story of how it got built.

My first design had branching, merging, conflict resolution — the works. Looked impressive on paper. Turned out I was building Git for documents when all

anyone needs is "save this version, show me what changed, let me leave a note." I stripped all of it out and shipped what actually mattered.

The other honest thing: I built this with Claude Code using the superpowers plugin. Vibe-coding with human intervention. I planned it, tons of tweaks, made architecture decisions,

and course-corrected when things got too complex. The AI was a collaborator, not an autocomplete. Two weekends, 210 passing tests, published to RubyGems.

If you're curious about the planning and implementation process — including the over-engineered version that didn't make it — it's all in the repo under

docs/superpowers.

Rails devs: gem install docsmith. Feedback welcome.

GitHub: https://github.com/swastik009/docsmith

reddit.com
u/Sagarmatha007 — 8 days ago

I built a CLI that analyzes Rails apps and gives a health score

I’ve been working on a small gem called RailsForge, and I recently cut it down to something much more focused.

The idea is simple:

railsforge doctor

It scans a Rails app and outputs a health report with:

  • severity-ranked issues (critical → info)
  • file + line references
  • actionable suggestions
  • a score from 0–100

Example output looks like:

Score: 72/100

Critical
app/models/user.rb:42 — Raw SQL query detected
  → Use parameterized ActiveRecord queries

High
app/controllers/posts_controller.rb:88 — N+1 query detected
  → Use includes(:comments)

It also has a JSON mode so you can use it in CI:

railsforge doctor --format=json

And a simple diff command to catch new issues in PRs:

railsforge diff baseline.json current.json

Repo: https://github.com/mfifth/RailsForge

Would appreciate any honest feedback, especially from people maintaining larger or older Rails apps.

u/zZaphon — 10 days ago

MySQLGenius v0.1.0 - PgHero-style dashboard for MySQL/MariaDB

Built a MySQL performance dashboard for Rails because nothing like PgHero existed for MySQL.

Core Features

  • Visual query builder with type-aware filters
  • Safe SQL execution (read-only, blocked tables, column masking, timeouts)
  • Table sizes, duplicate indexes, unused indexes, query stats
  • Server dashboard (connections, InnoDB buffer pool, query activity)
  • Slow query monitoring via Redis

Optional AI Features (any OpenAI-compatible API)

  • Natural language to SQL
  • EXPLAIN to index recommendations
  • Schema review for anti-patterns
  • Migration risk assessment

Setup

gem "mysql_genius"
mount MysqlGenius::Engine, at: "/mysql_genius"

Rails 5.2+, Ruby 2.6+, MariaDB auto-detected.

GitHub: https://github.com/antarr/mysql_genius

u/Bitter_Detective_416 — 12 days ago

Let's get serious when tracking gems

Proudly announcing that Gemtracker is now version 1.1.4

This is a major upgrade over the previous version, 1.0.5, as it includes most of the requested features and more:

  • Gem HealthCheck to make sure that gems that are not maintained do not turn into tech debt or vulnerabilites
  • Export in JSON, CSV and text format to share with compliance officers or anyone who needit.
  • Export that can be used in an CI or AI workflow
  • Improved speed and UI
  • Of course we squashed some bugs

Thank your to all of you who commented on our last post and suggested features, use cases and more. If you have a few minutes dropping a star or comment on GitHub will help us better serve the community

https://github.com/spaquet/gemtracker

Happy Coding!

u/stpaquet — 13 days ago