Java 8 to 17, Python and Node.js runtime bumps, AWS SDK v1 to v2, framework upgrades: the same change repeated across hundreds of repositories. AWS Transform custom (December 2025) runs these as defined transformations from one CLI command; coding agents such as Claude Code and Codex handle one-off and judgment-heavy changes. When to use which, and how to keep both safe.
Most technical debt is not one hard problem. It is the same easy problem in two hundred places: every service on Java 8, every Lambda on a deprecated Python, every repository on the AWS SDK for Java v1. That shape suits automation better than heroics.
Book a free 30-minute call. You'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.
Inventory: list repositories with the old runtime, SDK or framework version, and their owners.
Run the transformation on a pilot set of five to ten representative repositories and review every diff.
Feed corrections back into the transformation definition until the pilot diffs need no edits.
Roll out in waves through normal pull requests, with tests and owner review. The tool opens the change; people approve it.
Hand the repositories that fail to a developer with a coding agent, and record why they failed so the next wave improves.
No transformation merges without passing tests. Repositories without tests get a smoke test first.
Run agents with least-privilege credentials and no production access. Code changes go through the same review as human ones.
Measure the result: repositories upgraded, pull requests merged without edits, time per repository. That is how you know the definition is good enough to run unattended.
Once a month: what changed in tech that month and what it means for you, from cloud and AI to security and the tools you build with. Every item links to its source. No sales pitch, unsubscribe in one click.
Book a free 30-minute call about it. Bring your setup and your bill; you'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.
Or keep reading
Git Worktrees, Now That Your Coding Agent Uses Them: How They Work and What Breaks
Claude Code runs parallel sessions and subagents in git worktrees: separate checkouts on separate branches, sharing one repository. What a worktree shares and doesn't, the one-branch rule, where Claude Code puts them and when it cleans them up, and the things that still collide: dependencies, ports, local databases and .env files.
Read
What Ten Enterprise Modernizations Have in Common: Home Depot, Lowe's, Capital One, Netflix, Amazon and More
Ten public modernization stories, side by side: where each started, how long it took, how much was rebuilt rather than moved, and what changed. Six patterns repeat in almost all of them, and each one applies to a company far smaller than these.
Read
As of October 25, 2026. Provided as is, for general information, and accurate to the best of our knowledge on the date shown. Not legal, compliance, tax, financial or other professional advice. Prices, limits and vendor services change; check current vendor documentation before relying on anything here. Terms of use.