Module 1 Syllabus

Overview

In Module 1, students will learn to use Ruby and object-oriented programming to build software. They will develop skills to write automated tests, pseudocode, write implementation code, and refactor code to meet Ruby conventions. Through several large group projects and regular pairing exercises, students will learn skills and procedures for effectively collaborating and pairing with other developers.

Projects

Projects require students to apply new concepts from class and build on existing knowledge. Students will have a total of 4 projects in Module 1:

  • Independent Project - Begin Monday week 1, due Monday week 2.
    • The goal of this project is for students to practice all of the key concepts of module 1 covered in the prework and week 1.
    • This project is safe to fail, meaning it will not count towards the final promotion decision at the end of the module.
    • Students will be given feedback on their project, but scores will not be recorded.
  • Paired Project - Begin Monday week 2, due Thursday week 3.
    • This project will count towards the final promotion decision.
  • Group Project - Begin Monday week 4, due Thursday week 5.
    • This project will count towards the final promotion decision.
  • Independent Project - Begin Friday week 5, due Wednesday week 6.
    • This project will count towards the final promotion decision.

Independent Challenges

In week 6, students will participate in the Final Independent Assessment that will count towards the promotion decision. This is a 3 hour code challenge students will complete independently, meaning the student cannot seek help from other students, mentors, etc. Students are allowed to reference notes, other projects, and the internet.

In order to practice for the Final Independent Assessment in week 6, students will be given a practice Independent Challenge most weeks. They will be submitted using a Github Pull request, and instructors will give feedback in the form of comments on the Pull Request. These are not formal assessments, but an opportunity for the student to practice their problem solving skills and receive feedback from instructors.

Students can find examples of Independent Challenges here

Paired Assessments

In week 6, students will participate in the Final Paired Assessment that will count towards the promotion decision. Students will be required to complete a small coding task in advance of the assessment, and then will be given 30 minutes to pair with an instructor on an additional task that builds on their existing code.

In order to practice for the Final Paired Assessment in week 6, students will participate in the Mid Module Paired Assessment in week 4.

Students can find examples of Paired Assessment challenges here

Scores

Projects, Paired Assessments, and Independent Assessments will be scored on a 4 point scale:

  1. Well Below Expectations
  2. Below Expectations
  3. Meets Expectations
  4. Well Above expectations

Scores reflect the instructor’s expectations for the student’s progress at that moment in time, not the expectations for the end of the mod. Assessments will be broken into iterations. A student is expected to complete the project or assessment through iteration 3.

Written CFU (Check for Understanding)

Students will receive a weekly CFU (check for understanding). This CFU will cover the material up to that week. It is to be completed independently, and is closed note, closed internet.

Ruby Exercises

Link to Repo

Students will use these exercises to practice the material covered in module 1. While the projects require synthesizing many concepts, the Ruby Exercises are meant to practice a concept in isolation. Successful students will reinforce their skills through both projects and exercises. Exercises will not be assigned or graded, however instructors will provide a weekly list of suggested exercises to practice the material.

Support

One-on-Ones: Students can request to meet with an instructor to talk about non-technical topics at any time. This can include a student’s progress, stress management, suggestions for improvement, etc. This conversation should not involve laptops, coding, whiteboarding, etc. These will be guaranteed if requested.

Instructor Pairing: Students can request paired work time with an instructor.

Student Support: Students can request paired work time with Turing’s Student Support Fellow.

Lightning Talks

Each student will give a 5 minute presentation on a topic of their choosing. This topic does not have to be technical, but must be approved by instructors.

Portfolios

Students must complete a Portfolio, and participate in a Portfolio Review. Instructions for the Portfolio can be found here

Slack

Instructors will use the cohort Slack channel as the primary means of communication with students.

When sending a direct message (DM), students must DM ALL instructors. Exceptions are when a DM only applies to one instructor, for instance scheduling a one-on-one.

Attendance

Attendance is required at 90% or above to pass Module 1. Attendance will be counted at all scheduled activities from 9:00 am to 4:00 pm not listed as “Project Work Time”. Per the Student Course Catalog, tardiness will be counted as absence.