I'm doing a quick review of the existing features to see (a) what they do and (b) how what they do is modeled and possibly (c) what way can the model be simplified to reduce its api footprint
Some hypotheses Sri is considering during review:
If there's no clear model, the api is confusing and relies on memorization that adds nothing to understanding and is hard to "reason" about (spaghetti "logic")
If the model is difficult to describe, it is even harder to learn (concepts blur/conflated with process and method)
If the model is an entirely new concept to a user, then simplified version might provide a better anchor for introducing it (reduce time to seeing results)
If the model is a foreign concept with an intricate pattern of use, this is probably not a usable model for GEMSTEP purposes, and is more of a system api; needs conversion (programmer trap)
In GitLab by @daveseah on Aug 1, 2022, 13:45
I'm doing a quick review of the existing features to see (a) what they do and (b) how what they do is modeled and possibly (c) what way can the model be simplified to reduce its api footprint
Some hypotheses Sri is considering during review: