When checking a level, check all lower ones
Opened this issue · 2 comments
If I check level 2, check level 1 and level 0.
Is it really worthful and useful? May someone be level 2 and not level 1?
I guess someone may be level 2 and not level 1 at same time, but this depends on the skill...
But if you would implement this i'd suggest you something different. Supposing this is an evolution I don't think it makes sense to have level 1 checked if you have level 2 also checked, it should be just one level checked for each topic showing the stage you are at. Example: If my API level is: "Has the most frequently used APIs in memory", doesn't make sense at all, have checked: "Needs to look up the documentation frequently"; I'm not at this level anymore, why would be checked, you know ?
By definition, knowledge for each level is cumulative. But while in one group this is always true, this is false in another.
What if my first VCS was git and I neither used SVN nor CVS? Or what if I write code in TDD manner, but never thought that all testing is the job of the tester?
I think that "cumulativeness" here means that in case of exception from the rule it is not a big problem to understand/apply ideas from previous level.
Because of all the above I think that described feature must be implemented.