rgw@icdattcwsm:~$ l
rgw@icdattcwsm:~/Blog$ cat 2024-11-18-Compliance-Means-Compliance.md

A common mistake is to mis-label a process compliance issue as anything BUT a process compliance issue - product bug, design bug, communication bug, tech bug, bla bla bla bla bla ...

A compliance issue is nothing BUT a compliance issue.

Yes, compliance is, and feels, STUPID, yet 100% necessary.

You can solve for X, but you can't solve for STUPID. Thus, compliance MUST be driven, or closed, in the spirit of obedience - NOT 'solved'.

De-regulation is a valid debate, where decentralization is often the correct solution. However, relative notions of bad regulation is no excuse for non-compliance. Here, it is essential to 'embrace the suck'.

rgw@icdattcwsm:~/Blog$ cd ..