Modules

A module is the full written version of a lecture topic. The deck is the fast version you see in class; the module is the one you read when you want more than the deck, or when you missed the hour.

Reading a module is optional unless the schedule says otherwise. The schedule is also where you find out when each topic is taught, and it links that week's slides and reading directly.

Modules go up as they are written, in the order the course teaches them, so this list grows through the term.

Published so far

SE and What AI Changes · slides

What is left for a software engineer when the agent can write the code. Places a task on the delegation boundary, and sizes an unfamiliar problem in twenty minutes well enough to defend it against the agent's version.

The AI-Augmented Team · slides

Set your team up so the work is legible to every member, including the one that forgets everything between sessions. Put what governs the project in the repository, and make every unit of work traceable from requirement to merged code.

Professionalism · slides

Run a team problem the way you run a defect: observe the behavior, analyze its impact, investigate before you assume, and agree on a fix with an owner and a date. The standards themselves are on the Professionalism handbook.

Requirements as the Contract · slides

Find out what your client actually needs, and write it down so your team and your agent build the same thing. Running a first client meeting, business objectives and success metrics, the project glossary, and the scope line you will need in October. The nine kinds of requirement are in Requirement Types. Week 4 half still being written.

Requirements Traceability

Keep a use case honest end to end, forward (is it built and tested?) and backward (why does this code exist?), and see why that matters more, not less, when an AI writes the code. Still being written.