Skip to content

A straight answer about what is wrong with your Rails app

A written review with a prioritised plan, when you need a straight answer about what is wrong.

When you need one

  • Pages are slow and nobody can explain why.
  • The team has stopped shipping and no one can point at the reason.
  • Someone is asking a due-diligence question about the codebase.
  • Someone is proposing a rewrite.

What you get

A document you keep, and a call to walk through it. The document contains:

  • The findings, ranked by what they cost you and what they risk.
  • The fixes worth doing.
  • The ones that are not worth doing, and why.
  • An estimate for each.

What gets looked at

  • The data model and the queries it produces.
  • Background jobs: what runs, what retries, and what fails quietly.
  • The request cycle, and what sits inside it that should not.
  • The test suite: what it covers, and what it only appears to cover.
  • The deploy path.
  • The parts of the code the team avoids.

What an audit turned into

eLocker

A product with scalability problems and a team that needed to grow, at the same time.

A team and a product set up to continue without me, across three years of engagement.

Read the eLocker case study →

Konstantin is an exceptional RoR Consultant/Dev who deserves high praise for his remarkable contributions to our team in really tough situations. His profound expertise in his guidance for designing complex software systems has been a driving force behind the successful implementation of several critical projects.

Billy W. — Operations Director, elocker.com5/5

I'm extremely impressed with Konstantin's depth of knowledge on Ruby and software development in general. He's extremely sharp with software planning and very well organized. I did an initial consultation but plan to bring him in the loop to assist with back-end optimization and project management in the near future. Highly recommended!

Joel L. — Founder, Lately.com5/5

Tell me what you cannot explain

The symptom you are seeing, the Rails and Ruby versions, and roughly how big the team and the codebase are. I reply with what the review would cover.

Full overlap with European business hours, and 9am–6pm US Eastern.

43 clients, 21,500+ hours, 100% Job Success — the reviews are on Upwork.