Code Your Future - Home

🧑🏾‍💻 prep

Check your backlog and come to class with questions.

🔖
  1. overcoming-blockers
  2. Learn about Slack
  3. code.org
  4. CYF Blocks
  5. backlog

Overcoming Blockers

Reading

Overcoming Coding Blockers

Why are we doing this?

In class we will talk about Iteration and Blockers. Read over the day plan. What does iteration mean? What are Blockers? Write down your answers.

Learn about Slack 🔗

Learning Objectives

Preparation

You need to use the Internet to search for answers.

Introduction

Slack is the primary collaboration tool within our community and tech companies. This means you have to know it for your future job in tech.

What is Slack?

🎯 Goal: Understand how Slack works (25 minutes)

code dot org

Learning Objectives

Code.org is a block based programming tool. We will use something similar to build our course project. Go to the Code.org website and work through the first two exercises

Exercise

Go to Course Three, Lesson 2: The Maze

  1. Inspect the interface
  2. Complete exercise one and two

CYF Blocks

Learning Objectives

For the majority of this course, we will use a custom CYF application called CYF Blocks. It uses the same visual programming editor, Block.ly, as Code.org, but you will use it to create JavaScript for real websites you can show others.

CYF Blocks

  • Inspect the interface
  • Read the introduction
  • Complete all steps in the first exercise

Backlog

Learning Objectives

In software development, we break down complex projects into smaller, manageable parts, which we work on for a week or two. These periods are called “sprints.”

A sprint backlog is like a to-do list. It lists what the team has decided to work on this sprint. It’s chosen from a larger list, usually called the “product backlog,” which holds the entire project to-do list.

For your course, the mandatory work has been scheduled already. You will add any other tickets you want to work on to your backlog and schedule them according to your own goals and capacity. Use your planning board to do this.

You will find your backlog in the Backlog view on every sprint.

Copy the tickets you are working on to your own backlog. Organise your tickets on your board and move them to the right column as you work through them. It’s a flowchart:

flowchart LR Backlog --> Ready Ready --> in_progress in_progress[In Progress] --> in_review in_review[In Review] --> Done

Backlog (30 minutes)

  1. Find the sprint backlog
  2. Copy your tickets to your own backlog
  3. Organise your tickets on your board