The need to update and expand our Developer Stages has come up more times than I can count.
This month, we’re kicking off our Fellowship program and one of the first steps is for Fellow Mentors and Fellows to develop an individual learning plan. For those that want to use the fellowship as a way to advance through the dev levels, having an up-to-date set will be a great resource! And hopefully it will make it easier for anyone in the community wondering what it takes to become a /dev/4 or a /dev/5 to figure out how to get there.
What resources can we work with?
The 2017 Q1 Brainstorming Dev Stages spreadsheet that @burke shared with me a while back is a fantastic tool! It divides the dev stages into areas (Communty, Developer, Open Source, Tools) that are then broken down into skills (i.e: Tools >>>Bash, Git, JIRA, Maven, SDK) and then those skills are further broken down into what we expect developers at each level to be able to do.
How do we do this?
Here are three questions that you can help us answer, area by area:
Question/Task #1 (Row 2): Does this area capture the full set of skills that an OpenMRS developer needs? If not, what skills do we need to add?
Question/Task #2 (Rows 3-7): Which skill expectations need to be updated? What would you change or add to bring them up-to-date?
Question/Task #3: Where skill expectations are missing, what skill expectations would you add?
For the skill expectations, we probably want to start by identifying the skill expectation for /dev/5 and then work through /dev/4, /dev/3, /dev/2, etc. Open Source>>Tickets shows a nice progression from /dev/1 to /dev/5. It reminds me of one of my go-to resources for verbs that describe skill progression.
What do you think? How would you answer these questions?