I help your Rails team ship faster.

I get your codebase agent-ready.

Damian speaking into a microphone on stageRuby on Rails

I’m Damian, a senior developer with 15 years in production Rails applications.

I audit your Rails codebase, then fix what slows your team down in six weeks, with AI agents and small pull requests.

Sound familiar?

For Rails teams that care about code quality and want to ship faster.

  1. Friday fear

    Forty-minute CI. Nobody deploys on a Friday.

    A suite you trust, in minutes.

  2. Green by rerun

    CI reruns until it passes. Red means nothing.

    No flaky tests. Red means red.

  3. Upgrade wall

    Abandoned gems, monkey patches, no coverage.

    A staged, tested upgrade path.

  4. Untouchable code

    God models and invisible callback chains.

    Small refactors, covered by tests.

  5. Slower every month

    N+1 queries, missing indexes, a Sidekiq backlog.

    Measured fixes, before and after.

  6. Endless roadmap

    Legacy code makes every feature cost more.

    Features get cheaper again.

Hiring another developer will not remove the bottleneck.

  • A new hire inherits the same friction.

    Same CI, same flaky tests, same upgrade debt. And candidates read your Gemfile too.

  • Coding agents amplify what they find.

    On a clean codebase they multiply your team. On a tangled one they write legacy code faster.

  • The codebase is now the limit.

    A fast, reliable codebase decides how much your team ships, with or without AI. That is the work I take on.

What a cleaned-up pipeline looks like.

The same CI before and after a six-week sprint. Fewer steps, jobs that run in parallel, and no more “Re-run failed jobs” because of a flaky test.

CI Merge pull request #1284 from acme/checkout-fix
Re-run failed jobs Attempt #3
Triggered via push
2 hours ago
Status
Success
Total duration
38m 12s
Artifacts
1

ci.yml on: push

setup2m 41s
lint3m 05s
assets4m 18s
rspec21m 44s3 attempts
system tests6m 24s
CI Merge pull request #1342 from acme/invoice-export
Attempt #1
Triggered via push
2 hours ago
Status
Success
Total duration
6m 40s
Artifacts
1

ci.yml on: push

lint52s
assets1m 10s

Matrix: rspec

8 jobs completed3m 48s

Matrix: system tests

2 jobs completed2m 02s
Pull requests merged per day 3

Six weeks, one bar per working day

Re-runs for flaky tests 27
Re-run failed jobs

27 in the last 30 daysNone in the last 30 days

Sample project, for illustration. Your numbers come from your own audit.

Pull requests your team will enjoy reviewing.

So every pull request ships with a one-page visual report. Your reviewer understands the change in minutes.

Pull request report Ready to review

Stop booting Rails for 1,400 unit specs

Specs under spec/lib and spec/services no longer load rails_helper. Nothing changes in application code.

Unit suite
6m 48s1m 12s
Files touched
38
Behavior changes
none
Risk level
LowTest setup only, reverts cleanly, no migration.
Deleted files
spec/support/preload_rails.rbspec/support/legacy_db_cleaner.rb
  • Full suite green, three runs
  • Coverage unchanged at 91%
  • Needs a reviewer eye on spec/support/time_helpers.rb
“We still have to review all of this.”
Each pull request carries a report. What changed, why, what it does not touch, and the before-and-after numbers when they exist.
“We cannot absorb seventy PRs in a week.”
Small, single-purpose pull requests, in batches sized to your team’s week. If review falls behind, I slow down.
“How do we follow what is going on?”
A shared plan, updated every day. In scope, in progress, in review, done. Your technical lead sees the same board I do.

How it goes.

  1. 1A free 15-minute call

    What your team keeps postponing, and whether an audit makes sense.

  2. 2Read access

    Enough to start. Tools and access rules are agreed first.

  3. 3The audit

    I read the code and your workflow, measure, and write the plan.

  4. 4Priorities, with your team

    We walk through the findings and choose what comes first.

  5. 5Shared conventions

    Agreed with your developers. Every pull request follows them.

  6. 6Pull requests start

    One living document tracks the plan and every pull request, from created to merged.

Whatever your Gemfile looks like, I have probably met it.

  • Framework Rails 5+ · Ruby 2.7+
  • Databases PostgreSQL · MySQL · MongoDB · Redis · Elasticsearch
  • Background jobs Sidekiq · Solid Queue · Good Job · Delayed Job · Resque
  • Testing RSpec · Minitest · FactoryBot · Fixtures · Custom
  • Authentication Devise · OmniAuth · Custom
  • Authorization Pundit · CanCan · Custom
  • Frontend JavaScript Hotwire · Turbo · Stimulus · Vue.js · React · Custom JS
  • Frontend CSS Tailwind · Bootstrap · Material Design · Custom CSS
  • Asset pipelines Importmap · Sprockets · Propshaft · Webpacker
  • APIs GraphQL · REST · RPC
  • Deployment Docker · Kubernetes · Kamal · Heroku · Render · AWS · Azure · GCP · Bare metal
  • CI / CD GitHub Actions · GitLab · Others
  • File uploads Active Storage · CarrierWave · Shrine · S3 · Custom
  • Admin panels ActiveAdmin · Administrate · RailsAdmin · Custom
  • Monitoring Sentry · Bugsnag · Datadog · New Relic · Others

