Tedium is particular, scale is generic: Difference between revisions
Jump to navigation
Jump to search
Amwelladmin (talk | contribs) No edit summary |
Amwelladmin (talk | contribs) No edit summary |
||
Line 1: | Line 1: | ||
{{a|maxim|}}{{Tedium is particular capsule}} | {{a|maxim|}}{{Tedium is particular capsule}} | ||
{{sa}} | {{sa}} | ||
*Reg tech]] | *[[Reg tech]] | ||
*[[Software as a service]] | *[[Software as a service]] |
Revision as of 19:55, 7 February 2021
|
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.