Motivated by Bryan Cantrill, who brought up the abbreviation o11y for observability and is well known for his work on DTrace and blogging about his views on software, here are further ideas and thoughts on modern software engineering, explaining desirable properties of a software project and working with it for continuous improvement, longevity, and general sustainability, from cooperation to long-term maintenance.
| full expression | abbrev. | reading |
|---|---|---|
| reviewability | r11y | [ral-ee] |
| comprehensibility | c15y | [cis-ee] |
| reusability | r09y | [ron-ee] |
| hookability | h09y | [hon-ee] |
| observability | o11y | [oll-ee] |
| debuggability | d11y | [dil-ee] |
| reproducibility | r13y | [rib-ee] |
Check your patch, or have it done automatically. Is it consistent with others?
Have a peer review your work. Can they grasp it?
If applicable to multiple contexts, is your code split up, offering interfaces?
Mind your setup. Does it allow for isolating individual components?
Look at your module. When hooking into it, can you monitor its behavior?
When observing a module, do you have the information necessary to spot issues?
Create a build, run a test. Is there guarantee for a deterministic result?