Skip to content

Learning tracks · Track 5 of 7

AI learning track: Developers working with AI coding agents

For developers who hand real work to coding agents and need to trust what comes back.

Start with step 1: How do you give an AI assistant a useful brief?

After this track: You can brief a coding agent, define the checks it must pass and review its work without reading every line.

  • 10 steps
  • 16 min reading
  • 3 episodes, 2 hr 44 min

The path

Follow these 10 steps in order, or return to the one you need for your current work. Reading times are estimates; listening times cover the full episode.

  1. Step 1: Explainer About 3 min reading

    How do you give an AI assistant a useful brief?

    Start with the brief: a clear outcome, sources and boundaries make every later check easier to write.

  4. Step 4: Explainer About 3 min reading

    Who reviews the code when AI writes most of it?

    Use a five-step review checklist that ties tests and independent findings to the commit you merge.

  5. Step 5: External article

    My Robot Army: How I review AI code

    See one full loop in practice: cheap checks first, a reviewer from another model family and evidence behind every finding.

  6. Step 6: Glossary About 1 min reading

    Reward Hacking

    Recognize the case where the only way to green is gaming the tests, so you know what your backstops are for.

  8. Step 8: Explainer About 1 min reading

    Can AI modernize legacy code and old applications?

    Apply the same verify-the-logic discipline when agents read, explain and translate old code.

  11. Take it into your work. You can brief a coding agent, define the checks it must pass and review its work without reading every line.

Choose another track or continue through the five-level pathway.