Update a Gamma course deck from recent writing with Codex
I asked Codex to compare the two decks for my Maven course with the newsletters and articles we had written since the last version. It pulled the latest content repository, read the newer material, and opened the decks in Gamma using Chrome. I pointed it toward a few ideas I wanted to develop: software factories, the changing role of engineers, and giving agents useful company context.
Codex turned those sources into nine comments attached to specific slides. I reviewed the suggestions, approved posting them, and it added the comments in Gamma and checked that they were there. I could work through an edit list inside the deck instead of keeping articles open while hunting for the right place to use each idea.
The useful part was asking for the connection between the writing and the teaching material. “Make this more current” is a vague request. Giving the agent the actual newer work, the current slides, and a few themes produced changes I could evaluate one by one.
# Refresh a course deck
Adapted from my workflow; this is not the original transcript.
Compare the course deck I provide with the newer articles, newsletters, and other source material I identify. Read the sources and inspect the actual slides.
Find specific places where a newer example, clearer explanation, or changed assumption would improve the course. For each suggestion, give the slide title, the proposed change, the source link, and a short explanation of why it belongs there. Do not force every new article into the deck.
Draft the suggestions as concise slide comments. Show me the proposed comments before posting them. After I approve them, add each comment to its corresponding slide in the presentation app and check that it appears in the right place.