Tedium is particular, scale is generic: Difference between revisions

From The Jolly Contrarian
Jump to navigation Jump to search
No edit summary
Tags: Mobile edit Mobile web edit
No edit summary
Line 4: Line 4:
*[[Reg tech]]
*[[Reg tech]]
*[[Software as a service]]
*[[Software as a service]]
{{C|Tedium}}

Revision as of 10:23, 16 February 2021


A hearty collection of the JC’s pithiest adages.
Index: Click to expand:

Comments? Questions? Suggestions? Requests? Insults? We’d love to 📧 hear from you.
Sign up for our newsletter.

Tedium is particular, scale is generic. That is why it is tedious. Because it can’t be scaled, and therefore solved. If the same sort of tedium were common to enough market participants that a glib SaaS solution could fix it, it would have been fixed by now.

Fixable, generic tedium is not stable. It gets fixed. Particular tedium is stable. It persists, not because because it is tedious, but because it presents in a unique, abstruse, absurd, obtuse way. These kinds of things do not dissolve in water. They are not susceptible of straightforward, “let’s science the shit out of this” solutions.

See also