15 years inside production Rails applications.

I shipped my first website in 2006, made my first open source contribution in 2010, and have worked mostly on Ruby on Rails since 2011.

  1. 2026 A contribution merged into RailsPull request #56967 in the Rails repository
  2. 2023–2026 kelvin, a large Rails monolithGrew a new Rails application into a 130-table monolith serving enterprise customers in a regulated industry
  3. 2017–now Localtower, a Rails Engine for database migrationsBuilt to support applications from Rails 5.2 to Rails 8 and featured in Ruby Weekly
  4. 2017–2019 Ruby and Sidekiq at scalePostgreSQL, Sidekiq Enterprise, Kubernetes, APIs and a CI pipeline reduced from 45 to 4 minutes
  5. 2017 Rails due diligence for the Loco2 acquisitionA quality audit of a large, business-critical Rails application, read and assessed in days
  6. 2013–2016 Geeksters, one of the first Ruby dev shops in MoroccoWe built The House Of Geeks in Agadir, where I taught Ruby on Rails and grew the team from 2 to 15 full-stack developers
  7. 2011–2020 HashtagBattle, my first Rails product in productionScaled to thousands of users per minute and maintained for eight years

Security fixes in hours, not weeks.

The web gets more dangerous every month. When a vulnerability lands, you need to patch your code and deploy it fast. I get your team there.

  • Patch in hours.

    Up-to-date gems, so a security release is a small bump, not a migration.

  • Deploy the same day.

    A fast CI and a safe deploy path take a fix to production in hours.

  • Know when it matters.

    Advisories on your Gemfile, triaged and fixed in small pull requests.

A few practical questions.

How much time will our team need?
A technical contact, a kickoff to share context, and regular review time. We size the review load to your team before starting.
Can you help while we are recruiting?
Yes. The sprint clears an agreed backlog while hiring continues, so your next developer starts on a cleaner codebase.
Do we have to buy the sprint after the audit?
No. The audit is a standalone engagement with its own deliverable. Many teams use the plan internally.
Do you push to production?
No. Every change is a dedicated branch and pull request, merged only when someone on your team approves it.
What if our priorities change during the sprint?
We review the plan every week. Scope is fixed, but we can swap a priority if something more valuable appears.
Do you use AI coding tools?
Yes, extensively and openly. Standard tools only, inside the access rules we agree on. I review every change before your team sees it.
How do you handle access and confidentiality?
Read access for the audit, a dedicated account with the permissions you choose for the sprint, and an NDA when you need one.
Can we do everything remotely?
Yes. GitHub, Slack and video calls. I am based in Madrid and available on US working hours too.

Enterprise AI tools only. Zero retention of your code.

Every tool runs on a paid company plan, under the enterprise data policies of Anthropic, OpenAI and Cursor. No retention of your data or your code, and no training on it.

  • Claude CodeEnterprise plan
  • CodexEnterprise plan
  • CursorBusiness plan

Two ways to start.

Rails Codebase Audit.

Know what to fix first.

$1,200USD, fixed fee

You receive

  • Your main sources of friction, with real examples.
  • A prioritized plan, with what comes first and why.
  • Baseline measurements of CI, tests and performance.
  • A six-week sprint scope and the time it needs from your team.
  • A walkthrough with your technical lead.

Audit + Cleanup Sprint.

Six weeks to act on the priorities.

$24,500USD, fixed fee, audit included

Scope and success criteria agreed upfront. Coding agents run in parallel, and I review every change first.

Typical priorities

  • CI speed: boot time, slow steps, parallel workers.
  • Test reliability: flaky tests removed for good.
  • Upgrades: Ruby, Rails and gems, staged and tested.
  • Refactoring: the models and callbacks that slow you down.
  • Performance: queries and jobs, measured before and after.
  • If the audit finds nothing worth a sprint, I tell you. You keep the plan either way.
  • Yes, a start within three weeks is possible.

What would you like your Rails team to stop losing time on?

Book a free 15-minute call
  • The call: we get to know each other, your team’s constraints, your app’s challenges and its most sensitive areas.
  • Bring one or two people from your team. Those in the code every day help us cover much more.
  • Emails get a reply within 24 hours.
  • Fluent in English, French and Spanish.
Damian seated on stage, speaking into a microphone

An email can be this short.

Gmail opens a new email to me with this subject. You write the rest.

New message
To Damian Le Nouaille
Speeding up our Rails team
Hi Damian, I think our team needs to speed up on our Ruby on Rails development. We would like to talk with you about how to improve our application and our CI, and ship faster with agents. Could we book a call next week? Best, Sam