Tedium is particular, scale is generic: Difference between revisions
Jump to navigation
Jump to search
Amwelladmin (talk | contribs) No edit summary |
Amwelladmin (talk | contribs) m Amwelladmin moved page Tedium is particular, not generic to Tedium is particular, scale is generic Tags: Mobile edit Mobile web edit |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{a|maxim|}}{{Tedium is particular capsule}} | {{a|maxim|}}{{Tedium is particular capsule}} | ||
{{sa}} | {{sa}} | ||
*[[Real-life legal problems]] | |||
*[[Reg tech]] | *[[Reg tech]] | ||
*[[Software as a service]] | *[[Software as a service]] | ||
{{C|Tedium}} | |||
Latest revision as of 06:35, 22 October 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.