Have a tricky problem that you think requires a rewrite of your software? Join as a guest on our podcast and we’ll talk you out of it.

What we cover

  • Legacy code: characterization tests around the risky paths, then pieces moved out of the monolith one at a time behind flags
  • Infrastructure scaling: right-sizing AWS so it handles bursts, costs less, and shows you problems before it goes down
  • Containers and CI/CD: Docker and Amazon ECS migrations with pipelines that make deploys uneventful, zero downtime and one-command rollback
  • Database performance: slow Postgres, MySQL and Aurora queries found and fixed with indexing, query rewrites and workload isolation
  • Dead code: deleted only after access logs and traces show it has zero traffic

What the engagement looks like

Week 1: Map the risk

We read the code, the logs and the incident history, then write down where changes are dangerous, what’s actually dead, and which pieces are safest to change first.

Weeks 2–8: Move the first pieces

Tests around the riskiest paths, then the first changes go out behind flags with the old path still live. Infrastructure and database changes land in small steps with a rollback for each.

Hand-off

Your team owns every change. We leave a written plan for what to do next, the tests that protect it, and a runbook for each flag.

Proof

Universal Gem: A legacy Rails portal for an Illinois gaming operator, never rewritten. A connection storm in a vault job was fixed with a concurrency cap instead of a read replica, a page that took over three minutes to load became a paginated summary, and the codebase gained a Dockerized dev environment, a database-change log and unit tests on the finance calculations. Read the case study.

Homeworks (formerly CopilotCRM): Bug count down about 80%, deploys moved to ECS with zero downtime, Aurora and indexing tuned, email deliverability up from 91% to nearly 95%, and no rewrite of the core application. Read the case study.

From Isaac Askew’s work at a payments company: Isaac, who runs YGG, took a legacy PHP portal from zero automated tests to 343, upgraded six services from PHP 7.3 to 8.3 without incident, and deleted 245 dead files only after production traces showed zero traffic. Read the write-up.

Talk it through

A 15-minute call is enough to tell whether this is a good fit. Bring the system you’re worried about.

Book a call How we work & pricing

Prefer email? start@ygg.llc