v0.12.66: @newsroom.writer: Omnichannel programming

One new article written here from a voice memo.

Omnichannel programming borrows the retail distinction Darrell Rigby put into Harvard Business Review in 2011: multichannel means separate channels, each with its own copy of the work; omnichannel means every channel reads and writes one shared state. For programming that state is git, vaults, briefs and graphs. The worked example is this site's own writing session, counted from its transcript and the repository log: 54 messages in, 10 of them voice memos, and 40 releases, 36 articles and 87 figures out, in three days. It argues that review and custom interfaces are channels too, that the pattern holds for explorers, villagers and town planners at every altitude, that it is already how a new generation of developers and founders works, and names what breaks. Three figures.