About

10+ years shipping production software. I take ownership of your codebase and fix what's actually broken.

Paul

I help non-technical founders turn AI-built MVPs into stable, production-ready software.

Based in Romania. Working remote. 10+ years of Rails in production.

What I do

Most AI-generated codebases work until they hit production reality: concurrent users, unexpected input, a deploy that breaks the database migration, or a background job that silently fails. The code isn't wrong, exactly — it just wasn't built by someone who has run software under real load, real users, and real stakes.

That's where I come in. I read your codebase the way a senior engineer reads it: not to judge it, but to understand it and fix what's actually causing pain. Then I ship those fixes to production and leave guardrails so the next change doesn't break everything.

Background

Ruby on Rails (primary)

10+ years building, maintaining, and scaling Rails apps — APIs, background jobs, database performance, and full-stack web. This is the stack I know deeply.

Full-stack capability

JavaScript (React, React Native, Expo), Python, and Elixir. I can own the full technical surface area — backend, frontend, and mobile.

Infrastructure and DevOps

AWS (EC2, RDS, S3, and more), CI/CD pipelines, deployment strategies, monitoring, and alerting. I make deploys boring — the good kind of boring.

Product engineering

Third-party integrations, mobile apps (React Native + Expo), performance optimization, security basics, and technical due diligence. I've been the solo engineer, the lead, and the outsider brought in to fix things.

How I work

  • Understand before touching. I read the whole system before I change anything. Fixes without understanding just move the problem.
  • Root causes, not symptoms. Patching the error message doesn't fix what's causing the error. I find and fix the actual problem.
  • Ship, don't recommend. My deliverable is fixed code in production — not a PDF of suggestions. If I diagnose a problem, I fix it.
  • Leave it better than I found it. Tests for the risky paths, monitoring for the failure modes, and a clear plan for what comes next.

Ready to talk about your codebase?

Book a free 15-min fit call. You describe the pain. I'll tell you quickly if this is the right engagement.