Module 1 Pre-work

In order to make you as successful as possible during your time here, we have collected readings and exercises for you to complete prior to beginning Mod 1. This pre-work helps provide important context, vocabulary, and baseline of skills to help you hit the ground running on the first day of class. We’ve found that students who come into the program having invested time in familiarizing themselves with key concepts are able to maximize their time at Turing.

Mod 1 Pre-work Overview

The Mod 1 Pre-work is divided into three sections: Professional Development, Gear Up, and Technical. It is recommended that you start as soon as possible on your mod 1 pre-work, as it typically takes about 30 - 40 hours to complete. If you finish your mod 1 pre-work early, make sure you continue to code every day after you have completed the assignments, so that your skills don’t atrophy. You SHOULD NOT complete the mod 1 pre-work early and take an extended break from coding before your first day of class. This is very important to make sure you are in a routine that will keep your skills sharp and prepare you to hit the ground running on day 1.

Pre-work Assignments

The following assignments are due based on your mod 0 section and can be found on the mod 0 calendar

The pre-work is made up of 3 parts:

Professional Development (2 hours)

Turing is not just a school where you learn to code. Turing’s curriculum focuses on both technical and professional development.

In order to achieve our mission and vision, we also have group sessions each week called Gear Up in order to bring community awareness to certain issues in the tech industry.

The assignments below will be submitted in gists that you will create on your GitHub account. A gist is a text document that can be stored on GitHub. To create a gist, follow the steps below:

  • Log in to your GitHub account
  • In the upper right corner, click on the ‘+’ icon
  • Select ‘New Gist’
  • Enter a filename, with the extension .md
  • Enter the text of your gist in the large text area
  • click Create PRIVATE Gist
  • You can also visit

We take these exercises seriously, and we ask that you do too. We expect at minimum 4-6 sentences in response to each question, but feel free to expand and elaborate as you deem necessary. Use Markdown (this is a programming language used for writing) to format your gists.

Use these exercises to start telling your unique story with your distinct experiences. This is something we will continue to practice during your time at Turing.

You can find the professional development assignments here

Submission instructions for the PD assignment will be listed in the link above.

Gear Up (2 hours)

Gear up is a part of our curriculum where we talk about topics such as privilege and power, and ethical issues in the tech industry. Here is the Gear Up Assignment.

The gear up assignment will be submitted with the technical pre-work. Instructions can be found on the finalProject README of the technical pre-work.

Technical Pre-work (Program Specific) (30 - 35 hours)

The technical Mod 1 Prework is split up into 4 sections. Each section builds on the previous section in terms of technical content and complexity, so be sure to go in order!

At Turing, you will have to code every single day to stay on top of the workload and build muscle memory for everything you’ve learned. This pre-work is designed to get you into that essential routine before day one of class.

After completing the technical pre-work, you should be able to do the following:

  • Be comfortable navigating your development environment and using your tools (Atom, Chrome, the console, and the command line)
  • Develop a basic knowledge of Ruby (for back-enders) or JavaScript (for front-enders)

The link below will take you to the Github page that contains all the Technical work. Scroll through the page to find the instructions for getting your computer setup and getting started.

The technical pre-work and Gear up pre-work will be submitted in a google survey that is linked on finalProject portion of the technical pre-work repo for your respective program.

Next Steps.

If you have more time, review the curriculum site for the program that you’re joining.