Adding a course to DSA is a partnership today. You bring your slides, recordings, textbook and assignments. I run the pipeline that turns them into a course: a knowledge base, a lecture plan, learning goals, exercises, mastery questions and decks. You review what comes back, and then you run your class in it yourself.
CSS 430 Operating Systems is the worked example, because it is the first course to go through the runbook since 342 and 343. It took nine days from the registry entry to generated decks, goals and openers, and it is still not in front of students. The talk says what is left, what the review caught, and the question people ask first: whose voice the tutor speaks in. Today it is mine. The last part is what self-serve onboarding would take.
What is in it
- The partnership. What a course is inside DSA, and who brings, builds and reviews what.
- What you hand over. The sources the pipeline reads, and how exams, answer keys and student work stay out.
- How it gets built. Three lanes, ten steps, and roughly how long each takes.
- CSS 430. What went in, what came back, what the rubric read caught, what C instead of C++ changes, and where it is now.
- Review and voice. What you look at, how fixes happen, and the honest answer on the voice.
- Running your class. Rosters, exams, class materials, graded rounds, the dashboard, who pays.
- Vision and roadmap. Why it is not self-serve yet, and what would have to be built.
CSS 430's numbers are content and test counts from the repository. No students have used it yet, and no production data is in the deck.
Presenting it yourself
The slides are plain HTML with Reveal.js sitting next to them, so the folder works with no network. Arrow keys or space to advance, S for the speaker window (a timer and the next slide; these decks carry no notes), F for full screen, O for the slide overview, B to blank the screen, ? for help. Feel free to borrow any of it.