rgw@icdattcwsm:~/Blog$ cat 2024-12-12-Everything-Sucks.md

Assume EVERYTHING sucks.

Architecture has two objectives. One, to make a system elegant. Two, to allow for elegant expansion of the system's capabilities.

And elegance can be defined as an intuitively aesthetic and factually syngergistic balance between the structured and chaotic components of the system.

It follows that, from a business standpoint, the efficacy of tech architecture can be guaged by the extent to which this question is answered satisfactorily: Does the 'stupidity' of the system, add or subtract value?

All business requirements of tech development, thus, ought to be held to the same standard: Does the 'stupidity' of the business requirement, add or subtract value?

Assume the product, business requirement, system - sucks. Don't observe the customer/ user - simply ask him which features he hates. And solve, for that.

By default, everything sucks. Hope and optimism, is the belief that today, we can make something suck a little less.

rgw@icdattcwsm:~/Blog$ cd ..