Shipping in public is useful when the public record makes the work clearer. It gets less useful when the work starts bending itself around the performance.
The version I want is simpler: build real things, narrate the decisions, and leave behind enough context that someone else can learn from the path without needing to watch every minute live.
The channel split
Twitch is for the work while it is still moving. YouTube is for the cleaned-up trail. Articles are for ideas that need structure, references, or code snippets. GitHub is for the source when there is source worth sharing.
Each format should earn its place. If a topic only needs a short update, it should stay a short update. If it needs a real explanation, it should become a video or article.
The useful part
The useful part is usually not the final answer. It is the constraint that changed the design, the test that failed in an interesting way, the deployment detail that forced a simpler architecture, or the product question that made a clever implementation irrelevant.
That is the kind of public work I want this site to point at.