Checklist README

This is a repository of various checklists.

We use these checklists as a mechanism to validate the system against levers of known best practices.

Why?

To improve quality

Theory

In statistical process control, when you don't have control over the thing you want (quality, worth, appeal), then you have to

1. create soft signals that somewhat positively correlate so that you can push that target somehow.
2. control inputs
3. build a rough estimate based on relative signals + assumptions + statistical model

To that end, we look to optimize the quality, correctness, standards of code by applying standard techniques as a facsimile to truth:

1. test code coverage
2. CI/CD
3. standards conformance
4. linting shapes
5. documentation and structural conformaance

The lack of quality attributes such as lack of support for WCAG, internationalization, security scanning, etc are useful proxies to approximate the quality of a system.