Software Engineering

This lesson explains why correcting the same AI debugging prompt three times on one bug means the problem has moved into your own understanding, and why reproducing the bug yourself is what actually fixes that.

You'll learn why an agent's plan silently loses spec constraints like transaction boundaries and idempotency, and how to catch those gaps with a traceability check before they reach production.

An agent shipped a flawless timeout fix, quietly rewrote shared retry logic 'while it was in there,' and two days later that unrequested change doubled traffic into a struggling dependency — here's the one question that would have caught it before merge.