🧑🏾‍💻 Prep

There is just so much to do!

🔖
  1. Install a unix based os
  2. Check Git
  3. Install VS Code
  4. Create CYF Folder
  5. Fork your Planner 📼
  6. Set up Planner
  7. Make your Planning Board 📼

🧰 Install a UNIX based operating system

Learning Objectives

If you get stuck on any of the below or above instructions, please post in your class channel on Slack.

You probably already have this if you have done previous modules.

⚠️ warning

Code Your Future does not support Windows.

We have found that we don’t reliably have volunteers at class who can debug Windows problems, and they frequently come up, stopping trainees from making progress.

We do not support Windows so as to not waste lots of trainee and volunteer time. We have made this decision even though Windows is a popular operating system and has features like WSL which help to get experience with Unix.

You must use a Unix-based operating system at Code Your Future.

If you have a Mac or Linux machine already, you already have a UNIX based operating system. All CYF-supplied laptops run Mac OS or Linux. If you have your own machine and it runs Windows, you should already have set up a Linux partition.

If you have still not done this, you must do it now. We cannot support learners using Windows. It takes too much time from everybody else. If you need help doing this, post in Slack, or bring your laptop to a CYF co-working space to get support. It’s normal to need help with this process.

Dual Boot on Windows

📋 Check Git installation

Learning Objectives

Git

You will use Git continually as a developer. We will cover Git in more depth later in the course. Right now, we will just check that you have it installed.

Open up a terminal and run the command git --version to double check you have Git installed. If it is installed successfully, you should get a version number (which may not be exactly the same as this example, but should look similar):

git version 2.40.0

Otherwise, you will need to install it or ask for support on your Slack channel.

🧰 Install VSCode

Learning Objectives

We use VS Code to write all of our code in the course. It is known as an Integrated Development Environment (IDE) and really helps you write great code!

🔗 Download and install VSCode now

Watch this video if you’d like a quick introduction to VSCode:

Create a work folder

Learning Objectives

You’ll need to create a CYF folder to store your projects on the course.

  1. Open a terminal on your computer.

For each of the steps below, you’ll need to use the command line in your terminal.

Use this cli documentation to remember terminal commands.

  1. In your terminal, print your current working directory.

  2. List the files and folders in your current working directory.

You’ll need a place to store your work for the course.

  1. Make a new directory called CYF in your home directory.

  2. Change directory into the CYF directory.

  3. Double check you’re in the right place by printing your current working directory.

Set up Planner 🔗

Welcome to your coursework planner

This is how you will plan and manage your coursework at CYF. You will add all your work as issues to your fork of this repository, and then use a project board to manage your work. This is broadly how all technical projects are managed, so you will need lots of practice. Get started today.

1. How to get set up

  1. Fork this repo to your own GitHub
  2. Turn on issues in the settings

You must fork to your personal Github account. Forks created in the CYF org will be deleted by a bot.

2. Every module, you will add your work as issues

Each module has a module repo. The coursework for each module is added as issues to that repository. All the module repos are listed in the Table of Contents.

  1. Go to the module repo
  2. Click on the Issues tab
  3. Copy each issue from the module repo to your own coursework repo.

We are building a tool to automate this process, but for now you will have to do it manually. We all use the Kamino Clone Button Chrome extension to make this easier, so you could try that.

Copy issues for each week or at most for each module. The coursework content is updated frequently, you will not have the most up to date tasks on your board if you copy all modules at once.

3. Refine your tickets and add them to your project board

  1. Copy the example project board
  2. Link your new project board to your fork of this repo
  3. Add your tickets to the project board, using the labels to help you assign the fields
  4. Make your board public in the settings, so your mentors can see it

There are example project boards attached to each module, showing you ways you can use boards to manage your time, prioritise, scope, and track your work. You should use the same project board all the way through the course, and add to it as you go. Learn as you go, and adapt your board as you learn.

You can, and should, also add your own tickets to the board. Just remember it’s a public board, so don’t add anything you don’t want to share with your mentors.

You can watch this video about how to create your coursework-planner board.