Narrative serialization is the worst-case instance of the batch-size reduction problem. cc @fortelabs
-
Show this thread
-
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 reply 0 retweets 0 likesShow this thread -
Simply breaking up the narrative into arbitrary chapters makes every chunk unsatisfying. The first chapter of a mystery is all Chekov guns.
1 reply 1 retweet 0 likesShow this thread -
In creating "batches" (chapter-sized "releases") you have to create artificial 'episode arcs', cliffhangers and subplot wraps
4 replies 0 retweets 2 likesShow this thread -
You also have to keep the long-arc logic and momentum developing and not dissipating.
1 reply 0 retweets 2 likesShow this thread -
A truly complex narrative like a novel, if serialized, probably acquires additional 20-50% "batching" epicycles
1 reply 0 retweets 2 likesShow this thread -
My point: there is a tradeoff between batch size reduction and narrative serialization costs and a crossover line where former beats latter
3 replies 0 retweets 1 likeShow this thread -
Replying to @vgr @fortelabs
This sounds the same as the programming debate around how small code modules should be. If too small, hard to reconstruct "code narrative"
2 replies 0 retweets 2 likes -
Replying to @kylemathews @fortelabs
Any useful conclusions from that debate? Good readings?
2 replies 0 retweets 1 like
Manufacturing in general is a special case of easy/high decomposability into smaller batch sizes except at complex end like airliners/ships
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.