It's time to prepare for the next course by installing all relevant software! Depending on what track you signed up for, you will install software for C#/.NET or Ruby/Rails.
We have students install software during the weekend before team week for a couple of reasons. The first reason has to do with installation and configuration issues. It's normal to run into some issues when setting up your personal environment, and the way we deal with this is to work through the installation process early so that we can identify and address any issues sooner.
The second reason is that you'll be ready to tackle the remaining pre-work for the next course when it comes time to complete it. Students are required complete pre-work for the next course before the first day of the course. Most students complete the pre-work during the weekend before the course starts, but you can start as early as you like. Take a moment to follow the link below to look at your upcoming course, and notice all of the sections that are labeled "pre-work":
For full-time students:
For part-time students:
Find the course you are signed up for below and install the necessary software.
If you are in a track that includes the C# and .NET course, install the packages in the following lessons.
If you are in a track that includes the Ruby and Rails course, install the packages in the following lessons.
Sometimes issues can arise in the installation process. Because setup issues naturally arise, students and teachers collaborate on solving setup issues together during an in-class troubleshooting session at the start of the backend course. Let's review the guidelines and expectations for that now.
The first step is for you to take the time to install the necessary tools for the course at home. You start this process individually during the weekend before team week, and students often finish this process without help. If you run into any installation issues, that's ok. See #2 below.
It's important to take notes and screen shots for any issues or error messages that comes up. You can then share these notes with your peers and teacher during the in-class troubleshooting session. It's also important to take the time to work through the issue yourself. Whatever you try in the troubleshooting process, take notes. The same goes for any helpful resources you find online. We recommend reading through terminal output and any error logs that come up in the installation process, as they can point what to look into that may be missing.
Your instructor may have further instructions for you as far as how or where they want you to take notes on any issues. Your instructor may also ask that you "check in" about how your installation process went on a spreadsheet or whiteboard so they can track issues and organize help. Whatever it is, make sure to follow your instructor's directions.
For anyone who hasn't been able to resolve an installation issue, you will group up during the first class of the backend course and continue troubleshooting together. Your instructor will have more directions for you about grouping up, and they will be present and available during this time to also help troubleshoot installation issues. This troubleshooting session is focused on collaboration, so discuss your issues and share your notes with your peers. Situations happen where your classmate has solved a problem you are currently facing and has advice for you, and vice versa!
As you work through your installations, keep in mind that it's common for environment issues to crop up and for them to take a while to resolve. This is why we begin the installation process over the weekend before team week and continue into the first class of the backend course. Make sure to do your part by troubleshooting any issues that come up, and by taking notes on what the issues are and what you did to try and fix them.
If you have any questions or concerns, talk to your instructor about them as soon as you can.
Lesson 7 of 11
Last updated more than 3 months ago.