Elasticity also describes a feature that I’ve wanted my email inboxes to have, but never known the term for.
I would like messages to automatically archive after a certain duration, perhaps a week, if I haven’t interacted with them. If a message matters, I’ll read it, star/pin it, or both.
Attaining this kind of elasticity tends to be expensive, though—one has to be aware of specifically wanting it (rather than the vaguer and more prevalent generalized dislike of an inelastic status quo), and also know what the particular elasticity is called to search usefully for whether someone has already built it, and also test+implement a potential solution or build it oneself.
Since the ROI of elasticity tends to be long-term and subtle, I often find it difficult to regard that bolus of elasticity-generating effort as worthwhile to do instead of other stuff in any particular moment, even when it’d obviously be useful in a more general sense.
Elasticity also describes a feature that I’ve wanted my email inboxes to have, but never known the term for.
I would like messages to automatically archive after a certain duration, perhaps a week, if I haven’t interacted with them. If a message matters, I’ll read it, star/pin it, or both.
Attaining this kind of elasticity tends to be expensive, though—one has to be aware of specifically wanting it (rather than the vaguer and more prevalent generalized dislike of an inelastic status quo), and also know what the particular elasticity is called to search usefully for whether someone has already built it, and also test+implement a potential solution or build it oneself.
Since the ROI of elasticity tends to be long-term and subtle, I often find it difficult to regard that bolus of elasticity-generating effort as worthwhile to do instead of other stuff in any particular moment, even when it’d obviously be useful in a more general sense.
I actually had that as an example in a draft, but my friends told me it didn’t quite fit the mold so I deleted it :)