Narrative serialization is the worst-case instance of the batch-size reduction problem. cc
Conversation
Totally ordered sequence of bespoke tasks, payoffs at end, linkages that span first to last outputs (eg. clue on page 1 of murder mystery)
1
Simply breaking up the narrative into arbitrary chapters makes every chunk unsatisfying. The first chapter of a mystery is all Chekov guns.
1
1
In creating "batches" (chapter-sized "releases") you have to create artificial 'episode arcs', cliffhangers and subplot wraps
4
2
You also have to keep the long-arc logic and momentum developing and not dissipating.
1
2
A truly complex narrative like a novel, if serialized, probably acquires additional 20-50% "batching" epicycles
1
2
My point: there is a tradeoff between batch size reduction and narrative serialization costs and a crossover line where former beats latter
This sounds the same as the programming debate around how small code modules should be. If too small, hard to reconstruct "code narrative"
2
2
Any useful conclusions from that debate? Good readings?
2
1
Show replies
The book batch size reduction isn't to chapters, it's to an outline, of resonant elements
2
An outline isn't useful output though. It's an internal toolchain element.
1
Replying to
I’ll have to noodle on narrativization, but I’m currently trying to figure out how multiplexing relates to knowledge work
1
1
Multiplexing is like packing pencils into ever larger containers for shipping; inverse multip. like breaking up house into pieces 2 move
1
Show replies



