The exact tools used to port a massive codebase in days #programming #typescript #dev
A reported weekend Python-to-TypeScript port shows how agent-driven iteration can make once-prohibitive migrations plausible, provided verification is part of the loop.
Mike Krieger describes using an agent workflow to port **a couple hundred thousand lines** from **Python to TypeScript** over **one weekend**, motivated by a better Bun deployment path.
For large migrations, rethink the unit of work: let agents repeatedly port, verify, compare both implementations, and continue through failures. Treat deployment readiness and behavioral parity as explicit acceptance criteria.
Mike Krieger describes using an agent workflow to port **a couple hundred thousand lines** from **Python to TypeScript** over **one weekend**, motivated by a better Bun deployment path. For large migrations, rethink the unit of work: let agents repeatedly port, verify, compare both implementations, and continue through failures. Treat deployment readiness and behavioral parity as explicit acceptance criteria. This is one retrospective account, not a reproducible benchmark. The transcript provides no test coverage, defect rate, staffing detail, workload breakdown, or evidence that the same pace generalizes to other codebases.
This makes a very large, rapid migration seem operationally plausible when agents can iterate against behavioral parity and deployment criteria, but it does not establish that the result was reliable or economical. The candidates narrow the lesson from “migrations take days” to “large migrations may suit goal-level delegation only when tests, comparison, rollout controls, and review make the end state observable.”