Please be DRY and align the following qualities:
(if redundant consolidate, else provide more distinction)
"Availability" vs. "High Availability" : do we really need this distinction? you use the same 5 examples for each!
"Coherence" vs. "Cohesion" : distinction leads to nitpicking
"i18n (Internationalization)" vs. "Internationalization" : appears to be duplicate
"Functional suitability" vs. "Suitability" : lack of distinctive examples! appears to be redundant
"User experience" vs. "User interface aestetics" : do we really need dedicated "aestetics" for that one given use case? --> KISS!
Further observations:
"Code Complexity" should also be #usable
"Jitter" should also be #reliable
"Recoverability" vs. "Recover time" : isn't the latter more an attribute of the first?
gernotstarke
commented
1 month ago
Please be DRY and align the following qualities: (if redundant consolidate, else provide more distinction)
"Availability" vs. "High Availability" : do we really need this distinction? you use the same 5 examples for each! "Coherence" vs. "Cohesion" : distinction leads to nitpicking "i18n (Internationalization)" vs. "Internationalization" : appears to be duplicate "Functional suitability" vs. "Suitability" : lack of distinctive examples! appears to be redundant "User experience" vs. "User interface aestetics" : do we really need dedicated "aestetics" for that one given use case? --> KISS!
Further observations: "Code Complexity" should also be #usable "Jitter" should also be #reliable "Recoverability" vs. "Recover time" : isn't the latter more an attribute of the first?