What is covered, week by week, and which topics each lecture draws on.
Six lectures, spaced across the semester rather than stacked at the front, each one landing just before the studios that need it: a claim, an argument, a piece of Shitao’s own treatise read against the code you’re about to write. Where a studio is where an instrument gets built, a lecture is where you’re told why it’s worth building that way.
The single brushstroke
The opening lecture — why this course starts from one continuous gesture instead of a list of features
Week 1 · 22 February 2027
Gesture has more than a position
Why a timing signal you compute yourself outlasts a hardware signal you merely read
Week 3 · 8 March 2027
Time inside the instrument
Why an instrument with a clock of its own is a different kind of thing than one that only ever reacts
Week 5 · 22 March 2027
One path for every hand
Unifying mouse, touch and keyboard isn't an accessibility add-on — it's what a correctly-built instrument does anyway
Week 7 · 5 April 2027
When failure is the material
Telling a considered failure apart from a bug, and why the difference is a sentence you have to be able to say out loud
Week 9 · 19 April 2027
Showing an instrument to a stranger
What changes when nobody stands next to the work to explain it
Week 11 · 3 May 2027