Debugging Code You Did Not Write

Part of the Vibe Coding: Advanced Engineering course

Debugging your own code starts with an advantage: you remember what you were trying to do. Debugging generated code removes that advantage completely, and adds a specific trap. The author is still available, infinitely patient, and will produce a confident diagnosis for any bug you describe, whether or not it has any idea what is wrong.

Open flaky.py and click play. It hunts for inputs where split_amount violates its own invariant. Run it with a fixed seed so we are looking at the same thing ...