How do you migrate the last 3% of files that automation can't fully finish?
Treat the long tail differently from the bulk: stamp every file with a machine-readable status of what has and hasn't succeeded, build a tool to rerun just the failing step on just the affected files, then run a tight loop — sample a handful of similar failures, tune the approach, sweep it across the category, repeat for the next failure pattern. LLM output on the hardest files still served as a usable starting point for the small remainder of manual cleanup.
Answered in
How to Migrate Thousands of Legacy Test Files With LLMs, Not RewritesA step-based pipeline, retry loops instead of perfect prompts, and rich context injection turn a year-long manual migration into a six-week automated one.
Read the full analysisOther questions this article answers
More development best practices questions
- What did OpenAI’s Habitat team change?
- Does the reported 12× read improvement mean another team should copy the design?
- Does the Python Typing Survey measure all Python developers?
- Do Python type hints enforce types at runtime?
- What is interactive refactoring in gopls?
- Is interactive refactoring already part of the official LSP standard?
- What does Meta mean by human-on-the-loop software engineering?
- Does Meta's Forum project prove that AI can replace a software team?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the Development Best Practices beat.