You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a broad set of interests than I would be confident in. These really do not map well onto my competencies and proficiencies.
Yes, I realize (now) that the README.md file states that interests are for people who would be confident when selected for a project which primarily use the said technology.
However, I suggest a wider statement vocabulary would be more beneficial for selection and perhaps displaying the graph the connecting lines coloured differently or being otherwise distinguishable. Scanning the python, I think there might even be a stub for coding these in the graph visualization.
Also suggest ability to filter view on:
People and Subject areas by said level of "interest". I suggest we adopt the vocabulary: "interested", "competent", "proficient".
The text was updated successfully, but these errors were encountered:
Hi - thanks for the feedback! This tool is almost certainly going to be phased out in favour of skills information being incorporated into CapX. Do you want to contribute to one of these issues instead?
I have a broad set of interests than I would be confident in. These really do not map well onto my competencies and proficiencies.
Yes, I realize (now) that the README.md file states that interests are for people who would be confident when selected for a project which primarily use the said technology.
However, I suggest a wider statement vocabulary would be more beneficial for selection and perhaps displaying the graph the connecting lines coloured differently or being otherwise distinguishable. Scanning the python, I think there might even be a stub for coding these in the graph visualization.
Also suggest ability to filter view on:
People and Subject areas by said level of "interest". I suggest we adopt the vocabulary: "interested", "competent", "proficient".
The text was updated successfully, but these errors were encountered: