A good development stream is not just someone typing while chat watches. The typing is the least durable part.
What matters is exposing the judgment around the typing: why this change is small enough, why this abstraction is not ready yet, why a boring deployment choice is better than an exciting one, or why the first implementation should be thrown away.
Keep the work real
I want the stream to stay connected to actual projects. That means working on Storyverse, Fanstacks, open source, site improvements, tooling, and the kind of infrastructure details that usually disappear from polished videos.
Keep the context portable
Not everyone can make a live session. The job after a stream is to pull out the durable pieces: a commit, a clip, a write-up, a test case, or a video that makes the decision easy to revisit later.