M1 Backend Pentathlon
To advance to M2, M1 students will need to demonstrate competency in individual projects, pair projects, professional development and community engagement. M1 students will also need to successfully complete the following five activities in week 6.
Students will have 90 minutes to complete a written diagnostic. Questions will cover material from the five weekly diagnostics students receive on each Friday.
Students will pair with an assessor for 45 minutes. They will be assigned a baseline assignment and are expected to make meaningful progress on an extension. Students must demonstrate comfort with test-driven development, Ruby convention, and object-oriented programming.
Timed Independent Assessment
Students will have 2 hours to complete a timed exercise. Outside documentation is allowed, but students should not consult other students or mentors during this exercise.
- Student will have to clone down an assessment repo.
- There will be a branch that has tests on it that the student will have to merge into the master branch and resolve any conflicts.
- Once conflicts are resolved, the student will have to complete the remaining challenge, with testing, on their own branch (will include enumerable and additional code).
- Student must submit a PR to the repo.
Final (Pair) Project
Working in pairs, students much successfully complete (scores of 3 or higher across all categories) their final project, either Headcount or Black Thursday.
Students will need to submit their portfolio according to instructions posted in the M1 Backend section of the turing/portfolios README. Portfolio pull requests need to be submitted 12 hours before students present their portfolios to instructors on the final Thursday of the inning.
- End of Module Assessments (diagnostic, pairing, and timed-exercise)
- Individual Work and Projects
- Group Work and Projects
- Professional Skills