EasyEnv
Vibe Coding: Advanced Engineering
AdvancedLesson 9 of 1240 min · hands-on

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 ...

Want to learn Vibe Coding: Advanced Engineering Debugging Code You Did Not Write in a real environment?

Click below, get a fresh Linux box with Vibe Coding: Advanced Engineering ready to go, and work through Debugging Code You Did Not Write hands-on with an AI tutor that knows your code.

Start this lessonDebugging Code You Did Not Write

What you'll learn

  • Hypothesis-driven debugging instead of guess-and-patch
  • Deterministic reproduction before diagnosis
  • Shrinking to the smallest failing input
  • Bisecting a change set and reading the fix for scope

Read this lesson in your language

All lessons in this course

12 lessons
  1. 1Context Is The Whole Game35 min
  2. 2Pick The Right Brain, Pay The Right Price25 min
  3. 3Spec-Driven Development35 min
  4. 4Build Your Harness35 min
  5. 5Verification Loops: Make It Prove Itself40 min
  6. 6Reading Generated Code Like A Senior40 min
  7. 7Legacy Archaeology40 min
  8. 8Migrations At Scale40 min
  9. 9Debugging Code You Did Not Write40 min
  10. 10The Security Model Of An Agent40 min
  11. 11AI On A Team30 min
  12. 12Judgment: Knowing When Not To35 min

Explore other courses

Debugging Code You Did Not Write - Vibe Coding: Advanced Engineering (English) | Engineering Courses