1. Hatchling Levels (How to Graduate the Dev Hatchery)

At CodeDoesGood you can volunteer to do development in three different ways:

• Mentor. A Mentor will provide mentorship to newer developers and can choose to contribute code if they want.
• Developer. A Developer will contribute code but is not tasked with mentorship.
• Hatching. A Hatchling is the name we give to the newer developers. Hatchlings receive mentorship. They are like baby chicks that will "hatch" out of their eggs as they learn and grow and gain experience.

Hatchlings may go through these levels one at a time or may skip levels. When a new Hatchling joins CodeDoesGood we will use the Hatchling's own self evaluation as well as our review of their prior work to determine which level they enter CodeDoesGood at.

Hatchling 0:

Has completed only tutorial based projects or code samples. Has completed less than 20 of these.

Hatchling 1:

Has either completed more than 20 tutorial based projects or code samples or has done a couple small projects on their own or on a team without following a tutorial. These are mostly or possibly only learning assignments and not full projects. Also full apps which only have a few screens.

Hatchling 2:

Has completed at least one full app-store level project (does not have to be in an app-store) on their own or with a small team.

Hatchling 3:

Has completed at least two full app-store level projects (do not have to be in an app-store) on their own or with a small team, at least one of which does more than just download and display data. Example they have built a custom component, advanced animations, working with media, etc. These components were not copied from tutorials.

Hatchling 4:

Has worked on a team at a business under the guidance of a lead mentor and can satisfy the requirements of Hatchling 3. A Hatchling who has worked at a business under the guidance of a lead mentor but can not satisfy requirements of Hatchling 3 will be deemed level 3 for their first CodeDoesGood project. A Hatchling at level 4 should be able to resolve common compiler issues / errors on their own and have some kind of idea of how to look for answers when they are stuck. Note, we do not expect Hatchling 4's to be able to always find the answer, but at this level when they encounter an issue they should be past the point of freezing and should have at least somewhat of an idea of what to look for before asking for help.

Hatchling 5:

Feels confident working under the guidance of a mentor. Knows when to ask for help, does not allow themselves to be stuck for too long. Listens to feedback and addresses it in a mature way. Does not take code review personally, has learned code review helps them and improves their skills. Is able to spot basic errors in other people's code. May still experience panic or paralysis from time to time but more often than not can start a feature without too much guidance. This level would be considered an upper-junior on most junior-intermediate-senior scales.

Hatchling 6:

Is able to help other Hatchlings with questions. Understands what is going on with their project (things are not "magic" any more). Understands how the components of their platform fit together and can start to deduce what could be wrong when they encounter an error / compiler issue they have never seen before. Hatchling 6's should be actively involved in code reviews. This level would be considered a lower-intermediate on most junior-intermediate-senior scales.

Hatchling 7:

The jump from level 6 to level 7 is partly based on evaluations by mentors that have worked with the Hatchling but the final criteria for becoming a Hatchling 7 is that the Hatchling themselves must feel ready. This is the last level before graduating the Dev Hatchery. A Hatchling 7 is not expected to be at a mentor level but is expected to be self responsible. At this level a Hatchling knows to ask for help when they need it. They do not allow themselves to be stuck for very long. A Hatchling 7 can come up with multiple solutions to problems they face and they have learned debugging skills -- though they may still need assistance from a mentor to debug complicated issues. Hatchling 7's are interested in code review and answering questions on their platform channel.

A Hatchling may stay at level 7 for as long as they feel they need to. The next step after Hatchling 7 is to become a Mentor. The only difference between an Assistant Mentor and a Lead Mentor is the ability to lead a project. It is possible for a Hatchling 7 to graduate the Dev Hatchery and become a Lead Mentor for a small project though they most likely would be an Assistant Mentor on their first post-graduation project.