A weird way to think about batched production. If you write a blog post today that's published in a month, the version of you that wrote it has been "dead" a month when it gets out. I like anything I produce to be as much of a "fresh kill" of myself as possible. Macabre huh.
Conversation
Live players in the sense like to be just-in-time players for this reason. If you're living and changing, JIT is the highest-fidelity authentic output you can hope for. Batching and delay is dead-player production.
1
4
The flip side of this is being stuck in perpetual “hot takes” and never writing a timeless classic. How many books and articles written today will we look back on in even 10 years?
1
You misunderstood. The work may take years. I’m talking no delay between finishing and it being seen by others. Either deliberate delay due to editorial schedule or distribution delay for things like books screws this up.
Particularly bad for slow peer review. I used to hate those 3-6 month iterations because I’d already moved on. Felt like being executor of estate of dead person. That’s partly why I quit academia.
1
1
Show replies
I’m not sure it screws up a “fire and forget” type post, but it probably does if you want to have a significant interaction with your audience at launch time (which is probably where everything is headed anyway, tbf)
1

