Scrap legacy code and rebuild in Python for AI-assisted development
Peter discovered this after frustration with his portfolio companies: they'd try to have AI fix their Java codebase and it would struggle, but simply saying 'scrap it, rebuild in Python' resulted in a finished product in an hour. He now generates massive volumes of code using Kimmy K2 for speed, then routes the output through GPT-5.2 to proofread for vulnerabilities because the generated code 'just flat out works' and is too voluminous for human review. He learned the hard way about spyware risks from Chinese models after Alex warned him that open-weight models can inject vulnerable code when prompted with certain topics. The protocol thus has two phases: (1) rebuild in Python with a fast model for volume, (2) proofread with a trusted safer model.
LLMs are trained on massive internet corpora where Python dominates; the token prediction quality is higher. Java and especially C have less representation, so the model lacks the pattern depth to reliably generate correct code.
Peter: 'You come back an hour later and it's done... I'll easily crack 20 or 30k this month, but I'll also generate more code this month than my entire life up to this date. Um, so it's a bargain at 20k.'
If you just say no, scrap it. Rebuild it entirely from scratch in Python. You come back an hour later and it's done.

